Billing for something bought by the request.
Selling an API means the invoice is a function of what somebody's cron job did last month, and the key has to stop working the moment the card does. Usage charges, plan tiers and webhook-driven entitlements are how that gets wired.
00 - core API resources you can drive it all from
00 +- payment methods for your customers
00 % + 50¢- the only charge
- $
00 - monthly fee on a quiet month
The shape of an API business

Tiers plus what went over them
A plan with an included allowance, then pay-as-you-go beyond it. One-off charges can be applied to a live subscription, so an overage does not have to wait for the next billing date.

Keys follow the subscription
Your issuer listens to the payment and subscription webhooks and switches the key on and off. A failed renewal degrades access on its own instead of being noticed in a month's revenue report.

Developers self-serve or they leave
Upgrades, downgrades, card updates and invoices in a branded portal on your own domain. A developer who has to email sales to raise a rate limit is a developer evaluating someone else.

Your customers are companies
Business buyers who enter a tax ID at checkout get a proper invoice by email, on the first charge and on every renewal — which is what their finance team will ask for before they can expense it.
Wiring billing to your API
- 01
Model the tiers
A product with an offer per tier, plus a usage price for the requests beyond the allowance.
- 02
Sell from your docs
The overlay opens over the pricing page in your documentation site, so an evaluating developer never leaves it.
- 03
Issue the key on the webhook
payment_success is the signal that money arrived. Mint or activate the key there, server-side.
- 04
Revoke on the way out
Cancellation and failed-payment events are what should throttle or disable a key, rather than a manual review.
You could do all of this yourself
Selling digital goods across borders means registering for tax in each market, wiring up a tax engine, and answering for every dispute. As your Merchant of Record, that is our name on the paperwork instead of yours.
What you get to skip building
- Metered pricing
- Pay-as-you-go and usage-based plans, without writing a rating engine or a monthly invoice job.
- Proration on tier changes
- Moving between plans mid-cycle is worked out to the day, and the next renewal can be previewed through the API first.
- Signed webhooks
- Payment success, refunded and failed, plus subscription created, interval, updated and cancelled — with retries and delivery history.
- A REST API over everything
- Products, offers, orders, payments, subscriptions, users, discounts and webhooks at api.fungies.io/v0.
- Invoices for business buyers
- Issued automatically when a tax ID is supplied at checkout, on the first charge and on each renewal.
- Global tax, filed
- VAT, GST and sales tax under our registrations as Merchant of Record, recalculated on every renewal.
5% + 50¢
per sale, and nothing else
Negotiable at higher sales volume.
No monthly fee. No minimum. No card to get started.
One rate covers the whole stack. There is no tier that unlocks tax filing and no add-on for the store builder.
- ✓ Payment processing
- ✓ Tax calculation and filing
- ✓ Fraud screening
- ✓ Chargeback handling
- ✓ Store builder and hosting
- ✓ Every platform feature
Teams like yours, already shipping
All customer stories →TextToVideo.bot
Weeks of payment work, done in minutes
An AI video generation platform launched its subscription business without writing a payment integration at all.
RenderAI
From days of integration to a couple of minutes
An AI image platform replaced a slow manual payment process with three subscription tiers and an overlay checkout.
Leadsin.io
A hosted checkout with no payment infrastructure to build
A lead generation platform started taking monthly and yearly subscriptions without standing up any payment infrastructure of its own.
API product questions
Charge for the API without building a rating engine
Model the tiers, wire the webhook to your key issuer, and run a full cycle in sandbox before anyone is billed.





