API for managing monetization operations and proxying Stripe calls.

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.

These endpoints allow you to return Stripe products and prices to display to your users so that they can purchase them. They are all accessible using your Fusion API key and do not require a JWT token from the user.

Returns all active products from Stripe that are available in the geo location of the customer. If desired, a set of IDs can be passed as a query parameter to return only those specific products.

Key Fields:

• name - The product name, for display to customers
• description - Extra information about the product e.g. ‘Season pass for all games’
• marketingFeatures - This is an array of extra information strings that you can display to the customer, letting them know what features this product grants e.g. ‘Presale ticket access’, ‘Eclusive interviews’ etc.
• prices/defaultPrice - These are the available prices for your product, and will also be automatically filtered by geo location. To create a checkout session, you make a call to create-checkout-session using the ID of the price you wish to charge the user. Prices will either be of type ‘one_time’ or ‘recurring’ and will contain information about their billing and how long they give access. Currencies will also be served according to the customer's geo location if this has been set up with us by your account manager.
• features - Not to be confused with marketingFeatures! These features specify what entitlements are granted to the customer when they purchase this product. e.g., if the Paid Access feature is attached to this product, a customer will get Paid Access for the duration they are paying for this product. Similarly, if instead, the feature is for a PPV event, e.g. Liverpool V Man Utd Match Pass, they will gain access to just that entitlement instead. The featureId of these features, can be compared against the user subscription response to check if a customer already has access to a feature granted by the product, so you can prevent them accidentally buying the same thing twice, for example.

Please see the get all products section for more details on returned fields.

Please see the get all products section for more details on returned fields.

These endpoints allow you to perform monetization operations, and proxy through the Stripe, a world leading payment platform that is the technology underpinning of Fusion monetization. Here you will find endpoints for creating checkout sessions, retrieving checkout information and giving access to the customer portal.

These endpoints are for the checking of customer entitlements, establishing what a customer has access to and what products they should be able to purchase.

/