Quick Answer
To keep subscribers through a 90-day closure notice, open a replacement credit card merchant account early, request a card token transfer, and run old and new billing side by side.
Subscription records do not move between processors. Plans and schedules have to be rebuilt. A hard cutover at the deadline puts every renewal at risk on the same day. SeamlessChex serves 60+ industries, including subscription and high-risk businesses other processors turn away. My preference is to add bank debit as a second rail once card renewals clear on the new account.
Key Points
- In Redux's analysis of subscription accounts, published June 2026, 77.9% of credit card subscribers were still active at 90 days, versus 49.5% for debit and 24.9% for prepaid.
- After Paddle stopped supporting AI products in February 2025, NovelAI moved subscribers through an in-app migration link and offered an unspecified bonus incentive for switching on their own.
- SeamlessChex works with established businesses processing at least $25,000 per month, offering same-day onboarding and no contracts on a replacement credit card merchant account.
Running old and new billing side by side keeps renewals clearing while subscribers move to the new account.
A closure notice does not cancel a single subscription. It cancels the account those subscriptions bill through, and that difference decides how many customers are still paying when the window shuts.
Monthly recurring revenue, which one retention text calls "arguably the most important indicator of future business success," rises or falls with every renewal that clears or fails during a switch.
My brother Evan and I founded SeamlessChex in 2012 to help businesses move money, and credit card processing for subscription and recurring billing businesses sits at the center of that work. This guide is written for operators who have the notice in hand and need a plan, not reassurance. Inside, in the order the problems arrive:
- How many subscribers a business already loses to failed payments before any switch
- Where subscribers actually fall out when billing moves to a new processor
- What can move to a new processor (saved card tokens) and what cannot (plans and schedules)
- How to get a recurring billing credit card merchant account approved before the deadline
- What will decide how many subscribers survive the next forced exit
None of it is exotic. Developers who have moved subscription billing between processors describe the token handoff as achievable but slow, and one put it plainly in a 2021 forum thread: "It's no small task."
Card processing carries the replacement. Bank debit sits behind it as a second rail, on a network that carried 35.2 billion payments valued at $93 trillion in 2025.
Where I come down: the deadline that decides retention is the last renewal the outgoing processor will run, not day 90, and that date belongs in writing before any other work starts. Just as important, one named person should own subscriber messages for the whole window, so customers hear about the switch from the business before anyone else tells them.
A 90-day closure notice gives a subscription business one real asset: time to move recurring billing while the old account still charges renewals. I read that notice as a project plan with a due date. The first question to put to any provider of a replacement credit card merchant account is whether it approves subscription businesses that another processor has just closed.
Involuntary churn is subscriber loss caused by failed payments rather than cancellations. One subscription retention guide lists failed payments alongside product flaws and network failures as the moments customers expect a business to step in and help. A forced processor exit creates that moment for every subscriber at once.
Even a planned switch can stumble. When an AI storytelling company announced it was moving subscribers off Paddle in 2025, its new processor still had JCB and Discover cards not working, so some customers could not finish the migration they were being asked to make. Test card brands, recurring plans and customer prompts before the first renewal moves.
Card processing should carry the replacement, with a bank-debit rail behind it. Nacha describes scheduled, recurring payments between known counterparties on known due dates as "well served by ACH." Which subscribers need that second rail depends on how many a business is already losing before any switch begins.
How many subscribers does a business already lose to failed payments?
Before any migration, a typical subscription business already loses 20-40% of its churned subscribers to failed payments, so a processor switch adds risk to an existing leak.
Before you plan the switch, measure the leak you already have. Four numbers set your baseline:
- Your monthly retention rate, held against a healthy benchmark.
- Your failed renewals per billing cycle, split into recovered and lost.
- Your mix of prepaid, debit and credit cards on file.
- Every annual or quarterly renewal that lands inside the closure window.
Involuntary churn is the loss of subscribers to failed payments rather than to a decision to cancel. One failed-payment recovery vendor reports that it typically accounts for 20-40% of total churn in B2C subscription businesses, and its data shows the average brand losing 2 to 4 of every 10 churned subscribers this way. In 2020, a subscription analytics vendor put the average loss at about 9% of monthly recurring revenue. Neither figure involves a processor closure. Both describe a normal month.
The common assumption is that churn means customers choosing to leave. That belief hides most of the damage. The Learner retention text published on CUNY Pressbooks lists a failed payment as its own support trigger, next to product flaws and network failures, and sets a good monthly retention rate at "typically higher than 90%." It also notes that for "the majority of businesses," winning a new customer costs more than keeping an existing one.
Card type matters more than most teams expect. In the recovery vendor's own dataset, 90-day survival was 77.9% for credit cards, 49.5% for debit and 24.9% for prepaid. A second vendor claims that recovering one failed payment extends a subscription by more than 6 additional billing cycles, because the customer who stays keeps paying long after the saved charge.
In practice, start from last quarter's billing records. To size your own share of that loss, the same retention text divides canceled customers by active customers over a set period, then multiplies by 100. The version I trust runs that count twice, on revenue and on customers, and keeps failed payments apart from cancellations, since the text notes churn reads differently depending on which one you track.
I drew on 5 sources for this section, and they point the same way: failed payments are a payments problem before they are a marketing problem. That framing comes naturally at SeamlessChex. Before Seamless Chex, Evan Albert co-founded several other payment startups and spent time in fixed income sales and trading on Wall Street, so the mechanics of how money moves (and stops moving) sit at the center of how we look at retention.
Your baseline also feeds the application for a new credit card merchant account, since processing history is part of what gets reviewed. It helps to know the documents high-risk underwriters actually need before the closure clock gets short. Which leads to the harder question: what happens to those renewals on the day the old account actually closes?
Can you transfer saved cards and active subscriptions to a new payment processor?
Saved card tokens can often move processor to processor, usually for a fee, but subscription records cannot; plans and schedules must be rebuilt, and some customers will still need to act.
Two separate things live inside a recurring-billing account. The card token is the stored credential that lets you charge a customer again. The subscription is the schedule, plan and price attached to that customer. They travel very differently.
A 2025 thread on Reddit's r/stripe forum put the subscription half bluntly. Asked whether recurring subscriptions could move between two Stripe accounts, one commenter answered: "No, it's not possible. You can copy customers, but you need to re-create products, plans, and subscriptions in the new account." Another noted that scripts produce copies, but "no real transfer can be done." The schedule gets rebuilt wherever it lands.
Cards are more portable. The first path is a processor-to-processor token transfer: you ask the outgoing provider to send stored card data to the incoming one, which re-tokenizes it and issues new tokens for your billing engine. Practitioners describing a move from Repay to Viva Wallet said PCI requirements stretch the timeline, though the handoff can happen. In 2023, a developer who said they worked for a competing processor noted that many processors let merchants transfer stored data, "usually for a fee." That same discussion featured a team staying on Authorize.net purely "to avoid re collecting credit cards."
The second path is customer self-migration. You move new sign-ups to the new gateway, keep the old one renewing existing subscriptions, and ask each subscriber to enter a card on the new processor. NovelAI took this route in February 2025 after Paddle stopped supporting AI products. It sent subscribers to an in-app migration link, offered an unspecified "bonus incentive" for switching on their own, and required migration for access to its new NovelAI Diffusion V4 Full model.
| Migration path | Who has to act | What it depends on | Risk inside a 90-day window |
|---|---|---|---|
| Token transfer | The two processors | Outgoing provider's cooperation, a PCI-governed handoff, often a fee | The handoff runs longer than the window allows |
| Customer self-migration | Each subscriber | Old account still renewing, clear outreach, working card acceptance on the new side | Subscribers who never update before shutoff |
Neither path is complete on its own. Tokens move cards, not schedules. Self-migration moves both, but only for the customers who respond. The evidence available does not include a success rate for token transfers or a retention comparison between the two paths, so plan as if each will leave gaps.
My advice is to request the token export in the first days of the window and run the self-serve campaign in parallel, because whatever the old processor releases shortens the list of people you have to chase. A closing processor may also hold funds, and if that happens it helps to know how to unfreeze reserves on a terminated account while the migration runs. Both paths also assume something that has to be arranged before anything moves: an approved credit card merchant account on the receiving end, ready to accept those tokens.
Where do subscribers actually fall out when billing moves to a new processor?
Most subscribers never notice a processor switch until the first charge on the new system. The evidence suggests losses gather at that one charge, and standard churn reports can miss them.
On February 28, 2025, the AI writing and image service NovelAI posted a notice to subscribers. Its previous payment processor no longer supported AI products, so billing was moving to a new one. NovelAI asked people to switch on their own. It offered an unspecified "bonus incentive" and made updated billing a condition for using its newest image model, due out the next day. The same notice admitted that JCB and Discover cards were not yet working on the new processor.
The thread gives no figures on how many subscribers that cost. It does show where the risk sat: at the first charge on the new processor, where some cards could not go through at all.
Card brand was one weak point. How a card is funded may matter even more. Redux, a company that sells failed-payment recovery, analyzed more than $500 million in failed payments across hundreds of subscription accounts. It then broke out how often the first real charge failed for each card type.
Redux's figures come from new subscribers paying their first real charge, mostly after a trial. They show which cards break easily at a first charge. They cannot tell you how many subscribers a migration will lose. Redux itself describes the card a customer signs up with as "one of the strongest early predictors" of involuntary churn. In a migration, every re-entered card, and every stored card charged for the first time on the new processor, faces a first charge of its own.
A failed charge can still be won back, but slowly. Here is how the recovery clock runs in the sources we found:
| After a failed charge | What the evidence says |
|---|---|
| First 10 days | 90% of the transactions that are eventually recovered come back in this window, according to a billing-software roundup that names no original source |
| About 7 to 14 days | One large processor's default retry schedule makes 4 attempts in this span, according to Redux |
| 15 to 30 days | Accounts are typically suspended if a failed renewal gets no response by this point, according to Baremetrics |
| 27 days | Length of Baremetrics' own 7-email recovery sequence |
| 30 days | Card networks allow 15+ retries in this span, according to Redux |
There is a second problem. Some of these losses never show up as losses. In a July 2026 newsletter, Anton Zagrebelny described an audit by Philip Pages, a payment-recovery consultant, of an AI software company with $41 million in annual recurring revenue. The company's dashboard put failed-payment losses at about $480k a month. The audit put them at $2.68 million. About $2.2 million a month of the gap came from trials that failed at the first paid charge. Those customers never reached a paying state, so they were never counted as churn.
"A billing system is a state machine. Revenue leaks through the states your dashboard doesn't render."
Anton Zagrebelny, newsletter writer on billing infrastructure, 2026
One audit cannot show how common that gap is. Migrations raise the same question, though. A subscription rebuilt on a new processor starts over there. Whether a failed first charge shows up as lost revenue depends on how your reports treat a subscription that has not paid yet.
When we line the findings up, the risk of a forced switch sits at one charge per subscriber. That charge comes at the first renewal on the new processor. Weaker cards fail there most often, recovery takes days to weeks, and the loss may not show where you usually look for churn. None of our sources compared a parallel run with a last-minute cutover, and we have no migration figures of our own to add. The timing still points one way. Subscribers moved early have their failed first charges handled while the old account keeps billing everyone else. Move everyone near the end of a 90-day notice and all those first charges, and all their failures, arrive together with little room left.
- Before inviting anyone to switch, run a live charge on the new processor with every card brand your subscribers use.
- If your billing data records whether a card is prepaid, debit or credit, move prepaid and debit subscribers first so their failures get the most time to recover.
- Count back about 30 days from the closure date for the last wave of first charges, and ask the new processor how many retries it runs by default and over how many days.
- Track first charges on the new processor as their own category, listing every migrated subscription with no paid invoice yet. Do not rely on your churn report alone.
How we checked this
We read a subscription company's public migration notice and its comment thread, failed-payment research from two recovery vendors, a billing-software statistics roundup and a newsletter account of a payment audit. None of the figures here are ours. Redux and Baremetrics both sell failed-payment recovery. Redux's card-type data covers new subscribers, not migrations. The 10-day recovery figure has no named original source. The audit is a single company. NovelAI did not publish how many subscribers it kept. We process card payments for subscription businesses and gain when merchants switch processors, so we have a stake in this topic. Still unknown: how retention after a parallel run compares with a late, hard cutover. No source we found measured it.
- NovelAI, payment processor update for subscribers, February 28, 2025.
- Redux, guide to involuntary churn and card types, June 10, 2026.
- Orb, dunning and failed payment recovery statistics, September 22, 2026.
- Baremetrics, article on involuntary churn and dunning, published July 8, 2020, with data through December 2024.
- Anton Zagrebelny, newsletter on billing states and failed trial conversions, July 16, 2026.
How do subscription businesses get approved for a recurring billing merchant account before the deadline?
Apply for a replacement credit card merchant account in the first week, with processing history and subscription terms ready, then add ACH debit as a second recurring rail.
Both migration paths need a destination. A token transfer has nowhere to land until a receiving processor exists, and a self-serve campaign has nothing to send subscribers to until the new checkout is live. That makes the replacement account the first task of the window. Not the last.
If I had only the first week of a 90-day notice, I would spend it on the application. A complete file moves faster than a partial one, so gather these before you apply:
- Recent processing statements from the closing account, plus the closure notice itself.
- Your subscription terms, billing descriptor and cancellation flow as customers actually see them.
- Refund and chargeback history by month.
- Active subscribers by plan and renewal date, so the new processor can size the inbound volume.
When you compare options, the best credit card processor for a subscription business is the one that approves your recurring model as it really runs, accepts an inbound token transfer, and supports a second rail on the same relationship. Price matters too, and it helps to know what a high-risk merchant account should cost before you sign anything. SeamlessChex works with established businesses processing at least $25,000 per month, with same-day onboarding, no contracts, and approvals for subscription and high-risk businesses other processors turn away.
The second rail is ACH. Card processing stays primary, yet a subscriber who pays by bank debit is not stranded when a card processor withdraws. Nacha reports that 17.17 billion consumer bill payments and other debits moved over the ACH Network in 2025, including 11.41 billion internet payments and 4.86 billion prearranged debits. Same Day ACH reached 1.45 billion payments, up 16.7% from 2024, and the network settles four times every banking day, with bills due on a weekend or holiday collected the next banking day.
Two rails change the math of a closure. One withdrawal no longer stops every renewal. Bank debit also suits the customers most likely to struggle in a card migration, the ones whose cards keep getting replaced or declined, because their payment method does not ride on a single card processor's decision.
Set the ACH option up as a choice subscribers can pick during the card update, not as a separate project for month three. The closure notice that started this migration should be the last one with the power to halt every renewal at once.
What will decide how many subscribers survive the next forced processor exit?
Infrastructure decides it: a replacement card account opened early, stored tokens released by the outgoing processor, and subscribers moved in waves while the old account still renews.
I expect the next wave of closure notices to favor businesses that dual-run billing over those that wait for day 89. Failed payments already drain a large share of churn before any switch, so a hard cutover stacks a second failure point on the first.
One gap stays open. This article's evidence holds no retention figures by migration approach and no token-transfer success rate. Those are the numbers worth logging from week one: renewals cleared on the old account, renewals cleared on the new one, and subscribers who never came across.
A 2023 explainer on Berkshire Community College's Nexus blog argued that tracking cancellations, downgrades and canceled payments separates voluntary from involuntary churn, and predicted that "customer retention will rise as a result of reduced churn and its measurement." A migration cohort tests that idea fastest, starting with subscribers whose renewal lands before the new account goes live.
Summarize This Article With AI
Open this article in your preferred AI engine for an instant summary.
Frequently Asked Questions
What else do subscription businesses ask about switching billing during a closure notice?
Most remaining questions come down to speed, card data and communication: how fast a new account opens, what moves with the tokens, and what subscribers must do themselves.
How quickly can SeamlessChex onboard a subscription business facing a closure notice?
SeamlessChex offers same-day onboarding for credit card processing. Approval still runs through underwriting, so have processing statements and plan details ready before you apply. Start through the SeamlessChex contact page at seamlesschex.com/contact.
What has to happen for saved card tokens to move to a new processor?
Token transfer is the processor-to-processor handoff of stored card data. The new processor re-tokenizes what the old one sends, and those new tokens must then be attached to each subscription as its payment method. PCI requirements slow it down. I would file the request the day the notice lands.
Can existing subscribers keep renewing on the old processor during the switch?
Yes, while the old account stays open. Practitioners describe turning off the old gateway for new sign-ups but keeping it active for renewals, so legacy subscriptions keep billing until each customer updates their card. A closure notice puts a hard end date on that overlap.
What should subscribers hear when billing moves?
Three things: what to do, by when, and what happens to the old charge. In one 2025 migration, subscribers who switched got a cancellation email from the old processor, and reassurance came from a fellow user rather than the company. Another user paying through PayPal asked whether they needed to act. The post did not say.
Should a subscription business add ACH bank debit as a backup rail?
Yes, as a second rail behind credit card processing. The ACH Network reaches all U.S. bank and credit union accounts, but it does not settle on weekends or federal holidays. Schedule bank-debit renewals around banking days, especially in the final weeks before the old account closes.
Written by
Jonathan Albert
Co-Founder, SeamlessChex
Jonathan Albert is Co-Founder of SeamlessChex, a credit card processing and fintech payments platform recognized on the Inc. 5000.
Connect on LinkedInSeamlessChex works with established businesses processing a minimum of $25,000 per month.