Checkout Flow
Use this page to understand and verify checkout from the provider dashboard.
For production storefront implementation details, see Build a Storefront.
In the Dashboard
Use Store or Store Preview to verify products, devices, checkout mode, redirects, and purchase confirmation.
- Open Marketplace.
- Select the marketplace instance.
- Open Provider.
- Open Store or Store Preview.
- Select one or more listed products.
- Select devices from the provider organisation or enter device IDs manually.
- Choose live or test checkout mode.
- Create the checkout session.
- Open the returned checkout URL.
- Complete or cancel the Stripe checkout.
- Return to Purchases to confirm purchase state.
Checkout States
| State | What it means |
|---|---|
| Session created | Infuse created a hosted Stripe Checkout session and returned a checkout URL. |
| Redirecting | The browser is leaving your site or dashboard for Stripe Checkout. |
| Cancelled | The customer returned to the cancel URL. The basket can remain editable. |
| Pending confirmation | The customer returned to the success URL, but purchase state has not become active yet. |
| Active purchase | Infuse has validated payment, recorded the purchase, and created the entitlement. |
| Ready to install | A compatible release is available for the purchased product and device. |
Live and Test Mode
Use test mode for previews, QA, and demos. Use live mode only when you intend to create production purchase records.
The dashboard labels the selected checkout mode. Confirm the mode before opening the checkout URL.
After Checkout
- Open Purchases.
- Filter by device ID or marketplace item.
- Confirm the purchase status.
- Open the device page when you need to review compatible releases or queue an install.
What Happens Behind the Scenes
The checkout session contains:
- selected device IDs,
- selected marketplace item IDs,
- success and cancel URLs,
- checkout mode.
Infuse creates the hosted Stripe Checkout session and returns a checkout URL. The customer completes payment on Stripe. Infuse validates successful payment, records purchase state, and creates the relevant entitlements.
Treat the success redirect as a return to your site, not proof that fulfillment has completed. Always read purchase state from Infuse after the redirect.
For Custom Storefronts
Custom storefronts create checkout sessions from the provider backend. Keep provider credentials server-side, validate selected devices before checkout, and read purchase state after redirect. See Build a Storefront for the full integration flow.