Skip to main content
Capture converts a reserved authorization into captured funds. In this version of the API, capture is all-or-nothing: the amount you send must equal the original authorized amount.
This request requires a valid access token. See Authentication to obtain one with POST /v1/auth/token before you continue.

Full-capture rule

amount in the capture request must equal the amount on the AUTHORIZED transaction exactly. Partial capture isn’t supported — if you need to charge less than the authorization, capture the full amount and refund the difference once the batch closes. An uncaptured authorization can’t be voided, so if you authorize again for the correct amount instead, the first hold stays on the shopper’s card until its capture window runs out. amount.currency must also match the authorization’s currency — a capture naming a different currency is refused with 422 urn:radiumone:payment-gateway:tx:currency-mismatch.

The capture window

Capture within your account’s capture window, which defaults to 7 days from authorization and can be configured shorter or longer per acquirer. Capturing after the window closes fails with 422 urn:radiumone:payment-gateway:tx:capture-window-expired, and the transaction moves to AUTH_EXPIRED — see Payment lifecycle. Contact support to confirm your account’s configured window.

Steps

1

Capture the authorization

Send the transaction’s id and the same amount it was authorized for. API reference.
If the call times out, see Handle timeouts and unknown outcomes. If it fails with a window, amount, or expiry error, see Handle capture failures.

Handle the result

Any 2xx response is a result you must branch on status — never on response_code (that’s the verbatim host/acquirer code; useful for support tickets, not for your app logic).
After a timeout or a 5xx, replay with the same key. For every payment operation — purchase, authorize, capture, void, and both refunds — a replay of the identical request with the same request_id or operation_id is a lookup, not a resend, so it’s safe even after a 5xx that says retry_allowed: false (switch-timeout, database-unavailable). RadiumOne returns the outcome it recorded. If a capture, void, or referenced refund was sent but its outcome wasn’t recorded, RadiumOne asks the card network for the stored outcome instead of sending it again, and sends it only if the network never received it — so nothing is applied twice. A replay can return PENDING or REVERSAL_PENDING until the outcome settles. A request RadiumOne refused before it reached the card network (for example with device-settling or device-busy) is run again on the same transaction instead of returning a stored result — no second transaction is created. A capture that timed out after it may have reached the card network is reversed — the capture, never the authorization under it: while that reversal is open (REVERSAL_PENDING), a same-operation_id retry gets 409 tx:invalid-state-transition; once it clears, the hold is back to AUTHORIZED and the retry is sent as a new capture attempt. A capture that timed out before it left RadiumOne is sent as a new attempt on a same-operation_id retry — nothing was sent the first time. A void that timed out is reversed too: while that reversal is open, a retry gets 409 transaction:void-reversal-pending (retry_allowed: true); once it clears, the sale is back to CAPTURED and the retry is sent as a new attempt. While that earlier capture, void, or refund is unresolved, a follow-up with a different key on the same transaction gets 409 urn:radiumone:payment-gateway:tx:followup-outcome-in-doubt: resend the pending request first. See Handle timeouts and unknown outcomes.
Balance inquiry also takes a request_id field, but it isn’t an idempotency key — there’s no dedup or replay store. Every call re-queries the rewards host, even with the same request_id.
Keys are 8–64 characters, [a-zA-Z0-9-] only, unique per merchant account. Generate one key per order attempt and persist it to your database before you send the first request — never mint a new key just to retry the same attempt. See Prevent duplicate payments.
PENDING means the outcome isn’t known yet — most often after a processor timeout. Don’t assume success or failure. Recover it one of two ways:
  1. Wait for a webhook (payment.*, authorization.*, refund.* — see Webhook event types).
  2. Poll GET /v1/transactions/{id}/status — it returns the transaction as RadiumOne holds it. Poll every 60 seconds while it reads PENDING or REVERSAL_PENDING, and contact support if it isn’t final 60 minutes after your server sent the original request; INCONSISTENT means stop and contact support; anything else is final. See Check a transaction’s status.
If you don’t have the transaction id yet — a client-side timeout before the first response arrived — replay the same purchase, authorize, or refund with the same request_id and body. The replay is a lookup, not a resend: it returns the stored transaction and its id, whatever status it’s reached, including PENDING or REVERSAL_PENDING. A capture or void replayed with the same operation_id works the same way, and for a capture, void, or referenced refund whose outcome wasn’t recorded, RadiumOne checks with the card network before sending anything. Never re-submit with a new idempotency key just because the first attempt is slow — that risks a second charge for the same order. Capture responses are 200, including retries — a replayed capture with the same operation_id returns the same 200 result as the first attempt. If the outcome is unknown — no response, or any 5xx, even one that says retry_allowed: false — replay the identical capture with the same operation_id. The replay is a lookup, not a resend: RadiumOne returns the outcome it recorded, and if the capture reached the card network but the outcome wasn’t recorded, it asks the network for the stored outcome instead of capturing again. It sends the capture only if the network never received it. If the capture timed out after it may have reached the card network, RadiumOne reverses that capture — never the authorization under it — and reports authorization.capture_failed. While the reversal is open the transaction reads REVERSAL_PENDING, and a retry with the same operation_id gets 409 tx:invalid-state-transition: wait and retry. Once the reversal clears, the hold is back to AUTHORIZED (no webhook is sent for this), and your retry with the same operation_id is sent as a new capture attempt. RadiumOne doesn’t capture it again on its own. A capture that timed out before it left RadiumOne is sent as a new attempt too — nothing was sent the first time. Never mint a new operation_id for the same capture attempt.
operation_id replays never compare the request body. A retry with the same operation_id returns the original captured result even if the amount you sent this time is different — the original amount wins, silently. Use a new operation_id for a genuinely new operation. Reusing a capture’s operation_id for a void on the same transaction is rejected with 409 urn:radiumone:payment-gateway:tx:duplicate-operation, not treated as a replay.

Errors

Full HTTP status and meaning for each of these is defined once on Problem format and retries — this list is only the capture-specific nuance:

Webhook

A successful capture emits payment.captured. A capture that fails at the acquirer, or times out, emits authorization.capture_declined or authorization.capture_failed — the hold survives and you can capture it again. See Webhook event types.

Test your integration

See Test your integration for capture-window and decline scenarios.

Go-live notes

  • Capture as soon as you can fulfil — don’t hold authorizations open longer than necessary.
  • Replay a timed-out capture, or one that got a 5xx, with the same operation_id; check GET /v1/transactions/{id}/status if you’re unsure whether it went through.
  • Review the full go-live checklist.

Next steps

Payment lifecycle

See how capture fits into the full transaction lifecycle.

Void a payment

Cancel a captured payment before its batch closes.
Last modified on October 25, 2026