connection type custom

Veliro + Custom acquirer

Forward Veliro tokens to any HTTPS acquirer or processor endpoint. For bank relationships, regional acquirers, or internal payment switches.

Not every merchant fits Stripe, Adyen, or Worldpay. Some operate direct acquirer links, regional processors, or internal payment switches that still speak HTTPS. Veliro’s connection type custom registers your endpoint URL and authentication headers, then POST /v1/forward delivers token, cryptogram, and charge metadata in a documented JSON envelope.

Custom connections are how you keep tok_* portability when your “PSP” is a bank gateway or a home-grown orchestration layer. Veliro remains the credential and scheme layer; your endpoint remains the authorization path you control.

Security expectations are higher: your endpoint must use TLS 1.2+, validate Veliro signatures if configured, and respond within forward timeouts. Mutual TLS between Veliro and your endpoint is available for enterprise deployments; mirror the rigor card networks require on scheme links.

Custom routes are also useful for shadow traffic: forward a sample of charges to a new acquirer endpoint while production connection_id still points at the incumbent; compare approval rates before flipping defaults.

Setup

  1. Expose an HTTPS forward target

    Implement an endpoint that accepts Veliro’s forward JSON schema (documented in Connections API). Return structured approve/decline responses.

  2. Register the connection

    POST /v1/connections with type custom, url, and auth configuration (bearer token, basic auth, or mTLS client cert reference).

  3. Test in sandbox

    Point a sandbox connection at your staging acquirer stub; validate cryptogram and ECI fields your issuer simulator expects.

Forward & portability notes

  • Document timeout and retry behavior. Veliro forward calls are synchronous; slow endpoints block checkout.
  • Version your endpoint contract; Veliro includes API version headers for forward compatibility.
  • Regional acquirers may require local data residency; map connection routing to Veliro merchant regions accordingly.

Route Custom acquirer in sandbox.

Register a connection, provision tok_* via Secure Fields, and forward your first charge, same credential reference when you add a backup acquirer.