Skip to main content

​
Overview

The Auth/Capture/Void flow splits a card charge into two steps:
  1. Authorize — reserve the funds on the customer’s card without charging them yet
  2. Capture — settle the reserved funds once you are ready (e.g. after shipping or fulfillment)
  3. Void (optional) — cancel the authorization before capture if the order is cancelled
This is useful for hotel holds, ride reservations, or any situation where the final amount is confirmed after the initial authorization.

​
Key Requirements

Use your public API key encoded in Base64. See the Authentication guide for setup instructions.
Set these headers on every request:

​
Endpoints

​
How it works

1

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.
2

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.
3

Void if needed

If the order is cancelled before capture, call the Void endpoint with the authorization_reference to release the hold on the customer’s card.
Authorizations that are neither captured nor voided will expire automatically. The expiry window depends on the card network. Implement monitoring to capture or void authorizations before they expire.

​
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.