Choose a collection flow
Use this page to decide how customers should enter a Radom payment experience before you start building.
Radom supports several customer-facing collection flows. The right one depends on who should host the payment experience, how much UI you want to own, and whether the payment starts from a cart, a reusable link, or a customer-specific billing request.
Quick comparison
| Flow | Best for | Who hosts the customer page | Start here |
|---|---|---|---|
| Hosted checkout | Fastest production launch | Radom | Hosted checkout |
| Integrated checkout | Product-owned payment UI | Your application | Integrated checkout |
| Payment links | Low-code or reusable collection pages | Radom | Payment links |
| Invoicing | Customer-specific billing requests | Radom | Invoicing |
How to choose
Use hosted checkout when
- You want the shortest path to production.
- Radom can host the customer payment page.
- Your team prefers webhook-driven reconciliation over building the payment UI yourself.
Use integrated checkout when
- The customer should stay inside your own product UI.
- Your application needs to render payment instructions directly.
- You already control cart state, order state, and customer identity in your own app.
Use payment links when
- You need a reusable payment page without building a storefront.
- Operations, support, or sales teams will share the same collection link repeatedly.
- The collection flow should be quick to launch from the Dashboard.
Use invoicing when
- The payment request starts with a named customer and a payable billing record.
- You want invoice status and customer context in the same flow.
- Operations teams need clearer invoice lifecycle handling than a generic payment page.
Before you go live
- Confirm the public networks and tokens you want to expose in Supported payment methods.
- Decide whether you need reusable Products and pricing before launching the flow.
- Connect webhooks before production use.