Payment credential independence

Own your tokens. Not your processor’s.

Switch PSPs without re-collecting a card. Lift authorization with network tokens. Keep a full audit trail — one integration, every network.

Contact sales →View Docs

Sandbox to first token in under an hour — free, no sales call required.

+4.6%Auth lift · Visa CNP benchmark

0Re-enrollment on PSP switch

100%Audit coverage via webhooks

PCI DSS Level 1SOC 2 Type IIISO 27001PSD2 RTS

Live trace · req_b7Hk9e2Lw

MerchantSecure Fields SDK
POST /v1/tokens
Veliro routingapi.veliro.com
fan-out
MastercardMDES
Visa · routedVTS
American ExpressAETS
tok_3vKw…
Token returnedACTIVE

Scroll horizontally on narrow viewports to read the full trace.

synchronous · one round trip · token returned in‑band

Thesis

The credential layer is the one piece of payments infrastructure you should never rent from a processor. Own the token, own the cryptogram, own the audit trail, and a PSP becomes a routing decision you can change without telling a single customer to re‑add their card.

Read why we’re building a neutral credential layer

The lock-in nobody priced in

Your stored credentials belong to your PSP. Not to your business.

Most merchants don’t actually own their stored credentials. They’re tied to a processor’s token framework. Try to switch PSPs, add a backup, route smarter, or recover from an outage, and you find out who really owns the relationship.

+4.6%Auth lift on eligible Visa CNP trafficScheme benchmark

3 → 1Scheme integrations collapsed to one API

0Cards re-collected when you switch PSP

100%Credential lifecycle auditable via signed webhooks

Three commercial costs of PSP‑tied credentials, the ones that surface the moment you try to switch processor, add a backup, or renegotiate your rate.

PSP lock-in · no portability
Switch processors and you re‑enroll millions of cards. Add a backup acquirer and your credential estate fragments. A credential should travel with you. In most stacks, it can’t.
Authorization ceiling · lost revenue
Network tokens lift CNP approval rates in scheme benchmarks (Visa reports +4.6% on eligible traffic), but only with MDES, VTS, and AETS live and the right cryptogram on every transaction. Most teams ship one network and leave the rest on the table.Scheme benchmark, not a Veliro measurement.
Concentration risk · no resilience
One PSP holding your entire credential estate is one outage, one re‑pricing, or one acquisition away from an emergency migration. The risk never shows on a dashboard, until it does.

Comparison

PSP-tied tokens today vs. merchant-owned credentials.

The same credential estate, reframed as a decision table. Forward this section to finance or procurement — no integration guide required.

PSP independence in depth

Dimension	PSP-tied tokens today	With Veliro
Token ownership	Processor’s TRID — credentials live in PSP vault	Your TRID — merchant-owned credential layer
PSP switch	Re-enroll millions of cards · cardholder friction	Change connection_id on POST /v1/forward
Network coverage	Often one scheme · fragmented cryptogram paths	VTS + MDES + AETS in one synchronous call
Audit trail	Fragmented across PSP logs and portals	Signed lifecycle events · replayable deliveries
Auth optimization	Static PAN or basic PSP token	Per-transaction cryptogram with scheme-correct ECI

How it works

One integration. Every network. No PSP in the path.

Veliro sits between your application and the card networks, never between you and your processor. Card data enters through the Secure Fields SDK, we hold the network relationships directly, and a unified credential comes back in one synchronous call. Your acquirer choice stays yours.

01 · Capture

Secure Fields SDK

Drop hosted fields into checkout. Card data never touches your servers — SAQ-A eligible from day one.

02 · Provision

One POST /v1/tokens

Enroll with the right network in a single synchronous call. Credential binds to your merchant identifier, not your processor’s.

03 · Authorize

Per-transaction cryptogram

Fetch a fresh TAVV, UCAF, or AEVV with the correct ECI before every authorization. Issuers see what they expect.

