Skip to content
Concept demo

A fictional brand, designed and built by Get Ranked On Top. Not a real company.

00Payments infrastructure · Dublin · Since 2016

142msMedian authorisation, worldwide.

Velorum authorises, routes, screens and settles card, account-to-account and wallet payments in 46 currencies across 182 countries. One integration, one contract, one ledger.

Card-not-present authorisation rate, trailing 12 months
91.4%
API availability, trailing 12 months
99.995%
Currencies settled same day (T+0)
31
Transactions processed in 2025
4.1 bn

1,900 businesses in 182 countries process on Velorum.

  • QUAYLINE
  • Tessel Games
  • brisk/grocer
  • Halden Air
  • OSTRAVA MOBILITY
  • Mori & Søn

01Network

One payment, end to end, in milliseconds.

Each payment passes five stages. Every stage is timed, logged and returned in the API response. Choose a currency pair to run one €1,000 card payment through the network and see the fees it carries.

Currency pair

01CardToken •••• 44170 ms02AuthoriseIssuer response+38 ms03NetworkScheme · 3DS frictionless+74 ms04RiskScore 0.07 · pass+119 ms05SettleBRL · T+1+146 ms
Authorised end to end
146 ms
Settles
T+1
Cut-off 13:00 UTC
Effective rate
0.86%
of transaction value
Local acquiring · São Paulo. Mid-market 1 EUR = 6.1240 BRL.
Fee breakdown for EUR 1,000.00 settled in BRL
LineEUR
AmountCard, consumer, card-not-present1,000.00
Velorum processing0.29% + 0.10−3.00
Scheme and networkPassed through at cost−1.62
FX margin0.40% over mid-market−4.00
Total fees8.62
Payee receivesBRL6,071.21

02Rails

Three rails. One ledger.

Cards, bank transfers and wallets share the same payment object, the same webhooks and the same settlement file. Add a rail without changing your reconciliation.

Rail A

Cards

Direct connections to six card schemes, with network tokens issued at first use.

CNP approval
91.4%
3DS frictionless
93.0%
Median issuer leg
38 ms
  • Local acquiring in 41 countries
  • Automatic account updater
  • Smart retries on soft declines
  • Interchange++ on every statement

Rail B

Account to account

Instant bank rails where they exist, batch rails where they do not, one API for both.

Instant rails
23
Median confirmation
1.9 s
Chargeback exposure
0.00%
  • SEPA Instant, Faster Payments, Pix, UPI
  • Payee name verification before send
  • Refunds to source account
  • Mandates for recurring debits

Rail C

Wallets

Device wallets and 14 regional wallets, tokenised and settled on the card ledger.

Wallets live
16
Checkout
1 tap
Mobile conversion
+6.2 pt
  • Device-bound cryptograms
  • QR and deep-link flows
  • Same fee lines as cards
  • One reconciliation file

03Coverage

46 settlement currencies.

Funds settle to your account in the currency of sale, on local rails. 27 currencies settle same day when the payment is captured before cut-off. No intermediary bank, no lifting fees.

Europe · 13
CodeCurrencySettlesCut-off UTC
EUREuroT+016:00
GBPPound sterlingT+016:00
CHFSwiss francT+014:00
SEKSwedish kronaT+013:00
NOKNorwegian kroneT+013:00
DKKDanish kroneT+013:00
PLNPolish złotyT+015:00
CZKCzech korunaT+014:00
HUFHungarian forintT+014:00
RONRomanian leuT+013:00
BGNBulgarian levT+013:00
ISKIcelandic krónaT+112:00
TRYTurkish liraT+111:00
Americas · 8
CodeCurrencySettlesCut-off UTC
USDUS dollarT+020:00
CADCanadian dollarT+019:00
MXNMexican pesoT+017:00
BRLBrazilian realT+113:00
CLPChilean pesoT+115:00
COPColombian pesoT+115:00
PENPeruvian solT+115:00
UYUUruguayan pesoT+214:00
Asia–Pacific · 14
CodeCurrencySettlesCut-off UTC
JPYJapanese yenT+005:30
CNYChinese yuanT+107:00
HKDHong Kong dollarT+008:00
SGDSingapore dollarT+008:00
AUDAustralian dollarT+005:00
NZDNew Zealand dollarT+003:00
KRWSouth Korean wonT+106:00
INRIndian rupeeT+111:30
IDRIndonesian rupiahT+108:00
MYRMalaysian ringgitT+008:00
THBThai bahtT+008:30
PHPPhilippine pesoT+007:30
VNDVietnamese đồngT+207:00
TWDNew Taiwan dollarT+106:30
Middle East & Africa · 11
CodeCurrencySettlesCut-off UTC
AEDUAE dirhamT+010:00
SARSaudi riyalT+010:00
QARQatari riyalT+010:00
KWDKuwaiti dinarT+109:00
BHDBahraini dinarT+109:00
ILSIsraeli shekelT+012:00
ZARSouth African randT+013:00
KESKenyan shillingT+110:00
NGNNigerian nairaT+210:00
EGPEgyptian poundT+210:00
MADMoroccan dirhamT+112:00

