Migrate off Checkout.com
Switch off Checkout.com while keeping every stored card
Checkout.com vault tokens do not travel when you change processors. Veliro tok_* and network cryptograms let you leave Checkout, or dual-run acquirers, without customer re-entry.
Checkout.com wins many international-growth RFPs with competitive FX and local acquiring. Cards stored in Checkout’s vault, however, authorize only on Checkout until you export and re-tokenize elsewhere, a project measured in engineering quarters and churn spikes.
Veliro provisions credentials under your TRID before they ever rest in a PSP vault. Checkout registers as connection type checkout with your secret key; forward sends tok_* plus cryptograms. When you move to Stripe or Adyen for a market experiment, the same reference forwards, no “update your payment method” campaign.
High-growth teams often dual-run Checkout and another PSP for approval-rate tests. Veliro makes that an A/B on connection_id weights rather than duplicate card files. Roll back by routing forward traffic, not by restoring backups of PAN spreadsheets.
Checkout Fraud Detection and local payment methods remain on the authorization you forward. Veliro addresses custody and scheme connectivity; commercial PSP features stay on the PSP you route through.
Migration phases
Quantify Checkout-bound volume
Identify active card-on-file and subscription volume settling through Checkout credentials. Prioritize cohorts with upcoming contract renewal or rate renegotiation leverage.
Capture new cards on tok_*
Move checkout to Secure Fields + POST /v1/tokens. Stop writing new Checkout vault references into your customer model.
Configure successor connection
Register Stripe, Adyen, or Worldpay via POST /v1/connections. Validate sandbox forward with network-token and PAN-fallback cards.
Weighted cutover
Shift connection_id per cohort or percentage rollout. Monitor approval rates; Checkout-specific decline codes should disappear from forward responses as traffic moves.
Close Checkout custody
Revoke Checkout API keys on connections when forward volume hits zero. Retain Checkout only where it remains the chosen rail for specific markets.
Common pitfalls
- Confusing Checkout’s idempotency keys with Veliro’s; use Idempotency-Key on both token and forward mutations.
- Migrating during a FX promo window without baseline approval metrics.
- Leaving legacy Checkout webhooks pointed at handlers that expect Checkout-specific payment IDs instead of your tok_*.