Get going

Pick your starting point

Whichever way you're integrating, you'll be sending live API calls in under an hour.

Quickstart

Sign up, grab a sandbox key, and create your first subscription with a handful of curl commands.

Hosted checkout

Send customers to a Paylera-hosted page that handles plan selection, payment method capture, and 3DS — no PCI scope on your servers.

API-first integration

Drive the entire flow from your backend: customer, plan, payment method, subscription, invoice, payment.

The model

Concepts that show up everywhere

Read these once and the rest of the API reads itself.

Products & plans

Build your catalog: products group what you sell, plans price it.

Pricing models

Flat, per-unit, tiered, volume, package, usage-based — combine them per plan component.

Subscriptions

The lifecycle that turns a plan into recurring revenue: trials, renewals, upgrades, pauses, cancellations.

Invoices

Pricing, discounts, tax, finalisation. Per-line rounding at minor units. Immutable once issued.

Payments & dunning

Provider-tokenised methods, 3DS / SCA, refunds, smart retries when a charge fails.

Webhooks

Every state change emits a typed event. Signed, ordered per aggregate, delivered at-least-once.

Build the flow

Integration guides for the common paths

Step-by-step recipes for the things you'll actually do during launch week.

Onboard a customer

Create the customer, attach a billing address, capture a payment method.

Create a subscription

Pick a plan, set the trial, attach the payment method, handle the first invoice.

Report metered usage

Send usage events for seats, api_calls, anything you meter. Late events tolerated; idempotency enforced.

Receive webhooks

Verify signatures, process the typed envelope, ack with 2xx. We retry with backoff if you don’t.

Handle 3DS / SCA

The payment.requires_action problem document points at the next step. Resume after the customer authenticates.

Refund a payment

Full or partial. Refunds emit credit notes and re-post the ledger automatically.

Engineered for trust

Built to the bar of money-moving production

The hard parts — idempotency, FX, recognition, audit, RLS — are not features you opt into. They're the floor.

Idempotent everywhere

Every money-moving route requires Idempotency-Key. Replays return the original response byte-for-byte.

Multi-currency, real ledger

Invoices carry presentment + settlement currency, locked FX rate, and an explicit FX-gain/loss leg in the ledger.

Revenue recognition

Deferred revenue scheduled across the service period. Period close in one call. ASC 606-shaped exports.

Audit log on every admin action

Required reason, recorded actor, stable entity hash, exportable. AAL2 elevation for the dangerous moves.

PCI scope: SAQ-A

Card data flows through provider-tokenised methods. We never see PAN or CVV. You inherit our scope reduction.

OpenAPI 3.1, dated versions

Paylera-Version: YYYY-MM-DD. New optional fields freely; breaking changes ship behind a new dated version with overlap.