For SaaS, AI and API products selling from Türkiye
Usage-based billing with no cut of your revenue
Payrudder counts the tokens, API calls or GB each customer uses and issues the invoice at month end. Local cards are charged through iyzico, international sales go through Paddle and enterprise customers pay by bank transfer. Turkish e-invoices go out through Nilvera. You pay us a fixed monthly plan. The payment provider's fee is separate.
- Free plan to start
- Fixed monthly plan
- iyzico, Paddle & bank transfer
- e-Invoice via Nilvera

Parts you won't have to build yourself
- Usage metering
- Subscriptions
- Trials
- Invoices
- Credit notes
- Coupons
- Tax rates
- Customer portal
- Payment links
- Credit packs
- Payment retries
- Signed webhooks
- Revenue & MRR reports
- e-Invoice
- Paddle
- iyzico
- Bank transfer
How it works
From your customer's first API call to money in your account
01Meter
Count whatever you sell
Tokens, API calls, GB-hours or a unit you define. Your app sends usage events and Payrudder totals them per customer. You can see what each customer has used so far in the console.
- Five aggregations: SUM, COUNT, MAX, UNIQUE, LAST
- Late usage isn't lost, it lands on the next invoice as an adjustment line
- An event sent twice is counted once

02Bill
Changing a price shouldn't be a project
Subscription, trial, coupons and usage prices live in one package. When you change a price you can re-rate the closed month and bill only the difference. Your customer sees which usage each invoice line came from.
- Monthly or yearly plans with usage on top
- Credit notes and invoice pages your customer can open
- Re-rate a closed month and bill only the difference

03Collect
Get paid with methods that work in Türkiye
Turkish lira card payments go through iyzico. International sales go through Paddle, which handles tax there as merchant of record. If an enterprise customer pays by bank transfer, it lands in the same ledger. You open the Paddle and iyzico accounts yourself and Payrudder connects to them.
- Routing rules by customer country and currency
- Move a subscription from one provider to another
- A payment ledger reconciled against invoices
Payrudder routes each payment to Paddle, iyzico or bank transfer and sends e-invoices through Nilvera. 04Grow
Stop checking three dashboards for revenue
No need to open iyzico, Paddle and your bank statement side by side at month end. Revenue, MRR and failed payments for all your apps sit in Payrudder, split by provider and country.
- Reports by provider, country and currency
- Test and live side by side
- Console in six languages

