Describe what you sell
A catalogue of products, plans and packs. Free, recurring or one-time: the rules start with your model.
Monetisation, from the product side
Subscriptions, usage, credits, licences. Connect what your customers buy to what your product lets them do.
Your rules in sayAllow. Payments in Stripe.
A clear product contract, from payment to access.
A place for every rule
A payment doesn’t tell your application how many people to invite, which feature to unlock or which quota to apply. sayAllow makes that connection.
A catalogue of products, plans and packs. Free, recurring or one-time: the rules start with your model.
Connect subscriptions, features and quotas to an organisation. Your backend reads effective entitlements when they matter.
Payment events update the state. Your product receives callbacks and can read the current situation from the API.
Your model, your choice
Build your monetisation around the value your product delivers.
Access that lasts
A plan, a billing cycle and a set of entitlements. Let customers choose a subscription and evolve what it includes.
Example plan · illustrative values
Clear responsibilities
sayAllow coordinates billing and entitlements. Stripe handles payment pages and payment methods.
The experience, the users and the value you create.
Plans, subscriptions and the contract for product access.
Hosted Checkout, payments and the billing portal.
The product key stays on your server. Card data stays with Stripe.
Beyond Checkout
For installed software, an API or a hosted application, signed licences carry your customers’ entitlements. Validation fits into backends and deployed environments.
Understand entitlements and licencesAn integration you can follow
Configure your catalogue, connect an organisation, then start the right flow from your backend.
Read the integration guideproduct + plansorganizationfree / checkoutentitlements + usageLet your plans evolve