SEPA Direct Debit transactions (SDD)

• Initiation – With a valid SEPA direct debit mandate, you can start Direct Debit transactions via the interface, CSV import, PAIN008 file import, or API.
• Processing – Transactions are grouped in batches and sent to your bank for collection on the requested date. The batch includes all relevant mandate and transaction details.
• Settlement & notification – After collection, funds are credited to your account or settled by your payment service provider on the agreed date. Twikey then receives confirmation from the bank or provider, typically within 2 working days, and updates the transaction status in the interface and API.
• Transaction states – Transactions go through various states as they progress, f.ex. CORE mandate collections can report failures up to 8 weeks after collection.

Requirements for starting with Direct Debit transactions

• Twikey needs your power of attorney for the account(s) used to execute and manage Direct Debit transactions.
  More information is available in managing your payment methods.

Recurring Credit Card transactions (RCC)

• Initiation – With a valid token, recurring credit card transactions can be created via the interface, CSV import, or API.
• Processing – Transactions are grouped and sent to your payment service provider for collection on the requested date.
• Settlement – The payment service provider settles the collected amount on the agreed date.
• Settlement & Notification – The payment service provider settles the collected amount on the agreed date, and Twikey receives confirmation to update the transaction status accordingly.
• Transaction states – RCC transactions go through various states as they progres.

Requirements for starting with Recurring Credit Card transactions

• A contract with a payment service provider integrated with Twikey is required.
  More information is available in managing your payment methods.

Transactions menu overview

The Transactions menu gives you a complete overview of all payment transactions, from preparation and sending to follow-up and settlement. This article explains the different sub menus available and how transactions move through each stage.

To be sent

Shows transactions that are ready to be collected but have not yet been sent to the bank.
Transactions are grouped into batches and separated based on whether they are scheduled for immediate or future collection.
Click here to read how to send a batch for collection.

Sent

Contains transactions that have already been sent to the bank for processing.
This screen allows you to monitor the status of collections and identify transactions that have failed or require further follow-up.
Click here to read what you can do with transactions already sent for collection.

Unsettled

Displays transactions that could not be successfully collected and still require manual action.
These are typically transactions that remain unpaid after all automated follow-up steps have been completed.
Click here to read how to process unsettled transactions

Batches

Provides an overview of all batches created in the system.
Batches group transactions that are processed together and allow you to track, export, archive, or review collections at batch level.
Click here for an explanation of batch statuses and details.