04 · Route

Any acquirer

Authorize with any PSP you choose. Veliro sits between you and the networks — never between you and your processor.

05 · Lifecycle

Signed webhooks

Events on creation, suspension, network-token activation, and cryptogram invalidation. Failed deliveries retry; any past delivery is replayable.

06 · Audit

Explainable records

Every final state carries a decision trace. Query deliveries, replay events, and stream org audit logs — audit-ready by design.

Solutions

Built for the credential decisions that stall at scale.

We built on network tokenization — the hardest layer in payments. The same primitives run across portability, migration, and agentic commerce.

OutcomePSP independenceOwn the credential layer. A processor becomes a routing decision you can change without customer friction.OutcomeToken portabilityCredentials provisioned to your TRID travel across acquirers. Same tok_* on every route.MigrationPSP migrationSwitch off Stripe, Adyen, Braintree, or Worldpay. Change connection_id — not your credential file.OutcomeAgentic commerceMachine-initiated charges with scoped credentials, cryptogram freshness, and a full audit trail.

View all solutions · Browse by team

Three primitives. One contract surface.

Tokens, cryptograms, and lifecycle are exposed as orthogonal REST resources. Compose them. Don’t subscribe to a flow.

primitive.01Tokens

Credentials provisioned to your merchant identifier on the network, not your gateway’s. Provision, retrieve, suspend, resume, and delete without a processor in the loop. The credential follows you across PSPs.

Visa VTS
Mastercard MDES
Amex AETS · Token Service
Suspend & resume without re‑enrollment

Surface

POST /v1/tokens
GET /v1/merchants/{m_id}/tokens/{id}
POST /v1/tokens/{id}/suspend
POST /v1/tokens/{id}/resume

primitive.02Cryptograms

Per‑transaction TAVV (Visa) and UCAF (Mastercard) cryptograms with the right ECI indicator and unpredictable number. Issuers see the credentials they expect, acquirers see a token they can route, and authorization climbs, with a clean attribution path back to the strategy that earned it.

TAVV · UCAF · AEVV
ECI indicator handled
Single‑use · short TTL
Idempotent by request key

Surface

POST /v1/merchants/{m_id}/tokens/{id}/cryptogram
type PURCHASE · RECURRING · INSTALLMENT
ECI per scheme

primitive.03Lifecycle

Signed events for every credential state change: creation, suspension, network token activation, cryptogram invalidation, deletion. Failed deliveries retry and any past delivery is replayable, so a stalled consumer doesn’t become a lost event.

HMAC‑SHA256 signed payloads
Replayable per delivery
Wildcard or per‑type subscriptions
Rotatable signing secret

Surface

POST /v1/webhooks
GET /v1/webhooks/{id}/deliveries
POST /v1/webhooks/{id}/deliveries/{d}/replay
sig HMAC‑SHA256

VTS

MDES

AETS

Integration

Works where your stack already lives.

Veliro reads from the tools your teams use and posts outcomes to the acquirers finance trusts. One REST contract from sandbox to production — live in weeks, not quarters.

Full integration registry

Direct scheme relationships: Visa VTS · Mastercard MDES · American Express AETS

Trust

Direct network relationships. Audited boundary.

Veliro holds scheme certifications and operates the vault under service-provider PCI scope. Your checkout path stays on SAQ-A; formal attestations and evidence links live in the trust center.

PCI DSS Level 1 SOC 2 Type II ISO 27001 PSD2 RTS

The credential layer is the one piece of payments infrastructure you should never rent from a processor. Own the token, own the cryptogram, own the audit trail.
Why we’re building a neutral credential layer

REST aligned to the network-token lifecycle.

Predictable resources, JSON bodies, structured errors, transparent rate limits, and idempotency keys on every mutation. The same contract from sandbox to production.

