Migration
Switch to Superior — without changing a line of code.
Two paths to migrate, both designed to keep your customers and your code untouched: bring your saved-card tokens with you, or just point your existing Stripe, Square, or Authorize.Net traffic at our API and we translate the calls.
Two paths
Pick the migration that fits your stack.
Most merchants use both. Token import preserves your saved-card customers; API translation lets your code keep running unchanged.
Bring your tokens with you.
When you request a token export from your current processor, we ingest it into our PCI Level 1 vault. Your saved-card customers never re-enter a card — same card-on-file, same recurring schedule, no re-authorization required.
- Card and ACH tokens both supported
- Original metadata preserved (last4, expiry, customer ID)
- Recurring schedules transfer with the tokens
- Account-updater enrollment from day one
Point and process.
Already integrated with Stripe, Square, Authorize.Net, or Braintree? Change the API endpoint to ours. We translate the request shape, dispatch through our gateway, and translate the response back. Your code doesn't know the difference.
- Wire-compatible request and response shapes
- Same idempotency-key semantics
- Webhook event shapes preserved on your old format
- Switch to native Superior API on your timeline
API compatibility
Drop-in replacements for the gateways you already know.
Each translation layer is built and maintained by our integration engineers — not auto-generated. We test against the upstream API on every release.
Stripe
Payments / PaymentIntents API
Charges, PaymentIntents, Customers, PaymentMethods, Refunds, and webhook event shapes — all wire-compatible.
Square
Payments API
CreatePayment, RefundPayment, customer card-on-file, and idempotency-key semantics preserved.
Authorize.Net
AIM + CIM
Authorize/capture, recurring billing, and Customer Information Manager profiles — translated request and response.
Braintree
Transactions API
Transactions, Customers, PaymentMethods, and disbursement webhooks — native compatibility.
On a different gateway? Tell us which one — most translation layers spin up in days.
Token import
Four steps from export to live traffic.
The token migration itself is mostly waiting on your current processor. The technical work on our side is hours, not days.
- 1
Request your export
PCI rules require your current processor to provide a token export on request. We'll give you the exact phrasing to use and coordinate the secure handoff.
- 2
Vault-to-vault transfer
Your tokens move directly between PCI Level 1 vaults — encrypted at rest and in transit. Raw card data never leaves the controlled environment.
- 3
Mapping & validation
Each imported token is mapped to a Superior token with original metadata preserved (last4, brand, expiry, customer ID). We test-auth a sample to verify the import.
- 4
Switch traffic
Cut over your live traffic on a date you choose. Your saved-card customers keep paying with the same card-on-file — no re-prompt, no re-auth, no churn risk.
Typical timeline
Live on Superior in two weeks.
Most migrations complete in 10–14 days. High-complexity stacks may take longer — we'll tell you up front, not halfway through.
Day 0
Sign and request export
Underwriting kicks off in parallel with the export request to your current processor.
Days 5–10
Vault-to-vault transfer
Encrypted token transfer completes. Recurring schedules and customer profiles import alongside the cards.
Days 10–13
Sandbox validation
Run a sample of real authorizations through Superior in test mode. Webhook signatures, response shapes, and edge cases are verified end-to-end.
Day 14
Live cutover
Flip the API endpoint. Traffic moves to Superior. All tokens active. Existing client code unchanged.
What about…
The questions every CFO asks.
Migrations sound risky. Here's why this one isn't.
Reissued cards keep working
Imported tokens enroll in Visa Account Updater and Mastercard ABU on day one — so cards reissued after the migration are kept current automatically.
Active subscriptions don't blink
Recurring schedules transfer with the tokens. Your subscribers see no interruption, no re-prompt, no failed renewal.
Webhooks stay compatible
If you're on a translated API, your webhook listener keeps receiving events in your old processor's shape. Switch to Superior's native webhook format on your timeline.
Your PCI scope doesn't grow
Imports are handled inside our PCI Level 1 vault. You don't see raw PAN, you don't store one, and your assessment scope doesn't change.
Schedule a migration assessment.
Tell us where you process today and we'll walk you through exactly what your switch looks like — token transfer, API compatibility, and your live-on-Superior date.