Migrate off Adyen
Exit Adyen vault lock-in without a card-on-file rebuild
Adyen-stored tokens and per-entity vaults fragment portability. Veliro tok_* under your TRID let you leave Adyen, or add Stripe alongside, without customer re-enrollment.
Adyen’s unified commerce model attracts global merchants, but credentials stored in Adyen’s vault are still Adyen-scoped. Multi-entity setups make it worse: EU entity tokens do not authorize on your US entity without re-provisioning. Contract renegotiation or adding a US acquirer should not require a quarter of card re-entry campaigns.
Veliro holds network tokens under your TRID above entity boundaries. You register Adyen as one connection (API key + entity ID per route) while tok_* lives in your application. Leaving Adyen means registering a successor connection and changing connection_id; entity splits become routing rules, not credential migrations.
European merchants often discover Adyen lock-in during PSD2-heavy traffic: cryptogram and ECI handling must stay correct through the cutover. Veliro fetches UCAF and scheme-appropriate ECI per charge so the successor PSP receives authentication evidence issuers expect.
Adyen payment webhooks remain valuable for settlement during transition; Veliro webhooks cover token lifecycle. Run both until Adyen forward traffic drains: money events from Adyen, credential events from Veliro.
Migration phases
Map entities to connections
Document each Adyen entity ID, currency, and MCC. Each becomes a Veliro connection with type adyen; labels matter when you replicate routing on a new acquirer.
Stand up neutral custody
Provision new cards via Veliro; for existing Adyen-only tokens, plan a phased re-capture only where legally required; most migrations forward tok_* provisioned from Adyen-era checkout once you re-home capture.
Pilot forward on a slice
Route 1–5% of rebills through POST /v1/forward to the successor connection_id. Compare approval rate and latency against incumbent Adyen forward.
Shift default routing
Update billing workers to prefer the new connection_id by market. tok_* unchanged; entity selection becomes a function on forward, not a vault export.
Retire Adyen as custodian
Disable Adyen connections when no forward traffic remains. Keep Adyen only if commercial terms still win for specific markets you route intentionally.
Common pitfalls
- Treating each Adyen entity as a separate credential namespace in your DB instead of one tok_* with multiple routes.
- Ignoring MIT/recurring indicators on EU traffic during cutover.
- Cutting Adyen webhooks before settlement reconciliation catches up.
- Migrating entities on calendar deadlines instead of by traffic-weighted cohorts.