Migrating away from Vortex
How to leave, what moves with you, and what has a tail.
Migrating away from Vortex
An exit guide, written by us, on purpose. A payments provider you cannot leave is a provider you should not join — this page exists so the cost of leaving is known before you integrate, not discovered after.
What moves with you
| Data | How it leaves |
|---|---|
| Customers | Listable and exportable via the API you already use |
| Catalog (products, prices) | Fully readable via API |
| Invoices and their lifecycle state | Readable via API, including payment lifecycle and receipts |
| Subscription state | Readable via API |
| Settlement and payout history | Readable via API — gross, fees, refunds, adjustments, net, per settlement |
| Webhook event history | Listable and re-derivable from your own handler’s records |
Your identifiers were yours all along: customer upsert is keyed on your
external ids, and merchants carry your externalMerchantRef, so re-pointing a
new provider at your own records does not require an id-mapping archaeology
project.
What has a tail
- Stored card credentials. Card data lives in PCI-scoped vaults, never on your servers or ours in raw form. Moving stored credentials to a new provider is a standard vault-to-vault transfer performed at the processing level — request it, and we coordinate it. It takes coordination time; plan for it in your cutover schedule.
- Chargebacks and refunds. Card networks allow disputes months after a charge. Final settlement of your last processing period follows the dispute window and any reserve terms in your agreement — the same reason every provider, including the one you are moving to, holds a tail.
- In-flight settlements. Money already accruing settles and pays out on its normal schedule.
The order that works
- Point new charge volume at the new provider.
- Keep the Vortex webhook handler alive until in-flight invoices and subscriptions finish their cycles.
- Export historical records via API at your leisure — read access does not expire the day you stop charging.
- Request the stored-credential transfer early; it is the long pole.
If something on this page turns out to be harder in practice than we made it sound, that is a bug in the product or in this page — tell us and we fix whichever one it is.