connection type adyen
Veliro + Adyen
Route Veliro credentials to Adyen with entity-scoped connections. Keep tok_* when you add Stripe for US failover or renegotiate Adyen pricing.
Adyen’s unified commerce stack is attractive for global merchants, but Adyen-stored tokens are still Adyen-scoped. Multi-entity setups (separate merchant accounts per region) compound the problem: each entity’s token vault fragments your card-on-file estate.
Veliro sits above entity boundaries for credential custody. You register connections with type adyen, supplying API key and entity ID per route. Authorizations forward with tok_* plus scheme cryptograms; Adyen sees network-token authentication data without you provisioning cards separately into each Adyen entity vault.
European merchants often pair Adyen routing with PSD2-aware cryptogram and ECI handling from Veliro rather than re-implementing scheme field maps per market. When you add a US Stripe connection for redundancy, the same tok_* forwards to either connection_id, no customer re-entry.
Adyen’s webhooks for payment outcomes remain on the Adyen side; Veliro webhooks cover credential lifecycle (expiry, suspension, network token updates). Keep both pipelines: money events from the PSP, credential events from Veliro.
Setup
Register entity-scoped connections
POST /v1/connections with type adyen, API key, and entityId for each legal entity or market you route through. Label connections clearly in your ops dashboard.
Map forward to the right entity
Choose connection_id per charge based on currency, shopper country, or merchant of record, your tok_* does not change when the entity route does.
Validate cryptograms for EU traffic
Fetch per-transaction cryptograms with correct ECI before forward; EU issuers are sensitive to authentication evidence on tokenized MIT traffic.
Forward & portability notes
- Rotate Adyen API keys on the connection object without touching stored tok_* references.
- Use separate sandbox connections with Adyen test keys; forward idempotency keys prevent duplicate captures on retries.
- Connections API documents required fields for adyen type including live vs test environment selection.