The payments layer
One integration. Every terminal, every market.
From the driver's tap to a compliant receipt, Bolt runs the money flow — across any terminal, any bank, any CSMS, in any market — while your bank, your brand, and your customer stay yours. You go live; you don't go build.
Pre-auth placed
incremental · no frozen hold
Captured exact amount
card-present · your acquirer
Fiscal receipt filed
tax authority · signed
One layer, everything connected
Bring what you already run. Bolt makes it work together.
Bolt sits between three worlds and runs the whole thing as one system: your payment terminals (in front of any acquirer, through our own terminal applications), your charging network (any CSMS, over OCPI), and your invoicing & fiscalization.
See it in action
The whole charge, on screens you'll recognize.
What the driver sees
Tap, charge, done. No app, no account.
What you see
Every session, settlement, and exception in one dashboard.
What the tax office sees
A compliant fiscal receipt, signed and filed.
Tap to charge
Card · Apple Pay · Google Pay
What we run, so you don't
Four jobs. One layer.
Any terminal, any network — talking as one.
Bolt's own terminal apps sit in front of the bank you already use, and we run over any OCPI back-office. Nothing to rip out, nothing to lock you in.
The driver's tap, handled right.
Card, contactless, Apple Pay, Google Pay — no app, no account. Incremental pre-authorization, so there's no big frozen hold and no surprise on the driver's card.
Tap to charge
Card · Apple Pay · Google Pay
Every charge adds up — even the messy ones.
Half-sessions, drop-offs, partial captures, disputes — and the charge records that don't line up with the invoices — reconciled automatically, so your team never chases them.
A receipt the tax office accepts.
Country-specific fiscal receipts, with the signature wired all the way to the terminal — the piece the standard leaves open and everyone else leaves to you.
Why a standard isn't enough
A standard gets the terminal talking. It doesn't run the money.
The industry's OCPI payments module defines how a terminal and a charging network exchange a payment message — and stops there. It says nothing about how the money flows, fails, refunds, reconciles, or gets taxed, and it leaves the pre-authorization strategy, the fiscalization, and every cross-system case to you. Bolt is the layer that decides it, runs it, and keeps it correct as acquirer APIs, OCPI versions, and CSMS releases keep moving.
Built like infrastructure
Works with everything you already run.
Terminals
Runs on any modern payment terminal (Linux or Android) — your brand on the screen. Live today on:
We integrate any terminal, on us — new hardware added fast.
Charging network
Any OCPI 2.1.1–2.3.0 back-office. Nothing ripped out — you keep your CSMS.
Your bank
Bring your own acquirer. You stay the merchant; the money never touches Bolt.
Markets
The payments layer for EV charging across Europe — AFIR-compliant ad-hoc payments and country-specific fiscalization, already running in production and expanding market by market. North America and the Middle East next.
Security
Card data never touches the Bolt backend (PCI-DSS scope minimised). GDPR-compliant.
Reliability
99.9% uptime, monitored 24/7.
Go-live
Live in weeks — not a year-long build.
Book a demo — we handle the integration and get you live.
What it changes, by team
One layer. Off four teams’ plates.
Operations
Fewer failed ad-hoc sessions. Drivers tap and charge — no app, no account.
Finance
Terminal payments reconciled against charging sessions and payouts, automatically. No month-end spreadsheet hunt.
Support
Find the receipt, the session, and the payment reference in one place.
Expansion
Switch acquirer, terminal, or country without rewriting your CSMS.
Already integrated a terminal?
Already take card payments through a terminal integration?
Connecting a terminal is the easy part. Running multi-acquirer routing, the edge cases, reconciliation, and country-by-country fiscalization — and keeping it all correct as standards move — is the part Bolt owns, on any CSMS.
You keep the terminal integration you already have. Bolt takes over everything that breaks after the tap.
Keep your stack. Keep your money.
Any terminal. Any acquirer. Any network. One layer.
Mix and match terminal providers and acquirers, countries, currencies, and tariffs — on one platform, with no lock-in. Your bank stays your bank: we never step between you and your money. That's how the OCPI payment standard is designed — the operator is the merchant, settled to its own bank, not the payments vendor.
Standards & security
Standards-based and GDPR-compliant, architected so card data never touches our backend (PCI-DSS scope minimised). Going live is a setting you switch on, not a project you staff.
End to end
Going live is a setting, not a project.
From the driver's tap to a compliant, fiscalized receipt, every part of the charge payment resolves on one layer — across any terminal, any acquirer, any CSMS. One integration, one set of economics — and always your bank, your brand, your customer. Standards-based, GDPR-compliant, and architected so card data never touches our backend, so you switch it on rather than staff it. Live in weeks, not a year-long build.
Commercial model
How pricing works.
A fixed per-terminal subscription plus a usage fee on ad-hoc card volume. Your exact rate depends on your terminal, acquirer, country, and volume — we'll quote it on a short call. Integrating a new terminal is free, and there's no rip-and-replace.
Plug in payments. Skip building the infrastructure.
You'll never build a payments stack. You'll never maintain one either.