Grouping

Activities are grouped by type to help you easily find relevant events.

Profile

Profile activities allow you to track when and how changes were made. Most profile changes are currently supported, and coverage is continuously expanded to provide a complete audit trail.

Import and Export

Displays all data imports and exports, including:

• Customers
• Mandates
• Payment links
• Invoices
• Refunds

Support

Tracks changes related to support actions within your environment.

Settings

Shows changes to general environment configuration, such as:

• Creation and removal of users and administrators
• Profile removal

API

API-related events, mainly focused on:

• Exceeding rate limits
• Webhook failures
• API key changes

Bank

Bank-related activities around collections, transfers, and signing processes, including:

• AutoCollect failures due to missing account information
• Double payments detected for invoices (e.g. wire transfer received for an already paid invoice)

Integrations

Lists integration-related events, mainly errors that occur when an external integration fails.

Email

Activity grouped by email status :

• Sent
• Failed
• Pending
• Blocked

Future tasks

Activities related to upcoming tasks for agreements and invoices.

Invoices

Invoice-related activities covering communication, lifecycle events, and payment status.

Your profiles

Activity grouped by agreement actions for your active profiles .

• Invited
• Printed
• Uploaded
• Signed
• Accepted
• Cancelled

Activity Levels

Each activity is assigned a level, indicated by a color, to show its importance.

Info

Informational events that reflect normal usage of the platform.

Examples:

• Imports and exports executed in your environment
• Profile updates
• Creation of new users or administrators

Warning

Non-blocking events that require attention but do not immediately prevent actions.

Examples:

• Removal of users or administrators
• Detection of double payments for invoices
• Removal of a profile
• API key changes

Error

Critical issues that may block customer invitations, mandate signing, or payment collection and should be resolved as soon as possible.

Examples:

• Unable to reach the bank (remote failure): Often occurs when a customer tries to sign an agreement
• Email integration failures: Usually caused by incorrect configuration; the reason is often shown
• Could not finalise a direct payment: Typically due to an error returned by the PSP
• AutoCollect failed: Transactions could not be sent to the bank because an account number is missing
• API rate limit exceeded
• Webhook failures

How to resolve common errors

AutoCollect failed

AutoCollect failures appear in the Bank group at error level. The most common cause is a missing bank account number — the error message indicates which account or configuration is incomplete. Verify that a valid bank account is configured in Settings > Payment Hub and that the connection to your bank is active.

Webhook failure

Webhook failures appear in the API group. The message usually indicates whether the endpoint was unreachable or returned an error.

1. Open the webhook failure event and check the error details.
2. Verify that the webhook URL is correct and reachable from the internet.
3. Update the endpoint in Settings > Integrations > Webhooks if needed.
4. If the problem persists, contact Twikey Support with the error details from the activity log.

SMTP failure

SMTP failures appear in the Integrations group. The error message typically states the cause — SPF or DKIM misconfigurations are the most common. Consult your IT partner to review and correct the email setup. See Invalid email address for more information.