connection type checkout
Veliro + Checkout.com
Authorize Checkout.com with Veliro tok_* and network cryptograms. Swap processors without rebuilding card-on-file in Checkout’s vault.
Checkout.com combines acquirer relationships with a developer-friendly API; many high-growth merchants standardize on Checkout for international cards. Stored credentials in Checkout’s vault follow the same portability constraints as any PSP: they authorize on Checkout until you re-collect.
Veliro’s connection type checkout accepts your secret key and forwards authorizations with Veliro-managed tokens. Network tokens under your TRID arrive with fresh cryptograms; Checkout processes the payment without owning the long-lived credential.
Merchants evaluating Checkout against Stripe often pilot both as connections against the same tok_* estate, routing a fraction of traffic for approval-rate or FX experiments, then shifting connection_id weights without migration projects.
Checkout-specific features (Fraud Detection, vaulting SKUs) should be evaluated separately from custody. Veliro intentionally does not duplicate PSP fraud SKUs; it ensures the credential layer is neutral so PSP choice stays commercial, not structural.
Setup
Add Checkout connection
POST /v1/connections with type checkout and secret key. Use sandbox keys in test environments; separate connections for production.
Align currency and MCC
Forward payloads include amount and currency; ensure your Checkout merchant account supports the MCC and currencies you route.
Monitor forward errors
Checkout error codes surface through forward responses; correlate with X-Request-Id from Veliro for support tickets spanning both systems.
Forward & portability notes
- Dual-running Checkout and another PSP is a connection_id change at forward time, ideal for gradual migrations.
- Keep Checkout webhooks for payment settlement; use Veliro webhooks for token suspension and card updater events.
- Document which connection is default in your billing worker so failover logic is explicit.