Capture an authorized payment
Captures the full amount of a successful, uncaptured authorization. Partial captures are not supported, and a payment that is already captured or being voided cannot be captured.
Authorization
basic Basic HTTP authentication
In: header
Path Parameters
Payment id (UUID v7)
Header Parameters
Optional client-supplied retry key (≤255 chars; UUID v4 recommended). Don't use sensitive data — emails, PANs, or other personal identifiers. Identical requests retried with the same key return the original response (2xx and 4xx are cached). Mismatched bodies return 422; in-flight duplicates return 409. Keys are scoped per merchant + endpoint and expire after 24 hours. NOTE: on 5xx the idempotency record is discarded — retry with the same key (provider-side dedup protects against duplicate execution).
Response Body
application/json
application/json
application/json
application/json
curl -X POST "https://example.com/v1/payments/string/capture"{ "paymentId": "01928e1c-2a4d-7c8e-8b1a-1234567890ab", "status": "CAPTURED", "amount": 7200, "cardNumber": "555555xxxxxxxx4444", "cardExpiration": "1133"}{ "statusCode": 400, "error": "Bad Request", "message": [ "amount must not be less than 100" ]}{ "statusCode": 401, "error": "Unauthorized", "message": "Missing Authorization header"}{ "statusCode": 404, "error": "Not Found", "message": "Merchant not found: 01928e1c-2a4d-7c8e-8b1a-1234567890ab"}Authorize and capture a payment POST
Authorizes and captures the requested amount in a single operation. The request can optionally save the payment method for future use.
Charge a saved payment method POST
Charges an active saved payment method off-session and captures the payment immediately. The payment method must belong to the supplied customer and authenticated merchant.