Switching Payment Processor for Online Pharmacies Without Losing Cards
How an online pharmacy moves saved cards and refills to a new processor: network registration first, what transfers, the steps, after a closure.
Article summary
TL;DR
Saved cards can move: the old processor sends an encrypted export to a new processor that is PCI DSS Level 1 certified. Refill subscriptions don't move, so you rebuild them. For an online pharmacy, the new acquirer must first register you with Mastercard, and with Visa unless you hold a recognized accreditation, before processing your payments.
- Mastercard requires the acquirer to register a non-face-to-face pharmacy (MCC 5122, 5912) before acquiring its transactions (edition of August 4, 2026).
- Stripe sends card data only to "another PCI DSS Level 1-compliant payment processor".
- Stripe's export includes card details, emails and attached metadata, but not subscriptions, payment history or Link cards.
- "Each PSP issues its own token format": cards are re-tokenized on import.
- Cardholders can generally dispute for up to 120 days at Stripe: keep the old account open that long.
On this page
This guide is part of our hub on online pharmacy payment processing. The general guide, for any business: switching payment processor without losing customers. For brands rather than pharmacies, Tagada Rx bundles storefront, doctors, pharmacy and payments, open by application.
Line up the new acquirer first
Your cards are useless on a processor that can't yet accept your payments. For a pharmacy, acceptance depends on card network registration done by the acquirer.
| Network | What the new acquirer must do |
|---|---|
| Mastercard | Register the pharmacy before acquiring; verify it complies with applicable laws, then re-verify at least every 12 months (§9.4.3)2Mastercard Security Rules and Procedures, Merchant Edition, August 4, 2026, sections 9.2.1 and 9.4.3 |
| Mastercard | Penalty for acquiring without registration: up to $10,000, then monthly assessments (§9.2.1)2Mastercard Security Rules and Procedures, Merchant Edition, August 4, 2026, sections 9.2.1 and 9.4.3 |
| Visa | Be approved for high-integrity risk acquiring and register the merchant, unless the pharmacy is accredited by NABP or another body Visa recognizes (§1.9.5.1)3Visa Core Rules and Visa Product and Service Rules, edition of October 24, 2026, section 1.9.5.1 |
$10,000
Mastercard penalty, at most, for acquiring a pharmacy without registration
12 months
Maximum gap between Mastercard legality checks
120 days
Typical Stripe payout pause after a risk action
Mastercard's proof of legality "may include, but is not limited to, a written opinion from independent, reputable, and qualified legal counsel or accreditation by a recognized third party"2Mastercard Security Rules and Procedures, Merchant Edition, August 4, 2026, sections 9.2.1 and 9.4.3. Have your state pharmacy licenses and your LegitScript or NABP accreditation ready on day one. The list: online pharmacy merchant account compliance.
Tagada follows Visa and Mastercard rules and the laws that apply to payments.
What moves and what doesn't
| Data | Moves? | How |
|---|---|---|
| Card numbers and expiry dates | Yes | Encrypted export to a PCI DSS Level 1 processor1Stripe Docs, Request a payment data export, read November 2, 2026 |
| Patient emails and metadata | YesFrom Stripe | In the same export1Stripe Docs, Request a payment data export, read November 2, 2026 |
| Processor tokens | No | Re-created by the new processor4Gr4vy, How to migrate stored card data between payment providers, December 3, 2025 |
| Cards saved with Link | No | Excluded by Stripe1Stripe Docs, Request a payment data export, read November 2, 2026 |
| Subscriptions and refill schedules | No | Rebuild from your records1Stripe Docs, Request a payment data export, read November 2, 2026 |
| Payment history | No | Pull from the Dashboard or API1Stripe Docs, Request a payment data export, read November 2, 2026 |
Watch out
The export carries "any attached metadata"1Stripe Docs, Request a payment data export, read November 2, 2026. If clinical details ever ended up in payment metadata, they travel with the file. Audit metadata before you request the export, and keep prescription data in the pharmacy system, not in payment objects.
Fig. 1Old processor to new: what crosses over
Moves in the encrypted export
- Card numbers and expiry dates
- Patient emails and metadata, from Stripe
Stays behind
- Processor tokens, re-created by the new processor
- Cards saved with Link
- Subscriptions and refill schedules
- Payment history
Register with the new acquirer first. Then the cards can travel.
The migration, step by step
- Get approved by the new processor, including card network registration2Mastercard Security Rules and Procedures, Merchant Edition, August 4, 2026, sections 9.2.1 and 9.4.33Visa Core Rules and Visa Product and Service Rules, edition of October 24, 2026, section 1.9.5.1.
- Request the export from the old processor, naming the new one; Stripe asks for its attestation of compliance and PGP key1Stripe Docs, Request a payment data export, read November 2, 2026.
- Export your refill schedules yourself: patient, plan, price, next ship date, status.
- Match each refill to an active prescription in the pharmacy system; don't rebuild refills that have no prescription behind them.
- Rebuild subscriptions on the new system with the same dates and prices.
- Test real charges, a void and a refund before renewals run.
- Run both processors for one full billing cycle, as one migration guide recommends7Shuttle Global, How to switch payment providers without losing customers, March 21, 2026 (vendor guide).
- Keep the old account open for refunds and disputes on past charges6Stripe Docs, How disputes work, read October 14, 2026.
In this order: approval first, renewals only after a tested import.
Watch out
A new name on the statement creates "I don't recognize this" disputes. Keep your pharmacy or brand name in the descriptor, and tell patients before the next charge if it changes.
If you're switching after a closure
| When | Action |
|---|---|
| Day 0 | Read the notice; request the card export at once1Stripe Docs, Request a payment data export, read November 2, 2026 |
| Days 0 to 2 | Export refill schedules and history; apply to a new processor with your licenses and accreditation |
| Until approval | Pause refills you can't charge yet; tell affected patients |
| Before renewals | Import, rebuild, test, then restart refills |
| Ongoing | Answer disputes on the old account while funds are held; Stripe typically pauses payouts for 120 days after a risk action5Stripe, Unacceptable Risk Policy, last updated July 29, 2026 |
Fig. 2Switching after a closure, stage by stage
- Day 0Read the notice; request the card export
- Days 0 to 2Export refill schedules; apply with licenses and accreditation
- Until approvalPause refills you can't charge; tell patients
- Before renewalsImport, rebuild, test, then restart refills
- OngoingAnswer disputes on the old account while funds are held
Ask for the card export on day 0.
After a Stripe closure: why Stripe closed your online pharmacy account.
Avoid the next forced switch
Fig. 3Five habits that make the next switch easy
Know where cards live
And how they would move, before you need it.
Check platform lock-in
Some pharmacy platforms impose their processor; Pharmacy Times suggests asking whether you can choose your own merchant account and what migration limits apply8Pharmacy Times, Payment processing and compliance in telehealth: what 2026 will demand, January 30, 2026.
Keep your own records
Of refills, consent and prices.
Keep disputes low
So a closure doesn't happen: chargebacks for online pharmacies.
Plan a backup processor
Behind the same checkout: payment routing for online pharmacies.
How Tagada helps
Data you can export, processors you can change
Tagada Rx is a telehealth stack with storefront, doctors, pharmacy and payments, built to avoid lock-in on data9Tagada Rx, tagada.io/rx, read November 2, 2026:
- "Your data is yours to export"9Tagada Rx, tagada.io/rx, read November 2, 2026.
- Two ways to get paid: TagadaPay managed, where you hold no processor credentials, or bring your own processor, where "you keep the acquiring relationship, the settlement and the risk"10Tagada Docs, Payment processors, read November 2, 2026.
- Card data vaulted once: "Transactions flow to the best processor automatically"11Tagada Docs, Multi-processor routing, read November 2, 2026.
- Subscriptions with retries, pause and resume, cancellation and processor changes.
Tagada Rx is open by application to a selected group of brands. Details: Tagada Rx.

