one API.
every PSP.
full control.

Vermilion sits between your platform and your payment providers. Integrate once, route every payment by your own rules, and survive PSP outages with automatic fallback — without ever being locked in again.

Get sandbox access Read the docs

live connectors: stripe · adyen — next: checkout.com

the integration

a payment in one request

# same call whether it lands on Stripe or Adyen
curl https://api.vermil.dev/v1/payments \
  -H "Authorization: Bearer sk_live_…" \
  -H "Idempotency-Key: order-8412" \
  -d '{
    "amount": 4900,
    "currency": "EUR",
    "payment_method": { "type": "card", … }
  }'

# normalized response — PSP details abstracted
{
  "id": "pay_KATV6iorAs1Zsgy",
  "status": "captured",
  "amount": 4900,
  "currency": "EUR",
  "attempts": [{
    "provider": "adyen",
    "routing": { "strategy": "rule" }
  }]
}

how it works

route → attempt → fallback → notify

01
route
Your rules pick the PSP: by payment method, currency, amount — with health checks removing dead providers automatically.
02
attempt
We call the PSP with your credentials and map its response into one normalized status machine and error taxonomy.
03
fallback
Technical failure? The next PSP in your chain gets the payment. Declines are final — we never retry a refused card.
04
notify
You get one webhook format for every PSP — HMAC-signed, replay-protected, retried, with a delivery log you can re-drive.

why platforms choose vermilion

built for PSP independence

No lock-in

Every connector passes the same conformance suite — adding or dropping a PSP is configuration, not a migration project.

One token, many PSPs

Store a card once, charge it on whichever provider your rules select. Off-session and recurring included.

Audit-grade operations

Append-only audit trail, idempotency on every call, full routing explainability on every attempt. Your ops team sees everything.

Integrate in an afternoon. Stay independent for good.

Get sandbox access