T+0 same business dayT+1 next business dayCut-off is the capture time for the stated settlement day.

04Developers

One request. Every timing returned.

A single versioned REST API with idempotency on every write, signed webhooks and typed SDKs for six languages. The response carries the time spent at each stage, so latency is something you can monitor, not something you are told.

API version, stable since March 2024
v3
SDKs: TypeScript, Python, Go, Java, Ruby, PHP
6
Idempotency key retention
24 h
Webhook signatures
Ed25519

Request

POST /v3/payments
Idempotency-Key: ord_88412-a

{
  "amount": { "value": 100000, "currency": "EUR" },
  "settle_in": "BRL",
  "source": { "type": "card", "token": "tok_7Hq2Lw0xR9" },
  "capture": "automatic",
  "reference": "Order 88412"
}

Response

HTTP/1.1 201 Created   // 146 ms

{
  "id": "pay_01JD9X3K4RV2",
  "status": "authorised",
  "timings_ms": { "authorise": 38, "network": 36, "risk": 45, "settle": 27 },
  "fx": { "rate": 6.1240, "locked_until": "2026-10-18T13:00:00Z" },
  "settlement": { "currency": "BRL", "net": 6071.21, "date": "2026-10-18" }
}

05Status

99.995% over 90 days.

Published live, per component, with a written post-mortem for every incident longer than five minutes.

All systems operational

Updated 17 Oct 2026, 09:42 UTC

90 days agoToday
Components
Component90-day uptimeMedian
Authorisation API99.998%142 ms
Card networks99.996%38 ms
Account-to-account99.991%1.9 s
Payouts99.994%—
Dashboard99.989%—

Recent incidents

  1. 11 Sep 2026

    Elevated authorisation latency, APAC 14 min

    p95 rose to 610 ms after a scheme gateway failover in Singapore. No declines attributed.

  2. 19 Aug 2026

    Payout file delay, BRL 6 min

    Settlement file to the local clearing house sent 6 minutes past cut-off; all payouts value-dated correctly.

  3. 6 Aug 2026

    Dashboard exports slow 22 min

    CSV exports above 2 million rows queued. API and payments unaffected.

06Customers

Measured by finance teams.

We moved 31 markets onto Velorum in one quarter. Card approvals in Brazil went from 84.2% to 91.7%, and the fee lines matched our model to the cent.
Inês Carvalho-RoeHead of Payments, Quayline Travel
The coverage table is the contract. When it says INR settles T+1 by 11:30 UTC, it settles T+1 by 11:30 UTC.
Daniel Okafor-LindTreasury Lead, Tessel Games
Interchange++ with every line itemised. Month-end close went from four days to one.
Mareike StrandChief Financial Officer, Brisk Grocer Group

07Pricing

Every fee, in one table.

Published rates, applied from the first payment. Interchange and scheme fees are passed through at cost and itemised per transaction.

Velorum published rates
ProductVelorum fee
CardsInterchange and scheme fees at cost+ 0.29% + €0.10
WalletsAs the underlying card+ 0.29% + €0.10
Account to accountInstant or batch rail0.20%, cap €1.90
FX, major pairsOver mid-market, locked at authorisation0.25%
FX, other pairsOver mid-market, locked at authorisation0.40%
PayoutsLocal rail, any of 46 currencies€0.20
DisputesRefunded if the dispute is won€8.00
Setup, minimums, monthly fees—None

08Questions

Answered in figures.

How is the 142 ms median measured?

From the moment our edge receives the request to the moment it returns an authorisation decision, across all card-not-present payments in the trailing 30 days, all regions. The p95 for the same period was 318 ms. Methodology and raw percentiles are published on the status page every Monday.

What does interchange++ mean on my statement?

Three lines per transaction: the interchange fee set by the issuer, the scheme fee set by the network, and the Velorum fee. The first two are passed through at cost. Nothing is blended and nothing is averaged.

How long does an integration take?

A single-market card integration typically goes live in 9 working days. Each additional market is a configuration change: same API, same webhooks, same reconciliation file.

Can we keep our existing acquirer during migration?

Yes. Velorum can route a set percentage of traffic, by market or by BIN range, while you compare authorisation rates. Network tokens can be migrated without asking customers to re-enter card details.

Where is data stored?

Card data is tokenised at the edge and held in the region of capture: Dublin for Europe, Virginia for the Americas, Singapore for Asia–Pacific. Each region runs active-active across three availability zones.

Is there a minimum volume?

No. The published rates apply from the first payment. Above €25m a month we offer a volume contract with a fixed Velorum fee per transaction.

09Contact sales

Send us your markets. We send back the numbers.

A coverage check, a projected authorisation rate and a priced proposal for your volume, within one working day.

Demo form. Nothing is sent or stored.