Payment orchestration
iyzico, Paddle or a bank transfer? Payment orchestration decides which provider takes each payment and follows the result to the end. Payrudder picks the provider by the customer's country and currency. Every charge runs as a saga, and if the provider's answer is unclear it is checked before any retry.
What you get
- Paddle, iyzico and bank transfer behind one provider contract
- Routing rules by customer country and subscription currency
- Move a subscription between providers without two being live at once
- A payment ledger reconciled against the invoices
How it works
- 1Connect your own provider accounts
- 2Write routing rules for countries and currencies
- 3Payrudder charges, retries where needed and records the result

Questions
Are the Paddle and iyzico integrations production-ready?
The adapters are written from the providers' documentation and tested against fixtures. They have not been run against the providers' sandboxes yet. The roadmap lists what needs a real account.
Does Payrudder open my Paddle account?
No. You open the Paddle and iyzico accounts yourself and Payrudder connects to them with API keys. Payrudder has no influence on the outcome of your Paddle application.
Who retries a failed payment?
Paddle is the merchant of record and runs renewals and retries itself. For iyzico, Payrudder schedules the charges and the retries.
Other features
- Usage meteringSend usage as it happens. Every event is counted once, even when your client retries.
- Subscription billingMonthly or yearly plans, trials, upgrades with a preview, coupons, tax rates and invoice pages.
- Multi-tenant billingRun billing for many apps from one account. Each app has a sandbox and a live environment with its own keys.
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.