Skip to main content
These are the codes you hit while wiring up Elements — a bad publishable key, an Element that isn’t mounted, a duplicate Element, or a call made out of order. Every one is an ElementsError (see Error object and handling); catch it and branch on the whole err.code URN. Integration and SDK codes come from the SDK itself, synchronously or from submit(); Iframe-relayed codes are surfaced from inside the card iframe but arrive the same way, as err.code on the ElementsError submit() rejects with.
Your server’s API calls. Elements pages write them as the full path on the API host, as the SDK publishes them — for example, POST /gateway/v1/sessions is https://api.radiumone.io/gateway/v1/sessions (sandbox: https://api-sandbox.radiumone.io/gateway/v1/sessions). The Payments API reference lists the same operations relative to that base URL: POST /v1/sessions, PATCH /v1/sessions/{session_id}, GET /v1/payment-methods, POST /v1/transactions/purchase.

Integration and SDK codes

Thrown for programming errors and environment issues (urn:radiumone:elements:init:* and urn:radiumone:elements:card:*). Fix the integration rather than retry, unless noted. For the specific symptoms these codes map to, see Fix publishable key errors (the urn:radiumone:elements:init:* codes), Fix card fields that don’t render (container-not-found, element-destroyed, duplicate-element), Prevent double submission (submit-in-progress, submit-too-soon), and Handle browser network errors (iframe-timeout: offer one retry, since a retry with the same card returns the token that already exists).

Iframe-relayed codes

Surfaced from inside the card iframe. Treat an unrecognized code as a generic failure that isn’t retryable unless retryAllowed is true. Retry guidance for the codes you’re most likely to see:
  • urn:radiumone:elements:card:bind-network-unreachable (retryAllowed: true): the bind got no response. Offer a retry — see Handle browser network errors.
  • urn:radiumone:elements:card:expiry-missing / urn:radiumone:elements:card:cvv-missing: nothing was sent, so a retry is safe. If it repeats (for example on Safari before 15.4), treat it as final — see Split-field relay failures.
  • urn:radiumone:elements:card:overlay-blocked: nothing was sent. Retry once the modal or overlay covering the card field is closed.
  • urn:radiumone:elements:card:submit-too-soon: a repeat call within 1 second of a successful submit — see Prevent double submission.
The rest resolve the same way as a tokenization failure — see Handle tokenization failures.

Next steps

Error object and handling

The ElementsError shape and the standard catch pattern.

Tokenization errors

Bind-time gateway errors from submit().

3D Secure errors

Codes from authenticate(), handle(), and resume().

Handle failures overview

Find the right recovery guide by symptom.
Last modified on September 29, 2026