One billing account for every app you build
If you build more than one product, each one wants its own billing code. Payrudder gives every app its own sandbox and live environment inside one account, and you manage them all from the same console. NAFRU runs its own apps this way.
The hard part
- 01
Every new product repeats the same billing work
- 02
One product's data must not mix with another's
- 03
You still want to see revenue across all of them
How Payrudder handles it
An app is a tenant
Each app has a sandbox and a live environment with keys of its own. Row-level security keeps their data apart.

Configured per app
Metering, subscriptions, providers and e-invoices are configured per app, so each product prices the way it needs.

Team and reports shared
Switch between apps, invite your team and see each app's revenue and invoices.

Features used
- Multi-tenant billingRun billing for many apps from one account. Each app has a sandbox and a live environment with its own keys.
- Subscription billingMonthly or yearly plans, trials, upgrades with a preview, coupons, tax rates and invoice pages.
- Payment orchestrationRoute each payment to iyzico, Paddle or bank transfer by the customer's country and currency.
Questions
Can each app use a different currency or provider?
Yes. Currency, time zone, providers and routing rules are set per app.
Does one app's test environment affect another?
No. The sandbox and live environment are per app. A transaction made with a test key doesn't show up in live reports.
Billing for AI products
Meter tokens, images or minutes per customer and bill what was used.
See the use caseAPI usage billing
Charge per call or by tier. Quota checks take milliseconds.
See the use caseSelling SaaS from Türkiye
Local cards through iyzico, international sales through Paddle, one billing system.
See the use case
Start billing by usage
The free plan covers your first live payments. Hook up one meter, close a month in test mode, then go live.