A subscription business lives on the second payment, not the first. The first is a customer choosing to buy. Every payment after that is a charge to a stored card, and each one can fail for reasons the customer never chose: an expired card, a new card number, a temporary decline or a limit reached.
A white label payment gateway for subscription businesses gives a PSP, or a platform serving subscription merchants, the tools to keep those renewals going under its own brand. This page covers why renewals fail, how recovery works, the rules that are changing, and what to configure.
Why renewal payments fail
Most renewal failures are involuntary. The customer still wants the service, but the payment doesn't go through, and unless the merchant's systems catch it, the customer churns without ever having decided to leave. The table shows the common causes and what fixes each one.
| Cause | What happens | What fixes it |
|---|---|---|
| Expired or replaced card | The stored card number no longer works | Network tokens and card updates that keep the stored credential current |
| Soft decline | The issuer declines for a temporary reason, such as funds | Retries on a schedule that avoids hammering the card |
| Hard decline | The card is closed or the account is blocked | Asking the customer for a new payment method |
| Authentication required | The issuer wants the cardholder to authenticate | A customer-initiated flow for that payment, then back to automatic renewals |
The first two rows are where software recovers the most revenue. They need no action from the customer, so a good setup fixes them before the customer even notices.
How dunning and retries recover revenue
Dunning is the process of retrying failed payments and contacting the customer when retries don't work. It pays.
A subscription merchant has 20,000 subscribers paying $15 a month, so $300,000 of renewals a month. If 6% of renewals fail at first, that's $18,000 at risk each month. A retry schedule that recovers half of those payments brings back $9,000 a month, or $108,000 a year, from customers who never meant to leave.
The schedule matters as much as the retries. Trying again on the same day the card declined rarely works, while spacing attempts over several days, at different times, gives temporary problems time to clear.
The UK's new subscription rules
Regulation is catching up with renewals. The UK's Competition and Markets Authority says in its draft guidance that new subscription rules apply to consumer subscription contracts entered into on or after January 1, 2027, with the regulations still subject to parliamentary approval when the guidance was published.
For a PSP serving subscription merchants, that means merchants will ask for clearer renewal reminders and accurate records of what each customer agreed to. The gateway's job is to keep the payment side of those records complete and easy to export.
What to configure for subscription payment processing
The setup below covers the renewal side end to end.
- Store cards as tokens, with network tokenization where the card schemes support it.
- Set up the subscription plans each merchant needs, including trials, upgrades and downgrades.
- Define the retry schedule for soft declines, per merchant.
- Route renewals that fail on one acquirer to another, where the decline reason allows it.
- Send customer notices for failed payments and upcoming renewals through the merchant's channels.
- Report recovered, failed and cancelled renewals in the merchant dashboard.
Step 4 only helps when the PSP has more than one acquirer. With a single acquirer, the retry schedule and card updates do most of the work.
Choosing a white label payment gateway for subscription businesses
Picking the top white label gateway for recurring payments means testing the renewal flow rather than the first checkout. Ask how stored cards stay current, how the retry schedule is set and per whom, and whether failed renewals can be routed to a second acquirer.
Our checkout keeps tokenized cards up to date for recurring payments, and the platform automates recurring billing, refunds, partial settlements, add-ons and plan changes, with dunning that recovers failed payments.
Questions
What is a white label payment gateway for subscriptions?
Gateway software a PSP or platform runs under its own brand to process recurring payments for subscription merchants, with stored cards and dunning built in.
Why do subscription payments fail?
Mostly for involuntary reasons: expired or replaced cards, temporary declines and authentication requests. Hard declines, where the card is closed, are less common.
How do PSPs reduce failed renewals?
With network tokens and card updates, well-spaced retries, routing to a second acquirer where possible, and notices that ask the customer for a new card when nothing else works.