Authorize.net is a gateway — not a processor. When you migrate "from Authorize.net" you're usually migrating from Authorize.net + a legacy acquirer (First Data, TSYS, Harbortouch, EVO, etc). multiflow is gateway + processor + orchestration in one layer, so we replace both. CIM vault ports via PCI-compliant token re-authorization, ARB subscriptions recreate on identical billing days, and the acquirer relationship consolidates to multiflow's direct-to-network rails.
On Authorize.net today
On multiflow after migration
| What you pay for | Authorize.net | multiflow |
|---|---|---|
| Gateway fee | $25/mo + $0.10/txn | $0 — included |
| CIM (vault) fee | $20/mo + $0.10/txn | $0 — included |
| ARB (subscriptions) fee | $10/mo + $0.10/ARB | $0 — included |
| Processing rate | Varies by acquirer (IC+0.8-1.5%) | IC + 0.35-0.55% + 10¢ |
| Chargeback fee | $25-35 (acquirer) | $15 refunded on win |
| Batch closeout fee | $0.05-0.10/batch | $0 |
| PCI compliance fee | $10-25/mo (acquirer) | $0 |
| Monthly minimum | $25-50 acquirer | $0 under $50k vol |
Flat-rate processors optimise for onboarding friction, not P&L. Every line above that reads "flat" on the left and "IC +" or "tiered" on the right is a line where multiflow returns margin that was previously opaque to you.
Two separate relationships to unwind: the Authorize.net gateway (Cybersource-owned) and whatever acquirer lives behind it. We pull both contracts, identify the termination clauses, and time the migration to minimize early-termination fees. A.net data export runs through Merchant Interface → Settings → Download Customer Information.
Unlike other migrations, this one collapses two layers. Our single underwriting substitutes for both the gateway relationship (trivial) and the acquirer relationship (the heavy one). Expect 2 days for acquirer underwriting.
CIM releases stored card fingerprints + last4 + network-level metadata. We re-authorize each token through the acquiring network to verify validity and store under multiflow's vault. On network transaction ID preservation: most CIM tokens are eligible, but any card-on-file older than 36 months may trigger 3DS on first re-charge. Budget for 2-5% of vault customers getting a one-time CSC challenge on their next order.
Authorize.net exports ARB with subscription IDs, amounts, intervals, next-billing dates. We recreate each in multiflow matching every parameter. ARB on A.net cancels at next billing boundary; multiflow picks up that billing cycle. Customer sees no duplicate.
Fraud Detection Suite rules (velocity, CVV, AVS, IP-based) translate into multiflow's fraud engine. One-to-one mapping works for 90% of rules; custom FDS expressions get translated during day 5. Gateway DNS swap: your shopping cart points to multiflow endpoints.
Most A.net users have plugin-based integrations: WooCommerce, Magento, BigCommerce, custom. We ship a plugin swap package that preserves order metadata, refund flow, and receipt formatting. Goes in under 30 minutes for each site.
Apple Pay merchant IDs and domain registrations transfer manually (10 min per domain). Google Pay activates through multiflow admin. 3DS 2.x routing configures per card-BIN rule set.
A.net statement history (24 months) imports into multiflow reporting for trend continuity. Accountant/BI teams get a data dictionary mapping A.net field names to multiflow equivalents.
A.net gateway freezes to new transactions; refunds and disputes process for 45 days. Acquirer relationship terminates per contract terms — we coordinate the closeout letter so the final statement matches multiflow's opening statement with no gap.
Seven days, one operator ceremony per day, zero weekend overtime. Each step is reversible through day 30 — you do not fly one-way until the Authorize.net drain window closes.
Everything below is yours under Authorize.net's ToS. Export now, before underwriting opens — it's faster while you're still a customer in good standing.
Once you submit notice-of-migration, some processors throttle export API limits. You want these files in your S3 bucket before anyone at Authorize.net knows you're leaving.
Gateway + acquirer are separate relationships. When you email "Authorize.net" support, you reach Cybersource (owns A.net). When you call about a reserve or payout delay, you reach your acquirer (First Data, TSYS, Harbortouch, etc). Both must be wound down. Skipping acquirer notification leaves you on an "empty" acquirer contract with monthly minimums continuing to bill.
Early termination fees. Most acquirer contracts have 3-year terms with liquidated damages. If you're mid-contract, calculate the ETF vs multiflow savings — often the savings pay back the ETF in 2-4 months. multiflow will credit up to $5,000 of ETF against your first 6 months of processing fees as a buyout.
CIM fingerprint age. CIM tokens older than 36 months may fail the re-authorization step. These customers get a one-time "update your card" email during day 3.
E-commerce platform plugins. WooCommerce Authorize.net plugins are numerous (official, Skyverge, WooPayments). Each has a different config surface. Plugin swap is straightforward but requires verification that metadata fields preserve.
ACH/eCheck on A.net. If you use A.net's eCheck.Net, migration is trickier — ACH processing has a separate NACHA compliance layer. Talk to us first if ACH is more than 10% of your volume.
Rollback on an A.net migration is 2-3x harder than single-layer migrations because you're unwinding both a gateway swap and an acquirer swap. Within the first 5 days, rollback is feasible: reactivate the A.net gateway (still technically open), restart the acquirer relationship if it hasn't been terminated yet.
After day 10, the acquirer relationship is closed and rollback requires re-underwriting at the acquirer — effectively starting over. We strongly recommend confirming the migration path with a 20-transaction parallel run on day 4 before committing.
Authorize.net has been around since 1996, and integrations exist everywhere — every shopping cart, every custom-built e-commerce stack from 2005-2020 has an A.net code path. The gateway itself is excellent at its job: mature API, reliable uptime, deep fraud features. The migration pain isn't A.net the gateway; it's the acquirer lock-in that A.net implies. Most A.net merchants are on ISO-sourced acquirer deals with 3-year terms and no negotiated rate reviews.
multiflow collapses the layer. Gateway + processor + risk in one rail means one contract, one statement, and one support queue. The operators who benefit most from this migration run more than one brand and have felt the pain of coordinating a fraud rule update or reserve appeal across two different customer service organizations.
The operators who benefit most from this migration run more than one brand and have felt the pain of coordinating a fraud rule update or reserve appeal across two different customer service organizations.
From the Authorize.net migration field notesmultiflow's Hosted Payment Page UX closely mirrors Authorize.net SIM. Direct Post Method users swap one POST URL. Accept.js users swap one script tag + one API key. Custom API consumers get a compatibility shim that accepts A.net-shaped request bodies and returns A.net-shaped responses. The goal is that your shopping cart, custom code, or ERP integration sees near-identical request/response patterns post-migration.
FAQ
Talk to an operator
Human reply within 2 business hours. No chatbot.