Skip to main content
A pre-authorisation holds an amount on a customer’s card without taking the money. You then either capture it (taking some or all of the amount) or reverse it (releasing the hold). Typical uses: bookings with a cancellation window, deposits, and checking a card is good before provisioning.
1

Pre-authorise

POST /preauth with the same card fields as a charge (or a card_token), plus currency, amount and reference.
Keep pre_authid — it’s the handle for the next step. This response has no link field.
2

Capture

POST /charge with pre_authid, amount, currency and a reference. The amount can be less than the hold.
The response is a normal charge object, exactly as for Charging via the API, and a webhook follows.
3

Or reverse

POST /reverse with the pre-authorisation’s reference releases the hold.
Reverse returns a flat object rather than an envelope.
Pre-authorisation is card-only. Holds are released by the card issuer after a period if neither captured nor reversed; the exact window depends on the issuer, so reverse explicitly when you know you won’t capture.