elements.submit() itself — the gateway rejects the bind call, and submit() rejects with an ElementsError whose code is the problem type URN (urn:radiumone:payment-gateway:* or urn:radiumone:tokenization:*), verbatim. Charge-time token errors happen later, on your server’s purchase/authorize call, when a token that bound successfully has since expired.
Tokenization (bind) errors
Fromelements.submit()’s bind call: the gateway’s (urn:radiumone:payment-gateway:*) or tokenization service’s (urn:radiumone:tokenization:*) problem type, passed through as code verbatim.
The gateway decides whether each error can be retried and the SDK passes that through as retryAllowed on the error — branch on it at runtime, and follow Merchant action below.
409 urn:radiumone:tokenization:session-card-limit-reached means the session has reached its limit of 3 cards, counting the first.
Terminal: nothing is charged, and only a new session helps. A session where the switch is
allowed also binds a different card instead of returning session-not-bindable. See
Switch to a different card.
For the recovery pattern behind these, see Handle tokenization failures; for the bind-rate-limit and session-not-bindable cases specifically, see Prevent double submission.
Charge-time token errors
These come from your server’s purchase/authorize call, not fromsubmit() — the token was valid at bind time but lapsed before you charged it. urn:radiumone:payment-gateway:token:transient-expired and urn:radiumone:payment-gateway:token:data-purged are defined once, on the Payments API — see Payment method errors: Tokens for the HTTP status and meaning.
See Handle expired sessions and card tokens for the full recovery steps.
Next steps
Error object and handling
The
ElementsError shape and the standard catch pattern.SDK and integration errors
Codes thrown before you ever reach the bind call.
3D Secure errors
Codes from
authenticate(), handle(), and resume().Handle failures overview
Find the right recovery guide by symptom.