Migration from CloudPay to Fusion + Stripe Checkout
Overview
If you are currently on our legacy CloudPay API, this guide outlines what is being replaced with the new Fusion API, which integrates directly with Stripe Checkout and Stripe Customer Portal. This migration greatly simplifies integration by reducing custom API endpoints and shifting more functionality into Stripe’s hosted flows.
🔧 Technical Differences at a Glance
Topic | Cloudpay Flow | NEW Fusion + Stripe |
Auth | JWT in query param | JWT in `Authorization: Bearer` + `x-api-key` |
Sessions | /sso/start, /terminate | No sessions — JWT expiry controls access |
Products | /package endpoint returns plans | /products` returns products, features, prices |
Entitlements | CustomerEntitlements / Packages | Features via subscriptions |
Checkout | /checkout + Stripe Elements | /checkout-session → redirect to hosted Checkout |
Discounts | /discount endpoint | Stripe Coupons created in dashboard |
Account | /account, /billing-update, /cancellation | Stripe Customer Portal |
Transactions | /transaction API | Stripe webhooks + Checkout Session API |
IAP | Supported via /verify | Not supported — validate directly with Apple/Google/etc or via an integration. |
✅ Key Takeaways
- Fusion offloads flows to Stripe, cutting down custom code.
- Hosted Stripe Checkout and Customer Portal now cover most user interactions.
- IAP require external configuration.
- JWT + API key auth replaces CloudPay sessions.
What made this section unhelpful for you?
On this page
- Migration from CloudPay to Fusion + Stripe Checkout