Plans, checkout, proration, dunning, invoices and EU VAT, on your own payment account. The plan and payment status land in the user's token, so one guard in your API checks them offline.
Launch paid plans without writing a subscription system or keeping it in sync with your users.
An organisation's owners and admins manage the subscription for the whole team.
Reverse charge for businesses, OSS rates for consumers, and VAT numbers checked against VIES.
Connect your Adyen account for cards and SEPA Direct Debit. You are the merchant; your money never passes through us.
Plans, prices and entitlements made in the dashboard. Upgrades apply now with proration, downgrades at the period end.
Failed payments are retried, and the token's status says past_due, so your app can show a banner.
Invoice PDFs, EU VAT with reverse charge and OSS, and refunds from the dashboard.
A guard's plan and entitlement checks answer 402 plan_required, so your app can offer the upgrade.
Subscription, invoice and payment events, and an admin client for your backend.
When a user signs in, their token carries who they are, their organisation and role, their plan and payment status, and what your flags target. Your API checks it in one guard, offline, and your UI reads the same answers.
sub · amrorg.rolebilling.planflag()The user pays on the payment page and comes back to your app. From the next token refresh, the plan and its entitlements are in the token your API checks.
// In the browser: the user picks a plan and pays on your payment account
const { plans, subscription } = await auth.billing.get();
const { url } = await auth.billing.checkout({ price: 'pro_monthly' });
location.href = url!; // back in your app, the next token carries the plan
await auth.billing.change('max_monthly'); // upgrades now (prorated), downgrades at the period end
// In your API (the server SDK): plan and entitlement in one guard, offline. Not on it: 402 plan_required
app.get('/api/reports/export',
api.require('report:read', { plan: ['pro', 'max'], entitlement: 'export' }),
exportReports);This will be its own product, sold separately from the plans. It is not sold yet. Want to use it? Talk to us.
You are. Charges run through your own Adyen account and settle there. Anchr.ing runs the plans, invoices and VAT around them.
The subscription goes past due and the payment is retried. The plan still applies meanwhile, and the token's billing status tells your app to show a banner.
Yes. Test environments include billing, so you can build and test the checkout before you go live.
Set up plans in the test environment, wire up the checkout, and go live when your payment account is ready.
Hosted sign-in, organisations, roles and enterprise SSO.
Teams, invites, custom roles and org switching, with the role in the token.
Targeting and rollouts, evaluated offline from the token.
Talk to your users beside their plan, roles and flags.
Act as a user with a reason, a time limit and an audit trail.
Chat with visitors, and keep them when they sign up.