Fusion Payments is the fastest way to launch and scale subscription billing for your video service. Whether you're running a streaming platform, selling premium video courses, or launching a pay-per-view event, Fusion makes it easy to integrate secure, Stripe-powered payments — without writing custom billing logic or maintaining complex backend systems.

We’ve built Fusion to do the heavy lifting, so you can focus on what matters most: your content and your customers. With just a few lines of code, you can present pricing options to users, securely redirect them to a Stripe-hosted checkout page, and automatically grant access once payment is complete. No need to worry about PCI compliance, session management, or webhooks — Fusion handles it all for you.

Whether you're just getting started or scaling to thousands of subscribers, Fusion grows with you. Our API-first approach gives you the flexibility to design your own frontend while relying on our robust backend to manage sessions, pricing, and user access.

Guides

Step-by-step walkthroughs for setting up your first payment flow, integrating Stripe Checkout, handling success pages, and more.

API Reference

Complete technical documentation for Fusion’s endpoints, request/response formats, and authentication requirements.

API for managing monetization operations and proxying Stripe calls.

IMPORTANT NOTE ON ERROR HANDLING: This API uses a non-standard error handling pattern in its /v1 endpoints, where most errors return HTTP 500 status code regardless of the error type. The actual error type is indicated by the errors field in the response. Check the ApiError schema for the list of error strings. Exceptions to this pattern are explicitly noted in individual endpoint descriptions.

Authentication

This API uses two primary authentication methods:

• API Key - All calls must be made with your Fusion API Key in the X-API-KEY header
• JWT Token - All calls specific to a user e.g. checkout sessions and subscriptions must also contain a valid JWT token in the Authorization header in the format ‘Bearer TOKEN’. This token must contain the ‘sub’ claim which serves as the unique ID for the customer across the Fusion system.