Payment operation errors - Payments API

You’ll hit these on purchase/authorize, capture, void, and refund calls. Branch on the problem+json type URN and HTTP status returned in the body — never on title, which is a display label. See Problem format and retries for the response shape, the full HTTP status guide, and retry rules. The Retry? column says whether to resend the request, following those rules and the linked recovery page.

Auth and validation

Credential, scope, and request-body problems — see Fix rejected or expired access tokens for the walkthrough.

URN	HTTP	Meaning	What to do	Retry?
`urn:radiumone:gateway:validation-error`	400	Body failed schema validation — see Validation error details for the per-field `errors` array	Fix the request body against the schema	No
`urn:radiumone:auth:insufficient-scope`	403	Your key’s token lacks the scope this operation requires	Fix rejected or expired access tokens	No
`urn:radiumone:auth:outlet-binding-violation`	403	The key is bound to a different outlet than the one requested	Fix rejected or expired access tokens	No
`urn:radiumone:gateway:token-expired`	401	Your access token expired	Fix rejected or expired access tokens	Once — after re-exchanging or refreshing the token
`urn:radiumone:gateway:token-invalid`	401	Your access token failed verification	Fix rejected or expired access tokens	Once — after re-exchanging or refreshing the token; if it fails again, treat it as a configuration problem

Idempotency

request_id and operation_id reuse conflicts — see Handle replays and idempotency conflicts for the full walkthrough.

URN	HTTP	Meaning	What to do	Retry?
`urn:radiumone:transaction:idempotency-body-mismatch`	409	Same `request_id`, different body — or the same `request_id` reused for a different operation type	Handle replays and idempotency conflicts	No — never safe to retry as-is; resend the stored original body, or mint a new key for a genuinely new attempt
`urn:radiumone:tx:duplicate-operation`	409	Same `operation_id` reused for a different operation on the same transaction	Handle replays and idempotency conflicts	No — use one `operation_id` per operation

Transaction state (capture, void, refund)

Batch-state and lifecycle conflicts on a capture, void, or refund. See Handle capture failures and Resolve void and refund conflicts.

URN	HTTP	Meaning	What to do	Retry?
`urn:radiumone:tx:capture-window-expired`	422	Capture attempted after the window closed	Handle capture failures	No
`urn:radiumone:tx:capture-amount-mismatch`	422	Capture `amount` doesn’t equal the authorized amount	Handle capture failures — must equal the authorized amount exactly	No
`urn:radiumone:tx:currency-mismatch`	422	`amount.currency` on a capture or refund doesn’t match the original transaction’s currency	Capture an authorization and Refund a payment	No
`urn:radiumone:tx:auth-expired-during-capture`	409	The authorization expired mid-flight, racing your capture	Handle capture failures	Depends — see Retry rules
`urn:radiumone:tx:void-on-non-open-batch`	409	Void attempted after the batch closed	Resolve void and refund conflicts — refund instead	No
`urn:radiumone:tx:refund-on-open-batch`	409	Refund attempted while the batch is still open	Resolve void and refund conflicts — void instead	No
`urn:radiumone:tx:amount-exceeds-captured`	422	Refund `amount` exceeds what’s left (original minus prior refunds)	Resolve void and refund conflicts	No
`urn:radiumone:tx:refund-window-expired`	422	The refund window has elapsed since capture/settlement	Resolve void and refund conflicts	No
`urn:radiumone:tx:refund-target-not-refundable`	422	The target transaction is no longer eligible (already refunded in full, voided)	Resolve void and refund conflicts	No
`urn:radiumone:tx:invalid-state-transition`	409	The transaction’s state doesn’t allow the operation you requested	Resolve void and refund conflicts	Depends — see Retry rules
`urn:radiumone:transaction:void-reversal-pending`	409	A void was refused because an earlier void on the same sale hasn’t resolved yet	Resolve void and refund conflicts — check the transaction status for the earlier void’s outcome before voiding again	Yes, later — transient; only if the sale still isn’t voided

Automatic reversals

See Understand automatic reversals for the full walkthrough.

URN	HTTP	Meaning	What to do	Retry?
`urn:radiumone:transaction:reversal-limit-exceeded`	409	A reversal is stuck after repeated attempts	Understand automatic reversals — contact support	No

Next steps

Problem format and retries

The problem+json shape, HTTP status guide, and retry rules.

Payment method errors

Loyalty, discovery, routing, and token errors.

Decline codes

How a declined payment appears — that’s not an error.

Handle failures

Find the right recovery page by symptom.

Introduction

Guides

Payment methods

3D Secure

Handle failures

Webhooks

Errors

Reference

Payment operation errors - Payments API

Auth and validation

Idempotency

Transaction state (capture, void, refund)

Automatic reversals

Next steps

Problem format and retries

Payment method errors

Decline codes

Handle failures

​Auth and validation

​Idempotency

​Transaction state (capture, void, refund)

​Automatic reversals

​Next steps

Problem format and retries

Payment method errors

Decline codes

Handle failures

Auth and validation

Idempotency

Transaction state (capture, void, refund)

Automatic reversals

Next steps