Embedded Payments for SaaS & Platforms

Recurring billing starts with a customer authorizing a saved payment method, then charging it on a schedule as plans renew. Complexity comes from the details: free trials that convert to paid, upgrades and downgrades with proration, annual and monthly plans, taxes, coupons and multiple currencies.

Subscription charges are typically merchant-initiated, so the customer is not present to authenticate each one. That makes the initial authorization important, and it is why card network rules around stored credentials and clear consent matter. Keep renewal reminders, receipts and cancellation easy to reach, since confusion about charges is a common source of disputes.

Involuntary churn happens when a paying customer loses access because a renewal fails. Causes include expired or replaced cards, insufficient funds, issuer declines and temporary technical errors. Many of these can be recovered with the right process.

Dunning combines retries with customer communication. Retries are spaced according to the type of decline, since a hard decline such as a closed account should not be retried repeatedly, while a soft decline may succeed later. Card updater services can refresh expired details automatically, and emails or in-app prompts let customers fix payment details themselves. Alternative methods such as bank debits can help where cards fail often. Results depend on your customer base, so track recovery by decline reason. Our guide to improving approval rates covers the principles.

Usage-based and hybrid pricing add a measurement step. You need reliable usage records, a billing period, clear invoice line items and a way to handle disputes about usage. Larger customers often want invoices and purchase order references rather than card charges, so the stack should support both.

Software platforms that serve other businesses have an extra layer. They may onboard sub-merchants, split each payment between platform and customer, and pay out balances. That brings KYC, reporting and liability questions, so agree early who is responsible for what. See the payment gateway for the core API and marketplaces for split payments and payouts in more depth.