What changes and what does not
Your providers and your merchants stay. Provider accounts move into Tranzify terminals and routing into the flow builder; merchants on the hosted checkout change a link, API merchants integrate the Tranzify API in the sandbox and go live one by one. The contracts, the settlement and the licence do not move at all: they were never the platform’s.
The migration, step by step
- A network under your domain, providers in terminals, routing rules rebuilt and reviewed together.
- Sandbox: each merchant runs its own test suite against Tranzify.
- Production keys: the merchant goes live; the back office shows every payment with its trace.
- The next merchant. Both platforms run side by side until the last one has moved.
What moves, and how
| Item | How it moves | Who does it |
|---|---|---|
| Providers and terminals | Accounts, currencies, limits and fees entered in the terminals; sandbox payments through each | The client’s operations team with Tranzify |
| Routing rules | Rebuilt in the flow builder from the old rules, reviewed, activated as a version | Operations with Tranzify |
| Fees and reserves | Rules per merchant, as in the old ledger; the first settlement is the test | Finance |
| Checkout merchants | A new link; the old link keeps working until the merchant switches | The merchant |
| API merchants | The flow mapped in the sandbox, tests, production keys | The merchant’s developer |
| Webhooks | Tested in the sandbox before the switch | The merchant’s developer |
| Stored cards | Re-tokenised on the first successful payment where the acquirer allows | The vault |
| Payment history | Imported for reports and the merchants’ cabinets | Tranzify from the client’s export |
| Users and roles | Created in the back office; the audit log on from day one | The client’s administrator |
What you leave behind
Nothing you need: payment history is imported for reports; stored cards are re-tokenised on the first successful payment where the acquirer allows; webhooks are tested before the switch. What you do leave behind is the integration backlog, the adapters that break when a provider changes its API, and the reports finance reconciles by hand.
The parallel run
The old platform keeps processing the merchants that have not moved; Tranzify serves the ones that have; the client’s operations team watches both from the first day, with the Tranzify back office showing every migrated payment and its trace. A merchant whose tests fail stays on the old platform until they pass; a merchant whose approval rate drops after the switch is looked at the same day, with the routing trace in front of the team. The old platform is switched off when the last merchant has moved and the last settlement from it is closed.
What you gain
Your own cloud account as an option, five-year journals with a trace per payment, isolated white-label networks, payouts and finance in the same platform, the catalogue of providers that a new market needs, and a pricing model chosen for your volume. The checklist we go through with every client is in the blog post on migrating a PSP.