mode: "embed", RadiumOne Checkout posts messages to the parent page via window.postMessage. Every message shares one envelope:
Origin rules
- Listen for
messageevents and filter onevent.originequal to the RadiumOne Checkout host your session’scheckout_urlwas served from. - RadiumOne only posts to your page’s origin if that origin is in your registered
allowed_domains. On browsers that exposewindow.location.ancestorOrigins(Chrome, Safari), the real parent-frame origin is used; Firefox doesn’t expose it, so RadiumOne falls back to the origin derived from yoursuccess_url— make sure that origin matches your embedding page.
Events
The payment was approved (
status: "completed"), or the card was only held and not captured (status: "authorized"). Advisory only — confirm with your server before fulfilling.The payment outcome isn’t known yet (asynchronous processing). Wait for a webhook or poll your server.
The session’s TTL elapsed while the shopper was submitting payment. If a charge was already in flight, the session’s
decline_reason is "expired_while_processing": the outcome is unknown and the charge may have gone through, so wait for the payment.* webhook or poll the transaction status, and fulfil only on payment.captured — see Session expired mid-payment. A session that expires while the shopper is idle posts nothing until they try to pay.A payment attempt ended in an error. Advisory only — confirm the session’s status server-side. See
CHECKOUT_ERROR types for what each type means, and Handle payment service outages during checkout.There is no
CHECKOUT_CANCELLED event today — a shopper closing or navigating away from the iframe does not post a message. See Handle abandoned checkouts for how to detect this case instead.