REST, synchronous: JSON over HTTPS with Idempotency-Key on every mutating call; retries are safe by construction. No webhook subscription needed for the happy path.
Two auth surfaces, one API: Browser‑safe pk_* publishable keys for Secure Fields, server‑side vk_* merchant keys for tokens, cryptograms, connections, and webhooks.
Signed event stream: Webhooks for token lifecycle, network‑token state changes, and cryptogram invalidation. Payloads carry a Veliro-Signature HMAC and a rotatable secret.
Replay & reconcile: Every delivery is queryable and replayable from /v1/webhooks/{id}/deliveries. Audit logs stream from /v1/organizations/{id}/audit-logs.

Read the full API reference

provision-token.http

POST /v1/tokens HTTP/1.1
Host: api.veliro.com
Authorization: Bearer vk_live_4kGp8x…
Content-Type: application/json
Idempotency-Key: checkout_9f2a1e

{
  "card_data": "eyJhbGciOiJSU0EtT0FFUC0yNTYiLCJlbmMi…", // JWE, public key from JWKS
  "country": "GB",
  "source": "CARD_ON_FILE",
  "external_customer_id": "cus_8fa92b",
  "reference": "checkout_9f2a1e"
}

HTTP/1.1 201 Created
X-Request-Id: a1b2c3d4-e5f6-7890-abcd-ef1234567890

{
  "id": "d4e5f6a7-b8c9-0123-def0-123456789abc",
  "merchant_id": "a1b2c3d4-e5f6-7890-abcd-ef1234567890",
  "scheme": "VISA",
  "token_state": "ACTIVE",
  "network_token_state": "PROVISIONING_PENDING",
  "card_bin": "489537",
  "card_last_digits": "9876",
  "card_expiry_date": "1228", // MMYY
  "source": "CARD_ON_FILE",
  "external_customer_id": "cus_8fa92b",
  "reference": "checkout_9f2a1e",
  "created_at": "2026-05-25T14:32:01.887Z"
}

Audit‑ready by design. Control, not delegated.

Veliro is the audited boundary. Your stack stops touching PANs when checkout runs through Secure Fields, while you keep visibility into credential lifecycle and routing. Formal attestations are in progress; current status and evidence links are in the trust center.

Compliance certifications, scope, status, and evidence
Certification	Scope	Status	Evidence
SOC 2 Type II	Security, availability, confidentiality controls	In progress · observation window underway	SOC 2 status
PCI DSS v4.0 Level 1	Service-provider vault, tokenization, cryptograms	Scope locked · QSA assessment in progress	PCI scope
ISO/IEC 27001:2022	ISMS · key handling, vault tenancy, incident response	ISMS implemented · certification audit underway	Trust center
PSD2 · EU SCA	RTS-aligned issuer step-up and TRA exemption modes	RTS-aligned · self-attested	Security posture

SOC 2 Type II: ScopeSecurity, availability, confidentiality controls; StatusIn progress · observation window underway; EvidenceSOC 2 status
PCI DSS v4.0 Level 1: ScopeService-provider vault, tokenization, cryptograms; StatusScope locked · QSA assessment in progress; EvidencePCI scope
ISO/IEC 27001:2022: ScopeISMS · key handling, vault tenancy, incident response; StatusISMS implemented · certification audit underway; EvidenceTrust center
PSD2 · EU SCA: ScopeRTS-aligned issuer step-up and TRA exemption modes; StatusRTS-aligned · self-attested; EvidenceSecurity posture

Trust center SOC 2 report PCI AoC SLA

Sandbox to first token in under an hour — or we’ll walk you through it live.

Stop renting your credentials.

Request sandbox keys and provision your first credential under your TRID in minutes. Secure Fields keeps checkout on SAQ-A; scheme benchmarks for auth and interchange live in the trust center.

What to expect

We map your current token estate and PSP dependencies
You see a live trace: provision → cryptogram → authorize on your stack
You get a migration or auth-lift estimate based on volume and schemes

Contact sales →View Docs