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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
The key is to distinguish the type of decline:
| Decline type | What it usually means | Typical approach |
|---|---|---|
| Hard decline | Card cancelled, lost or invalid | Don't retry; ask the customer for a new payment method |
| Soft decline | Insufficient funds, limit reached, temporary issuer refusal | Retry in a different time window, within limits |
| Technical error | Network or provider failure | Retry immediately or through another route |
| Authentication required | The issuer demands customer verification | Take 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.
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.
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.
A recognizable billing descriptor, advance renewal notices, a simple cancellation process and dispute-alert tools reduce subscription chargebacks.
If you only look at overall acceptance rate, rebills get diluted. These metrics give a useful picture:
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.