Pre-Authorize (Hold Funds)
The first step detokenizes your card token to place a hold on the cardholder’s funds. PCI Booking replaces the token with real card data and sends an authorization request to your configured PSP.- Submit a card token, amount, currency, and gateway credentials ID.
- PCI Booking detokenizes and forwards the authorization to the PSP.
- The PSP places a hold on the funds and returns an authorization reference.
- No funds are transferred yet.
OperationType.
CVV. Each Process Transaction call that sends the card counts as one use of the CVV. Under the system default retention policy (one relay or one month, whichever comes first), the CVV is cleared after the first use, so a later charge, such as a no-show charge, is sent without it. If you need the CVV more than once, set a CVV retention policy on the token within 60 minutes of tokenization, or collect the CVV again with a CVV capture form.
Capture (Settle Funds)
The second step settles a previous authorization. You reference the original transaction ID, and include theCardToken as well - unless you supply a GatewayToken, in which case the card token can be omitted.
- Submit the original transaction reference and the amount to capture.
- The capture amount can be equal to or less than the authorized amount.
- PCI Booking forwards the capture to the PSP, which transfers the funds.
When to Use
- Hotels and travel. Authorize at booking, capture at checkout.
- Rentals. Authorize at pickup, capture at return.
- E-commerce. Authorize at order, capture at shipment.
- Partial captures. Capture less than the authorized amount if the final total changes.
Next Steps
Charge
Process a simple one-step charge instead.
Refunds & Voids
Reverse or refund completed transactions.
Process Transaction
Full API reference for this call.

