This page is part of the REST API Guides. Card capture happens in the frontend through the Payments Library; see the Payments Library Guides.
Some payment processors require additional parameters. See the Additional Guidance section for processor-specific requirements.
When to Use Authorize
- Physical goods: Authorize at checkout, capture when shipped
- Variable amounts: Authorize an estimate, capture the actual amount
- Verification: Confirm a card is valid before providing a service
- Hotels/rentals: Authorize a hold, capture the final bill. For deposits, balances and extras across a booking, see Booking Lifecycle
Authorize
The standard integration authorizes a token captured by the Payments Library. Reference it in thecardNumber field with an @ prefix; cvv is optional and can be left out for a tokenized card.
Authorize API Reference
Complete parameter reference for authorize requests
Authorize with Failover
Orchestra’s multi-gateway failover retries an authorization on a backup gateway if the primary fails. Add afallbackUpgs array to the request body. Each entry names a stored Payment Gateway Account in paymentGatewayAccountName, and Orchestra tries them in order. On authorize, any result other than Success or Accepted moves to the next gateway:
Capture
Capture an existing authorization to complete the transaction. Uses PUT method.Capture requires re-sending the
currency, card, and other details from the original authorization.Capture API Reference
Complete parameter reference for capture requests
Completing the Transaction
After authorizing, you have three options:
For void and refund operations, see Refunds & Voids.
Authorization Expiration
Authorizations do not last forever. How long a hold stays valid depends on your payment processor and the card, so check with your processor. After it expires, the hold is released and you need a new authorization.Sending Raw Card Details (Non-Standard)
Authorize
Capture
Related
Refunds & Voids
Cancel or reverse transactions