How it works

1. You create a reservation via the API for the maximum expected amount. Twikey evaluates the mandate against your configured risk rules immediately.
2. When the final amount is known, you capture it by creating a transaction against the reservation. The capture amount can be equal to or less than the reserved amount.
3. If you no longer need the reservation — for example, when a session is cancelled — you delete it via the API.

Behaviour by collection type

• Recurring Credit Card (RCC) — When supported by your PSP, a hold is placed on the cardholder's card directly at the PSP level. Funds are ring-fenced until you capture or the reservation expires. PSP-side reservation support depends on your configured payment provider — check your PSP's integration documentation for availability.
• SEPA Direct Debit (SDD) — No hold is placed at the bank. The reserved amount is locked internally against the mandate's risk rules.

Expiry

Reservations expire after 24 hours by default. If the reservation is not captured or cancelled before it expires, it is automatically cleaned up. For RCC, the hold at the PSP is released. You can set a custom expiration date via the API when creating the reservation.

Viewing open reservations

When the feature is enabled on your account, open reservations are visible on the customer detail screen alongside transactions — showing you which amounts are ring-fenced but not yet collected. Contact Twikey support to enable this.