Introduction
Paylera is a billing and payments platform for SaaS, marketplaces, and any business that needs recurring revenue, multi-currency invoicing, and a real ledger behind it. You point Paylera at your catalog and your payment provider, and we own the rest of the monetisation lifecycle.
What Paylera does for you
Once a customer enters Paylera, the platform owns:
- Catalog — products, plans, and components, with as many price models as you need (flat, per-unit, tiered, volume, package, usage-based).
- Subscriptions — trials, commitments, proration, upgrades, downgrades, pause / resume, cancellation, renewal.
- Invoicing — pricing, discounts, tax, finalisation, PDFs, re-issues.
- Payments — provider-tokenised methods, 3DS / SCA, refunds, chargebacks, smart retries (dunning).
- Wallets — prepaid credit, auto-top-up, settlement against open invoices.
- Multi-currency — presentment vs settlement currency, locked FX rates, FX gain / loss postings.
- Revenue recognition — deferred revenue scheduled across the service period, recognised on close.
- Affiliate payouts — attribution, commissions, batched payouts with hold periods.
- Webhooks — every state change emitted as a typed, signed event.
- Audit log — every operator action recorded with required reason.
You point us at one or more payment providers (Stripe, PayPal, Adyen, …), plug into our webhook stream, and ship.
Who it’s for
- SaaS companies with subscriptions, seats, and metered usage.
- Marketplaces that need split payments, affiliate commissions, and payouts.
- Multi-region products that bill in many currencies and need a real ledger to close the books.
- Teams that have outgrown Stripe Billing for Subscriptions, ChartMogul for revenue, and a homegrown dunning script.
What this site covers
| Section | What you’ll find |
|---|---|
| Get started | Sign up, sandbox, first call, first subscription, going live. |
| Billing concepts | The mental model behind every API call. |
| Integration guide | Recipes for each step of launch. |
| Webhooks | Listening to state changes. |
| API conventions | The shapes that hold across every endpoint. |
| Resources | Per-object lifecycle and field reference. |
| Security & compliance | PCI scope, encryption, DSR. |
| SDKs & tooling | Official clients and the OpenAPI document. |
Stability
The Public API is versioned by date (Paylera-Version: YYYY-MM-DD) and is
backwards-compatible within a version. Breaking changes ship behind a new
dated version with at least 12 months of overlap, an RFC 8594 Sunset
header, and a migration guide. See Versioning.