Model plans, trials and offers once, then take payment through Stripe or Apple in-app purchases without writing receipt-validation code.
Every task works three ways, and all of them change the same project. Here's one: a monthly plan with a seven-day free trial.
The Anythink dashboard
Fill in the plan once. It syncs to Stripe when Connect onboarding is complete.
The Anythink CLI
Plans go through the AnythinkPay API, so a script can create them.
Claude, through MCP
Describe the plan. It calls the same API and reports what it created.
you › “Create an AnythinkPay subscription plan called Pro monthly at £9.99 a month with a 7-day trial.”
Idempotent by design
Apple receipt verification keys off the purchase's original_transaction_id. Re-verifying the same purchase, or a renewal coming back around, updates the existing row instead of creating a second subscription.
A timely reason to avoid extensions
After that date, Firebase Extensions can't be installed or edited, which pushes Stripe and Apple IAP handling on Firebase into custom Cloud Functions. Anythink's payment handling is native, not an extension that can be deprecated.
| Capability | Anythink | Supabase | Firebase |
|---|---|---|---|
| Stripe subscriptionsSupabase: Stripe sync engine or a webhook recipe. | Built in | Add-on, extension or DIY recipe | |
| Apple in-app purchasesFirebase: via the RevenueCat extension, which Extensions sunsets 31 March 2027. | Built in | Not available | Add-on, extension or DIY recipe |
| Server-side receipt verification | Built in | Not confirmed | Add-on, extension or DIY recipe |
| Admin recovery (status override, resync) | Built in | Not confirmed | Not confirmed |
● Built in◐ Add-on, extension or DIY recipe– Not available? Not confirmed
Sourced from each vendor's own docs as of 28 September 2026. "Addon" means an extension, plugin or code recipe rather than a feature of the core platform.
Plans, trials, discount codes, Stripe and Apple in-app purchases, all on the same subscriber record.
Define subscription plans with billing intervals and trial periods, then layer on offer and discount codes for redemption and referral programmes.
In practice
POST https://api.my.anythink.cloud/org/{org_id}/integrations/anythinkpay/subscription-plans Content-Type: application/json { "plan_name": "pro-monthly", "name": "Pro Monthly", "description": "Full access, billed monthly", "amount": 19.00, "currency": "gbp", "billing_interval": "month", "trial_period_days": 14 }
What you can build
Sell a subscription through Apple in-app purchase. Anythink verifies the receipt against the App Store, binds it to the signed-in account, and keeps renewals from duplicating the entitlement. Your app just asks /me whether access is active.
Set a trial period on the plan, so new subscribers get full access for 14 days before the first Stripe charge. Offer codes extend a trial or discount the first invoice for a referral programme.
Route a buyer's payment to a seller through Stripe Connect and take a percentage automatically. Configure the split once; every transaction after that follows it.
Get Stripe's enterprise-grade payment processing with Anythink's simple setup. From your first sale to scaling globally, handle payments like the pros without the complexity.