Overview
The Auth/Capture/Void flow splits a card charge into two steps:- Authorize — reserve the funds on the customer’s card without charging them yet
- Capture — settle the reserved funds once you are ready (e.g. after shipping or fulfillment)
- Void (optional) — cancel the authorization before capture if the order is cancelled
Key Requirements
Use your public API key encoded in Base64. See the Authentication
guide for setup instructions.
Endpoints
| Method | Endpoint | Description |
|---|---|---|
POST | /card/auth_capture/authorize | Pre-authorize a card and reserve funds |
POST | /card/auth_capture/capture | Capture (settle) a previously authorized amount |
POST | /card/auth_capture/void | Void an authorization before it is captured |
GET | /card/auth_capture/authorize/{authorization_reference} | Retrieve a single authorization by reference |
GET | /card/auth_capture/authorize | List authorizations with optional filters (status, page, size, from_date, to_date) |
How it works
Authorize the card
Call the Authorize endpoint with the customer’s card details and the amount
to reserve. On success, you receive an
authorization_reference — store
this.Capture when ready
When you are ready to charge (e.g. after order fulfillment), call the
Capture endpoint with the
authorization_reference. The reserved funds are
settled to your account.Best-fit scenarios
- Inventory-dependent orders — Authorize at checkout, capture after stock is confirmed
- Hotel and travel holds — Reserve funds at booking, settle the final amount at check-out
- Risk-reviewed transactions — Hold funds while manual review is completed before capture
What’s next
Card Collections
Standard card charges without the auth/capture split.
Refunds & Chargebacks
Reverse a captured payment or respond to a chargeback.