Skip to main content
This page is part of the REST API Guides. Card capture happens in the frontend through the Payments Library; see the Payments Library Guides.
Prerequisites: API key and Payment Gateway Account configured. Authorization places a hold on funds without capturing them immediately. Use capture, void, or refund to complete the transaction lifecycle.
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 the cardNumber 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
Save the transaction ID from the response. You’ll need it for capture, void, or refund operations.

Authorize with Failover

Orchestra’s multi-gateway failover retries an authorization on a backup gateway if the primary fails. Add a fallbackUpgs 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:
The response is the result of the last attempt.
When using failover with authorize, check which gateway processed the transaction in the response. Send the capture, void, or refund to the Payment Gateway Account that processed it, not to your primary account.
See Multi-Gateway Failover for how Orchestra’s failover mechanism works.

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 typically reuses the same token referenced at authorize time.

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.
Don’t rely on authorization expiration to release holds. If you’re not going to capture, void the authorization explicitly.

Sending Raw Card Details (Non-Standard)

These examples show raw card details for completeness. Sending raw card data means it passes through your systems and puts you in PCI DSS scope. The standard integration captures the card with the Payments Library and references it here as a token (an @TOKEN value in the cardNumber field); see Authorize and Capture above.

Authorize

Capture

Refunds & Voids

Cancel or reverse transactions