Recurring rebilling
Recurring rebilling architecture directs subsequent merchant-initiated transactions through optimal acquirer partner routes. Cardflo evaluates decline codes and orchestrates smart payment retries, increasing transaction approval rates for high-volume operators without requiring manual finance team intervention.
- Category
- Subscriptions
- Capabilities
- 10
- Available on
- All plans
Cardflo's recurring rebilling capabilities ensure consistent revenue for subscription models. We manage the complexities of repeated payment attempts, card updates, and decline recovery.
This system is designed to minimise payment friction and maximise the lifetime value of your subscribers.
Cardflo automates the renewal of recurring payments, employing smart retry schedules and card updater services to overcome rebilling challenges. This method secures crucial subscription revenue and preserves the health of merchant accounts.
Recurring rebilling overview
Recurring rebilling involves the automated processing of subsequent transactions based on a pre-authorised mandate between a merchant and a customer. This mechanism sits within the merchant service provider layer of the payments stack, utilising Merchant Initiated Transactions (MIT) to execute scheduled captures.
Effective rebilling requires a robust framework to manage the lifecycle of a subscription, including the initial authorisation, subsequent settlement cycles, and the inevitable card lifecycle events that cause friction. By synchronising with card scheme account updaters and employing specific decline recovery strategies, merchants can maintain continuity without requiring manual customer intervention for every billing cycle.
The process relies on secure tokenisation to store sensitive cardholder data, ensuring compliance with PCI DSS standards while allowing the PSP to submitt authorisation requests to the acquirer at defined intervals. This infrastructure is essential for subscription-based businesses seeking to minimise involuntary churn and stabilise cash flow.
How recurring rebilling works
Initial mandate and tokenisation
The process begins when a customer completes a Customer Initiated Transaction (CIT) through 3DS verification. The payment gateway generates a secure token that replaces the primary account number. This token, along with a mandate ID, allows the merchant to initiate future rebilling attempts without re-collecting sensitive payment details from the cardholder.
Scheduled authorisation request
On the predefined billing date, the system sends an authorisation request to the acquirer using the stored token. This request must be flagged as an MIT to inform the issuer that the cardholder is not present. The transaction includes the original authorisation reference to comply with scheme requirements for recurring payments.
Automated card updates
Prior to the scheduled rebilling, the system queries card scheme databases for changes in credit or debit card statuses. If a card has expired or been replaced due to loss, the Account Updater service retrieves the new details. This ensures the rebilling attempt uses current credentials, reducing soft declines.
Intelligent retry logic
If an authorisation fails due to temporary reasons like insufficient funds, the system executes a retry strategy. These attempts are timed to coincide with typical cycles of liquidity, such as common paydays. Each attempt is tracked to ensure the merchant stays within the limits permitted by card schemes for retries.
Why recurring rebilling matters
Control of involuntary churn
A significant portion of subscription cancellations results from payment failures rather than active customer choice. Issues such as expired cards, technical timeouts, or temporary credit limits cause service interruptions. A structured rebilling framework identifies the specific decline reason and applies the appropriate recovery tactic, such as dunning or card updates, which helps maintain the customer relationship without needing a new acquisition cycle.
Operational efficiency and settlement
Manual billing processes are prone to errors and do not scale with business growth. Automating the rebilling cycle ensures that settlement occurs promptly and that revenue is recognised in the correct accounting period. By using standardised identifiers for recurring transactions, merchants also benefit from more predictable processing costs and reduced manual overhead in managing accounts receivable and payment reconciliation.
Recurring rebilling use cases
Streaming renewal traffic peaks
Streaming services can submit millions of low-ticket merchant initiated transactions after midnight or around major content releases, creating gateway congestion and clusters of soft declines. Cardflo orchestrates traffic across its acquirer partner network and schedules targeted retries using issuer response codes, rather than repeatedly presenting unrecoverable hard declines.
High-volume SaaS subscription billing
SaaS vendors rebilling annual enterprise licences often encounter expired corporate cards, temporary expenditure controls or issuer declines on large merchant initiated transactions. Cardflo applies network tokenisation and account updater data where available, then uses decline-aware retry logic and multi-acquirer routing to recover eligible payments without resubmitting hard declines.
Publisher access renewal continuity
Digital publishers depend on low-ticket monthly rebilling to preserve paid access, but replaced cards and stale credentials can cause avoidable issuer declines at renewal. Cardflo supports network tokens and updated credentials, distinguishes soft from hard decline codes, and routes permitted merchant initiated transaction retries through suitable acquirer partners.
Membership rebilling after soft declines
Fitness apps and online coaching services face soft declines when monthly membership charges meet temporary insufficient funds, issuer velocity controls or authentication history gaps. Cardflo sequences retries according to response codes and prior transaction context, while gateway orchestration directs merchant initiated transactions to an appropriate acquirer partner without repeatedly attempting terminally declined cards.
Recurring rebilling by the numbers
This is a typical industry range for merchants who implement automated card updaters and intelligent retry logic compared to those with basic billing.
General industry data suggests that a majority of expired or replaced cards can be successfully updated through scheme services, assuming the issuer participates.
Standard recovery rates for soft declines when using staggered retry attempts over a 14-day cycle, varying by industry and customer demographic.
Methodology: these figures are illustrative ranges drawn from published industry data and observed merchant cohorts, not guarantees. Actual results depend on your risk profile, card mix, geography and acquiring setup, and are confirmed only in your own pricing and approval terms.
Related terms
Talk to our team about a live rollout across our acquirer partners' rails.
What you get with Recurring rebilling
- Automated tokenisation of payment credentials for secure storage and subsequent Merchant Initiated Transactions.
- Integrated card account updater services to refresh expired or replaced card details automatically.
- Customisable retry schedules based on specific decline codes and issuer response analysis.
- Support for multiple currencies and local payment methods within a single rebilling framework.
- Dunning management tools to organise customer notifications following a failed payment attempt.
- Detailed reporting on recurring revenue metrics including churn rates and recovery success benchmarks.
- Compliance with PSD2 and SCA requirements for the initial customer authorisation mandate.
- Configurable billing cycles to support weekly, monthly, quarterly, or bespoke subscription intervals.
- Automatic adjustment of rebilling amounts to accommodate discounts, taxes, or tiered pricing changes.
- Standardised transaction flagging to ensure correct processing by issuers and reduced refusal rates.
A short scoping call, then a written plan for your MIDs.
Questions about Recurring rebilling
How does rebilling work under PSD2 and SCA regulations?
Under PSD2, the first transaction in a recurring series must be a Customer Initiated Transaction (CIT) that undergoes Strong Customer Authentication (SCA), typically via 3DS. Once the customer has authorised the mandate, subsequent payments are classified as Merchant Initiated Transactions (MIT).
These MITs are out of scope for SCA, provided the merchant correctly flags them and uses the original transaction ID. This allows for scheduled rebilling to occur without the customer being present to provide a second factor of authentication.
What is the difference between a soft decline and a hard decline in rebilling?
A soft decline occurs when a transaction is refused for temporary reasons, such as insufficient funds or a technical timeout. These transactions can often be successfully retried later.
A hard decline is a permanent refusal, often due to a stolen card, closed account, or an invalid BIN. Hard declines should not be retried, as doing so can lead to penalties from card schemes like Visa or Mastercard for excessive retry behaviour.
A rebilling system distinguishes between these two to optimise recovery efforts.
How does recurring rebilling decide when to retry declined transactions?
Recurring rebilling evaluates the decline category, issuer response, previous attempt history and permitted retry window before scheduling another authorisation. Temporary conditions may justify a later attempt, while definitive responses should end automated retries.
Cardflo’s gateway orchestration applies merchant-defined rules across recurring flows and records each outcome, helping revenue operations teams analyse recovery performance without repeatedly submitting transactions that are unlikely to succeed.
What happens when a customer's card expires in a subscription model?
When a card expires, the rebilling attempt will result in a decline code specifically indicating an expired card. To prevent this, merchants use Account Updater services provided by the card networks.
These services allow the PSP or gateway to query the network for the new card number or expiry date linked to the original account.
The system then updates the stored token with the new details, allowing the next rebilling cycle to proceed without the customer needing to update their account manually.
Can rebilling amounts be changed without a new mandate?
Yes, if the initial mandate and terms of service allow for variable amounts, a merchant can adjust the rebilling figure. However, the transaction must still be flagged correctly as a recurring MIT.
Significant increases in the amount may sometimes trigger an issuer's fraud filters, so it is best practice to notify the customer in advance of the price change to reduce the risk of a retrieval request or a chargeback for a disputed amount.
What is dunning management and how does it relate to rebilling?
Dunning is the process of methodically communicating with customers to recover declined payments. In a rebilling context, dunning starts immediately after a soft decline.
The system may send an automated email or SMS informing the customer of the failure and providing a link to update their payment method.
This coordinated approach between retry logic and customer communication is the primary way to reduce involuntary churn and ensure the subscription remains active.
Related features.
Related guides.
See how Cardflo compares.
From the blog
The subscription model provides predictable revenue through recurring fees for SaaS and streaming services. While it fosters long-term customer loyalty, businesses must manage higher acquisition costs and potential churn. This approach offers stability for companies providing ongoing value through continuous access to products. It is designed to generate a steady income stream and build relationships.
Read articleSubscription payments are a specific subset of recurring billing where customers pay at the start of each cycle. These automated payments occur at weekly, monthly, or annual intervals until the service is terminated. This model helps businesses reduce churn and secure predictable revenue while helping customers budget effectively. It is an ideal system for strengthening long term loyalty.
Read articleA recurring payment is an automated billing system where a customer authorises a business to charge their card or bank account at regular intervals. This model is common for gym memberships, insurance premiums, and streaming services. It provides convenience for consumers while ensuring consistent revenue for service providers. Payments occur at fixed or variable amounts without manual customer input.
Read articleReady to improve your payments setup?
Tell us about your business. We'll match you with the right acquiring partners and the right route, typically inside a week.