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.
Basic Charge
The standard integration charges a token captured by the Payments Library. Reference it in thecardNumber field with an @ prefix, in place of @YOUR_TOKEN below; cvv is optional and can be left out for a tokenized card. A token only works in the account that created it: a token from another account, including any shown in these docs, returns 400.
API Reference
Complete parameter reference, response fields, and validation rules
The token replaces the card number only. You still send
cardHolderName, expirationMonth, and expirationYear. When tokenizing through the library, these are returned alongside the token in tokenAndMaskedCardModel.bankCard. See Tokenization for creating tokens with StringTokens directly.Using Inline Credentials
Instead of a stored Payment Gateway Account, you can provide credentials inline:Adding Failover
Orchestra’s multi-gateway failover retries a charge 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:
Charge vs Authorize
If you need to hold funds without capturing immediately, use Authorize & Capture instead.
Sending Raw Card Details (Non-Standard)
Related
Refunds & Voids
Reverse or cancel this charge
Authorize & Capture
Hold funds and capture later
Tokenization
Store card numbers securely