Frequently asked questions
Can an online pharmacy move saved cards to a new processor?
Do refill subscriptions transfer when I change processor?
Why does a pharmacy need registration before switching?
Will patients have to re-enter their card?
How long should I keep the old processor account?
Sources
Checked November 3, 2026- Stripe Docs, Request a payment data export, read November 2, 2026
- Mastercard Security Rules and Procedures, Merchant Edition, August 4, 2026, sections 9.2.1 and 9.4.3
- Visa Core Rules and Visa Product and Service Rules, edition of October 24, 2026, section 1.9.5.1
- Gr4vy, How to migrate stored card data between payment providers, December 3, 2025
- Stripe, Unacceptable Risk Policy, last updated July 29, 2026
- Stripe Docs, How disputes work, read October 14, 2026
- Shuttle Global, How to switch payment providers without losing customers, March 21, 2026 (vendor guide)
- Pharmacy Times, Payment processing and compliance in telehealth: what 2026 will demand, January 30, 2026
- Tagada Rx, tagada.io/rx, read November 2, 2026
- Tagada Docs, Payment processors, read November 2, 2026
- Tagada Docs, Multi-processor routing, read November 2, 2026
Tagada Rx
Switch processor without losing a refill
Tagada Rx runs the stack behind your brand. Open by selection: every application is reviewed, and we reply to each one.
- 01Tell us about your brand
- 02We review every application
- 03Go live under your brand after review
