When to switch from Authorize.Net to Stripe on Adobe Commerce
Ask AI about this article
A B2B client of ours moved their store's card payments from Authorize.Net to Stripe this fall. A few weeks later they were paying a better rate and using features they didn't have before. The person who runs payments on their side told us he'd been having fun in Stripe's dashboard. You don't often hear "fun" and "payment processor" in the same sentence.
The trigger wasn't a feature list. Their Authorize.Net contract was coming up for renewal, and someone on their team asked if they should look at Stripe. Our advice fit in one line: get a real quote, lay it next to what you pay today, and let the numbers decide. The quote won, by enough that the decision made itself.
That's most of the lesson. Stores rarely switch payment gateways because something broke. They switch because somebody finally looked. Below is when it's worth looking, how to compare quotes fairly, and what the switch involves on Adobe Commerce, Magento Open Source and Mage-OS. That includes the parts that get missed: saved cards, refunds on old orders, and the fields your ERP reads.
When is it time to switch payment gateways?
The cheapest moment is the month before your contract renews. Leaving at renewal usually costs nothing extra, and a second quote is useful even if you stay. Check three things in your agreement today: does it renew on its own, how much notice does it need, and does leaving early cost anything?
Beyond the calendar, these are the signs worth acting on:
- Nobody can say what you pay. Add up every fee on your last three months of statements. Divide by the volume you processed. That's your effective rate. If no one has worked it out in a year, start there.
- You pay two companies to take one payment. Authorize.Net's gateway-only plan is $25 a month, plus 10¢ per transaction and a 10¢ daily batch fee (Authorize.Net pricing). The merchant account behind it bills you separately. Stripe has no setup fee and no monthly fee (Stripe pricing).
- Buyers ask for things you can't offer. Apple Pay or Google Pay. ACH bank debit for large invoices. A payment link for an order taken over the phone.
- Decline messages send people to the phone. A buyer sees "transaction declined" and calls your office to find out why. A gateway that shows the real reason (expired card, wrong security code, not enough funds) saves both of you that call.
- Your PCI questionnaire is longer than it needs to be. If card numbers touch your own form or server, your yearly paperwork grows. Hosted card fields keep them off your servers. Our Adobe Commerce payment gateway integration guide explains which questionnaire you're likely on.
- Payouts don't match. If finance spends days working out which orders are inside each deposit, look at the gateway's reports and at what your store sends to the ERP.
And when to wait? If your effective rate is fair and nothing is missing, switching is work with no payoff. Don't do it in your busiest weeks. And don't do it in the middle of an upgrade or a replatform. One change to checkout at a time.
How do you compare payment processor quotes fairly?
First, know the two pricing models you'll be quoted.
- Flat rate. One percentage plus a fixed fee per charge, whatever card the buyer uses. Stripe's published US rate for domestic cards online is 2.9% + 30¢. Authorize.Net's all-in-one plan lists the same 2.9% + 30¢, plus its $25 monthly fee.
- Interchange-plus (IC+). You pay what the card networks charge for that exact card, called interchange, plus a fixed markup from the processor. Debit cards cost less to accept. Corporate and rewards cards cost more. Stripe offers IC+ and volume discounts to businesses with large volumes.
Neither one is always cheaper. It depends on your card mix. That's why you compare on your own numbers, not on the headline rate. Here's the method we gave our client:
- Work out your effective rate today, from real statements.
- Give every provider the same facts: monthly volume, average order, how many payments are corporate or purchasing cards, how many are international, and how many refunds and disputes you get a month.
- Ask for an all-in figure on your mix, not a rate card.
- Compare every line, not just the percentage: monthly and batch fees, PCI program fees, the dispute fee (Stripe lists $15 per dispute), payout timing, contract length and exit terms.
- Price bank debit on its own line. For a B2B store, this can matter more than the card rate. At Stripe's published US prices, a $5,000 invoice paid by card costs $145.30 in fees. Paid by ACH Direct Debit, at 0.8% capped at $5, it costs $5.
That last one is worth a pause if your buyers place big repeat orders. Moving a few regular accounts onto bank debit can save more than shaving a tenth of a percent off cards.
What does switching from Authorize.Net to Stripe involve on Adobe Commerce?
Less than people fear, and more than one toggle. Here are the pieces, in the order we'd take them. The store in this story runs Magento Open Source. All of it applies the same way on Adobe Commerce and on a Mage-OS build.
Install Stripe's module, switched off
Stripe maintains its own module for Adobe Commerce and Magento Open Source (Stripe docs). It installs with Composer. On our client's store we pinned the exact version, so a routine update can't change checkout unless someone decides it should. Deploy it switched off. The old gateway keeps taking payments until you're ready.
Decide what happens to saved cards
Cards that buyers saved with Authorize.Net don't move on their own. You have two options.
- Import them. Stripe's data migrations team can import saved cards from your old processor, once that processor sends an export (Stripe: import payment data). Stripe warns that processors handle this differently. Some charge a fee, some need forms, and the final export can take anywhere from a few days to several months. Once Stripe has valid data, imports usually finish within 10 business days. Security codes never move, because PCI rules don't allow storing them. Afterwards your store needs Stripe's mapping file loaded, so each customer points at their new Stripe record.
- Let buyers enter them again. If most of your buyers type in a card with each order anyway, this is simpler. The card gets saved again at their next checkout.
Subscriptions are a separate job. Stripe's card import doesn't move them. Stripe's docs also warn you to cancel the old ones as soon as the new ones are active, or customers get billed twice.
Keep the old gateway installed until its refunds are done
Turning the old method off at checkout isn't the same as removing it. An order paid through Authorize.Net still refunds through Authorize.Net. An online credit memo in the admin needs the old module and its credentials to do that. And Authorize.Net only refunds transactions settled within the past 180 days (Authorize.Net support). Disputes on old charges can turn up later too, and they come to the old account.
So keep the old module installed and switched off, keep the account reachable, and put a date on the calendar to remove it. Our client did just that. Authorize.Net is still in their store, switched off, as a backup. What we did remove was a payment extension that came bundled with Magento. The store had never used it, and it still loaded its script on every page. The integration guide has the longer version of that story.
Check capture timing if you charge when you ship
Many B2B stores authorize the card when the order is placed and capture the money when it ships. The two gateways don't give you the same window. Authorize.Net holds an authorize-only transaction for up to 30 days before it expires (Authorize.Net support). Stripe's module docs say a card authorization holds for up to 7 days (Stripe docs). If your backorders ship weeks later, settle the plan before the switch. Capture at order, authorize again before shipping, or charge a saved card when it ships.
Tell the ERP before the first Stripe order lands
This is the seam that gets missed. Three things change on every order:
- The payment method code. Stripe's module records the payment method as
stripe_payments. If your ERP (Epicor Prophet 21, NetSuite, Business Central, whichever you run) or your accounting import maps payment methods to terms or GL accounts, add the new code before the switch. Otherwise the first Stripe orders arrive unmapped. - The transaction ID. Authorize.Net's transaction IDs are numbers. Stripe's start with
pi_. Any import field, report or matching rule that expects a number needs a look. - The payout report. Finance will reconcile from a new report in a new format. Walk them through it before the first month end, not after.
Our ERP integration readiness checklist covers which fields the store and the ERP need to agree on. The integration guide covers matching payouts to orders.
Make sure the webhooks reach the store
Stripe tells your store about things that happen after checkout, like refunds, disputes and delayed payments, through webhooks. Each environment needs its own endpoint and signing secret, and Stripe has to be able to reach it. A staging site behind a login wall won't hear from Stripe unless you let Stripe through. When webhooks go missing, orders can sit in limbo. That's the problem behind Magento 2 orders stuck in pending payment.
Should you run both gateways side by side, or switch all at once?
Our client's first idea was careful. Send a few products through Stripe, keep Authorize.Net on the rest, and switch fully once some orders had gone through cleanly. It's a sensible instinct. We recommended against it, and they agreed.
Magento decides which payment methods to show from its configuration, by website and store, not by product. (Here's how that decision works.) Splitting one catalog between two gateways means building routing logic, testing it, and tearing it out a few weeks later. That's real work on the most sensitive page of the store, for something temporary.
Here's what we suggested instead:
- Deploy the module switched off.
- Test in Stripe's sandbox the way your buyers really buy. For this client that meant a very large order, because their corporate-card buyers often run into their own card limits on big purchases. It also meant every kind of decline. In the sandbox, the shopper saw the real reason: expired card, wrong security code, not enough funds.
- Automate the basics. We added two checkout tests, one for a guest and one for a registered customer. Each pays in Stripe's sandbox, then checks the database to confirm the order was invoiced with a Stripe transaction. They refuse to run unless the checkout is on a test key.
- Pick the hour. Give the team a heads-up. Switch Authorize.Net off and Stripe on in the admin. Then buy your cheapest product with a real card, and refund it.
One honest caveat. Stripe's own migration guide suggests ramping volume up rather than moving everything at once. Your new Stripe account comes with a new merchant ID that banks haven't seen yet, and that can cause a short-lived rise in declines. It matters most when you're charging imported saved cards or subscriptions. For a store where buyers type in a card at checkout, a planned switch is simpler. If you're moving a big file of saved cards, ramp those up gradually.
Our full go-live test list is in the integration guide.
Why is Stripe often the simple choice?
When clients ask what to move to, we usually point mid-market stores to Stripe, because it's simple to run. Here's why:
- One account. The gateway and the merchant account come together, with no setup fee or monthly fee.
- The module is Stripe's own. It covers both Adobe Commerce and Magento Open Source, and Stripe maintains it.
- New payment methods without new code. Apple Pay, Google Pay, ACH Direct Debit and others are turned on from Stripe's dashboard. Stripe's docs say you don't need to upgrade the integration to add one.
- Smaller PCI scope. Stripe says both of the module's checkout options, the embedded Payment Element and a redirect to Stripe Checkout, are SAQ A eligible. You still own the other scripts on your payment page. While we were in there for the switch, we took the scripts that had nothing to do with paying off our client's checkout page: a product zoom viewer, a contact popup, marketing tags.
- B2B tools in the admin. Staff can create an order for a phone customer, email the buyer an invoice link to pay, or request a bank transfer (Stripe docs).
- Tools people like using. Our client's payments lead brought up the developer tools on his own, a few weeks in.
When is Stripe not the right choice?
Being fair about it:
- You have the volume to negotiate. A merchant acquirer on IC+ pricing may beat a flat rate. Ask Stripe for IC+ too, since it offers custom pricing at large volumes. Then compare like with like.
- A lot of your revenue is on corporate or purchasing cards. These cards can qualify for lower interchange when the payment carries extra order data, the old Level 2 and Level 3 data. In October 2025, Visa replaced that program with its Commercial Enhanced Data Program. Stripe's guidance on it is written for IC+ pricing (Stripe support). On a flat rate, don't expect to see that saving directly. Ask every provider how they handle it.
- You need more than one processor. Failover, or routing by region or by cost, is payment orchestration. Our payment orchestration guide covers it.
- Your ERP takes payments too. Maybe phone orders or invoices get paid inside the ERP, through its own processor. Adding a second processor for the web store then means two sets of reports and two places to refund. One processor for both can be worth more than a slightly lower rate on one.
And if you're on the other side of all this, a payment provider that wants its own module in Adobe Commerce stores, that's a different job. Here's how we build payment gateway modules.
Frequently asked
Can I move saved cards from Authorize.Net to Stripe? Yes, if Authorize.Net sends an export to Stripe's data migrations team. Ask early, because the old processor's export is usually the slow part. Security codes don't transfer, and subscriptions move separately.
Can I still refund Authorize.Net orders after switching to Stripe? Yes, as long as the old module stays installed with its credentials, and the payment settled within Authorize.Net's 180-day refund window. Past that window, you'll need another way to pay the buyer back.
How long does it take to switch from Authorize.Net to Stripe? On the store in this story, the module went in at the end of one month. It took its first live payment about two weeks later, once the client was ready to flip it on. Importing saved cards adds the old processor's export time on top.
Does Stripe's module work on Adobe Commerce, Magento Open Source and Mage-OS? Stripe supports Adobe Commerce and Magento Open Source. Mage-OS shares the same payment framework, so the same module generally applies. Check the module's supported versions against your build, and test it.
Do I need to cancel Authorize.Net right away? No. Keep it switched off until refunds and disputes on its orders are done and the contract ends. Our client let their contract run out and left the module installed, switched off, in case they ever need it.
When does your payment contract renew?
If you don't know offhand, it's worth finding out this week. If the date is a few months away, you're in the window where a second quote costs nothing and there's still time to act on it. Our client's switch started with one question from someone on their own team.
If you'd like a hand with the switch itself, that's part of our payment gateway work. Honestly, it's one of the more satisfying jobs we do: the store gets cheaper to run, and the buyers at checkout never notice a thing.