Subscriptions · Rebills

Why Subscription Payments Fail and How to Recover Them (Involuntary Churn)

TL;DR In a subscription business, the first charge converts the customer, but the charges that follow (rebills) sustain the business. A rebill can fail for very different reasons: an expired or replaced card, insufficient funds, issuer fraud suspicion or a technical misconfiguration. The levers that usually have the most impact are: flagging recurring payments correctly (MIT), using network tokens and automatic credential updates, designing a smart retry strategy, and measuring rebill acceptance rate separately from first-charge acceptance rate. What isn't measured separately can't be optimized.

Why Rebills Are a Different Problem From the First Charge

The first payment is made by a present customer, on their device, who can authenticate (for example with 3D Secure). The rebill is initiated by the merchant with no customer involvement. That difference changes everything:

That is why rebills should be measured and optimized as a flow of their own.


The Main Challenges of Recurring Payments

1. Involuntary Churn

This is the loss of subscribers who didn't want to leave: their charge failed and the service was cancelled. In many subscription businesses it makes up a significant share of total cancellations, and it is the most recoverable because the customer hasn't decided to go.

2. Credentials That Stop Being Valid

Cards expire, get lost, replaced or reissued with a new number. If you store the card number as is, each of those situations is a failed rebill.

3. Incorrect Flagging of Recurring Transactions

Card schemes distinguish between customer-initiated transactions (CIT) and merchant-initiated transactions (MIT). If a rebill is not sent as an MIT referencing the original transaction, the issuer may treat it as an ordinary unauthenticated payment and decline it, or apply requirements that don't fit.

4. Digital Wallets and Device Tokens

With Apple Pay or Google Pay, the stored token may be bound to the device (DPAN) and not valid for merchant-initiated recurring charges. For subscriptions, a token tied to the merchant's account (MPAN) is usually preferable. If the payload isn't configured to request it correctly, the rebill can fail even though the first payment went through.

5. Poorly Designed Retries

Retrying without criteria carries two risks: failing to recover payments that were recoverable (by waiting too long or retrying at the wrong time) and, at the same time, exceeding the retry limits set by the schemes, with possible fees or penalties. Exact limits vary by network and change over time, so verify them against each scheme's current documentation.

6. Issuer Fraud-Suspicion Declines

Some issuers decline rebills with generic risk codes. Often it isn't real fraud but a lack of context, and it can be improved with better data, tokens and correct flagging.

7. Chargebacks and Monitoring Programs

In subscription models, disputes over charges the customer doesn't recognize are common (unclear descriptor, forgotten subscription, unexpected renewals). Schemes monitor dispute and fraud ratios per merchant; exceeding thresholds can bring fees and remediation obligations. Prevention is cheaper than correction.

8. Regulatory and Scheme Changes

Strong customer authentication (SCA) in Europe, easy-cancellation and renewal-notice rules, and periodic Visa and Mastercard rule updates directly affect how a recurring flow is structured. They should be reviewed regularly.


How to Recover Failed Payments: The Highest-Impact Levers

Flag the Transaction Correctly (CIT and MIT)

The first payment should be made as a customer-initiated transaction, with authentication when required, and record the intent to charge later. Subsequent rebills should be sent as MIT, referencing the original transaction according to your provider's and the scheme's requirements. Everything else builds on this foundation.

Use Network Tokens

Network tokens (such as those offered by Visa and Mastercard) replace the card number with a credential that updates automatically when the card changes or expires. They reduce declines caused by stale credentials and usually improve approval rates compared with storing the PAN directly. Availability depends on your provider and the network.

Automatic Credential Updates

If you don't use network tokens, some schemes offer card-data update services (account updater) so you receive new numbers and expiry dates before the next charge. Ask your acquirer whether it supports this and how to enable it.

A Smart Retry Strategy

The key is to distinguish the type of decline:

Decline typeWhat it usually meansTypical approach
Hard declineCard cancelled, lost or invalidDon't retry; ask the customer for a new payment method
Soft declineInsufficient funds, limit reached, temporary issuer refusalRetry in a different time window, within limits
Technical errorNetwork or provider failureRetry immediately or through another route
Authentication requiredThe issuer demands customer verificationTake the customer through an authentication flow

Beyond the decline type, timing matters: day of the month, proximity to payday or time of day can influence approval. What works for your business is found by measuring, not assuming.

Dunning: Communicate Well With the Customer

When a charge fails, notify the customer with a clear message and a simple link to update their payment method. Well-designed recovery emails and notifications turn declines into collected payments without manual effort. Also offer a reasonable grace period before suspending the service.

Routing and Multi-Acquirer

If the same rebill is declined at one acquirer, another may approve it. A payment orchestrator lets you retry through alternative routes while respecting each scheme's rules, provided tokens are portable or properly managed.

Chargeback Prevention

A recognizable billing descriptor, advance renewal notices, a simple cancellation process and dispute-alert tools reduce subscription chargebacks.


What to Measure to Optimize Rebills

If you only look at overall acceptance rate, rebills get diluted. These metrics give a useful picture:


Common Mistakes in Subscription Businesses


Frequently Asked Questions About Subscriptions and Rebills

What is a rebill?
A recurring charge that follows the first payment of a subscription, initiated by the merchant without customer involvement at that moment.
What is the difference between CIT and MIT?
A CIT (customer-initiated transaction) is started by the customer, for example the first payment. An MIT (merchant-initiated transaction) is started by the merchant, such as a later monthly charge, relying on the authorization established in the original transaction.
What is involuntary churn?
The loss of subscribers whose cancellation was not their decision but the result of a failed charge (expired card, insufficient funds, issuer decline).
How many times can a declined payment be retried?
It depends on the decline type and on each card scheme's rules, which limit retries and change over time. Check current limits with your acquirer or provider.
Do network tokens improve rebill acceptance rate?
They usually help because they update automatically when the card changes or expires and give the issuer more confidence, although the result depends on your provider, your customer base and the network.
Why do recurring payments fail with Apple Pay or Google Pay?
A frequent cause is a device-bound token being generated that is not valid for merchant-initiated charges. The request must be configured to obtain a credential suited to recurring payments.

Are Your Rebills Failing More Than They Should?

If you run a subscription business and don't know how much you are losing on rebills or why, at PayScaling we analyze your recurring flow: MIT flagging, tokenization, retries and decline reasons by issuer, and deliver an action plan prioritized by impact.

The Payments Diagnostic costs €250 + VAT.

Request a Payments Diagnostic →

PayScaling is a boutique payments optimization consultancy for e-commerce, specialized in improving acceptance rate, reducing acquiring costs and optimizing payment stacks.