How payments work where there's no cashier — vending, EV, parking, fuel, car wash — what MDB is, and why unattended is harder than countertop POS.
An unattended payment system takes payment with no human present — a vending machine, EV charger, parking gate, fuel pump, or kiosk. That sounds like a normal terminal, but it isn't: there's no cashier to recover from an error, the hardware often lives outdoors, and the certification bar is higher. The protocol that ties many of these machines together is MDB, the Multi-Drop Bus.
The defining trait is simple: no operator is present at the point of sale. A staffed countertop terminal has a cashier who can re-run a declined card, hand back a receipt, or call support when something hangs. An unattended terminal has none of that. It has to complete the entire transaction — including every error, timeout, and reversal case — entirely on its own, then do it again ten thousand times in a parking garage no one visits.
That single difference cascades into stricter reliability requirements, tougher security expectations, and certification test plans that are genuinely harder to pass than their indoor equivalents.
Self-service retail, MDB-connected
Charger payment systems
Meters, gates, garage kiosks
Forecourt & outdoor pay-at-pump
Pay-at-the-bay & loyalty
Card & mobile-based
MDB stands for Multi-Drop Bus — the industry-standard serial protocol that vending machines and many unattended devices use to connect peripherals to the machine controller. Bill validators, coin mechanisms, and cashless payment readers all hang off the same bus. A single MDB bus can connect up to 32 peripherals with combined power and data over one connection.
When a customer taps a card on a vending machine, the cashless reader talks to the machine over MDB: it tells the controller a payment is authorized, the controller vends the product, and the reader finalizes the sale for the exact amount. It's a clean idea wrapped in a famously fiddly protocol — which is why a clean API in front of MDB is worth so much to operators.
Outdoor and unattended environments carry their own card-brand and processor test requirements on top of standard EMV Level 3. The reasons are physical and procedural.
| Factor | Indoor / attended | Outdoor / unattended |
|---|---|---|
| Error recovery | Cashier intervenes | Must self-recover |
| Environment | Climate-controlled | Weather, dust, tampering |
| Connectivity | Generally stable | Often intermittent |
| Transaction flow | Standard | Unattended-specific timeouts & flows |
| Cert complexity | Baseline | Additional requirements, longer timeline |
This is why an outdoor pay-at-pump certification against a strict processor spec can take longer and cost more than an indoor counter terminal — and why catching the unattended-specific issues during pre-certification, rather than after submission, matters even more here than usual.
A hardware-agnostic unattended platform is one where the payment software works across multiple terminal manufacturers and models instead of being welded to a single vendor's device. For an operator, that's the difference between choosing hardware on cost, availability, and form factor — and being held hostage by one manufacturer's roadmap and pricing. It also means a device going end-of-life doesn't force a ground-up rebuild of the payment stack. Certified stacks that run on PAX, Ingenico, and Verifone give operators room to move.
Hardware-agnostic platforms for vending, EV, parking, petroleum, and car washes — certified stacks with MDB integration, engineered for uptime.
See unattended platforms