Skip to main content

Hosted checkout

Radom hosted checkout is the fastest way to launch a customer-facing crypto payment flow while keeping the payment UI hosted by Radom.

When to use hosted checkout​

  • You want the shortest path to production.
  • You want Radom to host the payment experience and quote handling.
  • You still want dashboard visibility and webhook-based reconciliation.

Typical flow​

  1. Create a checkout session from your backend.
  2. Redirect the customer to the hosted checkoutSessionUrl.
  3. Let the customer pay on one of the public network and token combinations you exposed.
  4. Use webhooks as the source of truth for fulfillment and reconciliation.
  5. Optionally send the customer back to your success or cancel URL for UX continuity.

Before you start​

Create a checkout session​

Create checkout sessions from a secure backend. A session can be built from products, ad-hoc line items, or both.

{
  "successUrl": "https://merchant.example/payments/success",
  "cancelUrl": "https://merchant.example/payments/cancel",
  "gateway": {
    "managed": {
      "methods": [
        {
          "network": "Ethereum",
          "token": "0xa0b86991c6218b36c1d19d4a2e9eb0ce3606eb48"
        }
      ]
    }
  },
  "lineItems": [
    {
      "productId": "ff20f359-f170-4b88-b59c-9ef4c7aa097b"
    }
  ]
}

Use the checkout session API reference for the full request schema and related endpoints.

Use the session response​

Store the checkoutSessionId in your own system so you can reconcile later webhook events against the order or customer journey that created the session.

Use the checkoutSessionUrl to redirect the customer to the hosted payment page.

{
  "checkoutSessionId": "<UUID>",
  "checkoutSessionUrl": "https://pay.radom.com/checkout/<UUID>"
}

Reconciliation and launch notes​

  • Redirect URLs are helpful for user experience, but webhooks should be your source of truth for fulfillment.
  • You can create sessions from products, ad-hoc totals, or mixed line items depending on how much pricing logic you want in your own system.
  • Hosted checkout is usually the best fit when you want Radom to own the payment page rather than rendering payment instructions yourself.

See also​