Skip to main content
Elements runs entirely in the browser up to the point your server receives a token, so a shopper’s own network conditions — offline, a flaky connection, or a blocked request — can interrupt tokenization independently of anything the gateway does.
TL;DR: submit() rejects with urn:radiumone:elements:card:bind-network-unreachable or urn:radiumone:elements:card:iframe-timeout → offer the shopper one manual retry, and confirm the session hasn’t expired first.

When this happens

  • The shopper’s connection drops or times out while the card iframe is binding the card with RadiumOne. The iframe retries the bind itself first.
  • The card iframe doesn’t answer the page within 55 seconds, for example because it failed to boot or a Content Security Policy or browser extension blocked it.
  • The page isn’t served over HTTPS (outside localhost), or crypto.randomUUID isn’t available — Elements requires a secure context.

What you see

What to do

1

Serve your checkout page over HTTPS

urn:radiumone:elements:card:insecure-context means the page itself isn’t secure — fix the page’s protocol; there’s nothing to retry. localhost is exempt for local development.
2

Offer one retry, not a loop

Show a “try again” button rather than resubmitting automatically. Branch on the whole code, and on retryAllowed for anything else:
  • urn:radiumone:elements:card:bind-network-unreachable (retryAllowed: true): the bind never got a response, so a retry is safe.
  • urn:radiumone:elements:card:iframe-timeout: the bind may have succeeded before the iframe went quiet. A retry with the same card returns the token that already exists, so it doesn’t bind twice. Offer one retry; if it times out again, check that your CSP and the shopper’s extensions aren’t blocking the card iframe.
3

Check the session before retrying

If the shopper waited a while before retrying, confirm the session hasn’t expired first — see Handle expired sessions and card tokens. A network retry into an expired session just produces a second, different error.
4

Stop after one retry

The SDK and the card iframe already retry the bind internally before submit() rejects. If your one manual retry fails too, point the shopper at a page reload rather than retrying again.

Prevent it

  • Don’t self-host or proxy the SDK script or iframe through your own infrastructure — load it directly from RadiumOne’s CDN so the shopper’s browser talks to RadiumOne directly, without an extra network hop that can fail.

Handle Elements failing to load

Network failures at SDK load time, before any card field exists.

Install and load Elements

Secure-context and browser-support requirements.
Last modified on September 29, 2026