On every plan
The months of billing work you get to skip
Invoice issued, payment collected, receipt sent
When a period closes, the PDF invoice is generated, the payment is charged through the provider and the receipt goes to the customer. If a step stalls it resumes where it stopped. If the provider gives no clear answer, Payrudder asks for the result before retrying, so the same payment isn't charged twice.
Test before you go live
Every app has a test environment with a payment simulator. Close a month in seconds and look at the invoices it produces.
Coupons, credit packs and refunds
Discount coupons, prepaid credit packs, refunds to the card or to a credit balance. Tax is applied at the rate you set per customer country. Payrudder is not a tax engine.
Invoice pages and a portal for your customers
Every invoice has its own page and PDF. The customer portal and payment links open in your customer's language.
Receipts and reminder emails
Payrudder sends the invoice, receipt and payment-failed emails. For payments taken through Paddle, Paddle sends the receipt and Payrudder doesn't send a second one. Your app gets every event through signed webhooks.
Numbers your accountant can trust
Revenue, MRR and unpaid invoices are matched to individual payments. No hunting for differences between the dashboard and the bank statement at month end.
Keep each product separate
Selling more than one product? Run them all from one account. Each app has its own customers, API keys and test environment.
Use cases
For products that charge by use
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 caseBilling for many apps
Run billing for every product you own from one account.
See the use case
Pricing
Your price is set by monthly collections and metered events
Start free. You pay for how much of the system you use, and we take no cut of your revenue. The payment provider's fee is separate.
Pay for 10 months
Free
Try it with your first real payments
$0/mo$0/yr
Get early accessIncluded every month
- collections
- 50 collections
- metered events
- 50K metered events
- emails
- 300 emails
- storage
- 1 GB storage
- event rate
- 50/s event rate
- Plan
- 1 app
Starter
For your first paying customers
$19/mo$190/yr
Get early accessIncluded every month
- collections
- 300 collections
- metered events
- 1M metered events
- emails
- 1,000 emails
- storage
- 5 GB storage
- event rate
- 200/s event rate
- Plan
- 3 apps
- Recommended
Growth
For products that are starting to grow
$59/mo$590/yr
Get early accessIncluded every month
- collections
- 1,000 collections
- metered events
- 5M metered events
- emails
- 3,500 emails
- storage
- 25 GB storage
- event rate
- 1,000/s event rate
- Plan
- 10 apps
Scale
For high volume
$199/mo$1,990/yr
Get early accessIncluded every month
- collections
- 5,000 collections
- metered events
- 40M metered events
- emails
- 16,000 emails
- storage
- 100 GB storage
- event rate
- 5,000/s event rate
- Plan
- Unlimited apps
Enterprise
Custom limits and a contract
from$599/moContract
Get early accessIncluded every month
- collections
- 20,000 collections
- metered events
- 200M metered events
- emails
- 60,000 emails
- storage
- 250 GB storage
- event rate
- Custom event rate
- Plan
- Unlimited apps
Invoices, PDFs, invoice pages, retries, receipts, webhooks, refunds and credit notes on every plan.
Payrudder Cloud is in early access. Compare all plans
From the blog
Guides to usage-based billing
· 10 min read
What is usage-based billing? A practical guide
Usage-based billing charges customers for what they actually use. Learn the pricing models, the hard parts, and whether to build it or buy it.
Read more →· 9 min read
LLM token billing: how to charge without losing margin
LLM token billing ties your AI revenue to inference cost. Pick a billable unit, choose a pricing pattern, set limits and alerts, and keep your margin.
Read more →· 9 min read
What is payment orchestration? A guide for SaaS
Payment orchestration routes each payment to the right provider by country and currency, retries safely without double charges and keeps one ledger.
Read more →
FAQ
Pricing, providers and getting started
What is Payrudder?
A billing service for products that charge by use. It meters usage, runs subscriptions, issues invoices and collects payments through Paddle, iyzico or bank transfer. Revenue reports are included.
Which payment providers does it work with?
Paddle, iyzico and bank transfer. Paddle is the merchant of record, so it handles tax abroad and renewals itself. With iyzico, Payrudder schedules the charges and retries. You open the accounts and Payrudder connects to them with API keys.
Can I sell to Turkish and international customers at the same time?
Yes. A routing rule picks the provider by the customer's country and currency, for example iyzico for Turkish lira and Paddle everywhere else.
Can I use it instead of Stripe?
Partly. Stripe doesn't open accounts for companies registered in Türkiye. Payrudder does the metering and subscription work Stripe Billing does, while iyzico and Paddle charge the card. For international sales you need an approved Paddle account.
Does it work for AI and API products?
Yes. You meter whatever you sell, such as tokens, calls or GB-hours, with exact decimal quantities. Your app can check a customer's limit in milliseconds, and an alert fires once when a threshold is reached.
How are e-invoices issued?
A UBL-TR e-invoice is generated from the same invoice data and sent through Nilvera. The integration is written, and a run against Nilvera's test portal is on the roadmap.
What counts as a collection?
A successful live payment: a card charge, a confirmed bank transfer, a payment link or a credit pack purchase. Failed attempts, refunds and test-mode payments are not counted.
Do you take a share of my revenue?
No. Plans are priced on collections and metered events. We don't take a percentage of what you bill. Paddle's and iyzico's own fees are separate.
When can I start?
Payrudder Cloud is in early access. Leave your email through the form and we will set you up.
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.
Contact
Talk to us
Early access, a demo, pricing questions or a provider you need. We answer by email.
Another way to reach us
We answer every message by email, usually within two working days.