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
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 automatically retries an authorization on a backup gateway if the primary fails. For authorize requests, failover isn’t a field you pass in the request body: it’s configured on your Payment Gateway Account setup.Contact Support
Email support@orchestrasolutions.com to enable multi-gateway failover for your authorize requests.
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 expire if not captured (typically 7-30 days depending on card network). After expiration, the hold is released and you’ll need a new authorization.Sending Raw Card Details (Non-Standard)
Authorize
Capture
Related
Refunds & Voids
Cancel or reverse transactions