Maaz Zindani

Loading the index…

↑↓ move↵ openesc close4072 pages

Help for owners

I want to change payment provider without losing my subscribers

Short answer

Saved card details cannot simply be copied by you. The old provider has to export them, and the new one has to import them. For a move to Stripe, Stripe imports the data and returns a mapping file, and subscriptions are migrated separately. Cancel the old subscriptions as the new ones go active, or customers are billed twice.

  • Written for business owners
  • Updated
  • By Maaz Zindani, Senior Software Engineer

Does this sound like your situation?

  • My current provider is too expensive, too limited or has frozen my account, and I want out.
  • I am afraid every subscriber will have to type their card in again.
  • I do not know whether subscriptions, invoices and history move with the cards.
  • My developer says the switch is a weekend job, and I am not sure it is.
  • I am worried customers will be charged twice or not at all during the change.

Why does this happen?

  1. Card details are held by the provider, not by you

    Your site or app usually stores only references to saved cards. The numbers themselves sit with your current provider, so a move needs that provider's cooperation. Stripe's migration guide says the previous processor encrypts the data and uploads it, and that some processors charge a fee or require specific forms, and that producing the export can take anywhere from a few days to several months.

  2. Cards move, but billing history and subscriptions do not come with them

    For an import into Stripe, the guide says subscriptions, invoices and other billing data are not part of the card import, and that subscriptions are migrated with a separate toolkit or the API. Card security codes cannot be imported either.

  3. Running both providers at once can bill people twice

    Stripe says new customers can start on Stripe while existing ones stay with the old processor during the migration, and to cancel the previous subscriptions as soon as the Stripe ones become active or customers are billed twice.

  4. A new account looks new to card issuers

    Stripe notes that the new account has its own merchant identifier, so a temporary rise in declined payments is possible after the switch, and recommends ramping up volume instead of moving everything at once.

What can I do about it today?

  1. Do not cancel the old provider yetKeep that account open and active until the new one is proven. Closing it first can remove your only copy of the card data.
  2. Ask the current provider for a written data exportContact their support, ask what they need from you and how long it takes. The wait is often the longest part.
  3. Count your live subscribers and note their renewal datesA simple list of who renews when, and how. You will need it to check that nobody is missed or billed twice.
  4. Read the current provider's terms about data releaseStripe's guide suggests checking them, because the provider may be obliged to release your data when asked.
  5. Tell your developer to plan a gradual moveAsk for a plan that starts with new customers on the new provider, then moves existing ones in groups, instead of one switch for everyone.
  6. Do not email customers about card changes yetWait until you know whether cards will move. A premature message gets people to cancel or to type details into the wrong place.

When should I bring someone in?

  • You run subscriptions or instalments, where one mistake means charging people twice or not at all.
  • Your current provider has frozen or closed the account and you need your data out.
  • Your app or site was built by someone who is no longer available.

How do I handle it?

  1. Map every place the old provider is usedCheckout, renewals, refunds, webhooks, reports and the customer records that store its IDs. The list shows how big the change is.
  2. Agree the order of the moveNew customers first, existing ones in groups, with a date by which each old subscription is cancelled and the new one is live.
  3. Test with the new provider's test modePayments, failed cards, refunds and renewals are run in a test environment before any real customer is touched.
  4. Compare the money after each groupCharges, refunds and counts are reconciled against the old provider's records, and the old provider stays available as a fallback.
  5. Keep a way backA backup is taken before production changes and the rollback is tested, so one bad group does not become a full outage.

The price depends on what I find, so I quote in writing after a short discovery call. Tell me what is happening and I reply within 24 hours.

What do owners ask about this?

Will my subscribers have to re-enter their cards?

Not necessarily. If the providers support an import, the saved payment methods can be moved. If the old provider cannot or will not export them, customers have to add their card again, and I cannot change that.

How long does a migration take?

It depends mostly on how fast the old provider produces the export. Stripe's guide says that can range from days to months, and that its own standard processing time is 10 business days once it has received valid data.

Can I move to a provider other than Stripe?

Yes, but each provider has its own process and limits. I read that provider's own guide before planning, and I do not assume it works like Stripe's.

Will there be failed payments after the move?

Possibly. Stripe warns of a temporary rise in declines when issuers see a new merchant identifier, which is why a gradual move is safer.

Sources

How was this page made?

I drafted this page with AI assistance from the official documents listed under Sources. Found a mistake? Tell me.

For your developer: the technical fixes

Next step

Want this off your desk?

Send me a few lines on where things stand. I reply within 24 hours.