Skip to main content

Fintech & payments

We take payment on unattended devices — cash, card, QR — and reconcile daily takings against what reached the account. 14M transactions.

Fintech
Anti-fraud
Risk detection and protection.
Billing
Recurring charges, tokenisation.
Payment routing
Rule-based payment routing.

Case

Self-service equipment has to take money and issue a fiscal receipt with no cashier present. We build the layer between the device and the bank: card and cash acceptance, the fiscal registrar and a receipt that reaches the customer instead of staying in the machine's memory.

Every transaction is tied to a device and a shift, so reconciling takings is a report rather than an audit. The equipment keeps working offline, and the transactions catch up with the server once the connection returns.

This is how the self-service car washes, vending machines and terminals we have connected work.

Where money disappears in payments

Taking payments is the easy part; what follows is hard. How much came in cash, how much by card, how much is stuck in incomplete transactions, and why the shift total is off by a few hundred. Without data from the device itself this cannot be untangled.

The second problem is taking money where there is no cashier. The device stands outdoors, runs around the clock, and must reliably take payment, deliver the service, and record both events so they can be reconciled later.

What we do

Unattended payment acceptance

Bill and coin acceptors, contactless terminals, QR payment from a phone with no app to install.

Revenue reconciliation

What the device accepted matched against what reached the account. Shift discrepancies surface the same day, not at month end.

Incomplete transactions

Paid but not delivered, or the reverse — logged separately and raising an alert.

Acquiring integration

Connection to bank processing, receipts and fiscalisation where required.

Device-level fraud checks

Enclosure opening, counter resets, mismatch between dispensed and paid — all recorded.

Owner reporting

Revenue per site and per device, trends, payback on each unit.

What it runs on

MDB and ccTalk for payment peripherals, integration with bank acquiring, Modbus to talk to the equipment controller. Node.js and PostgreSQL on the server. We do not build banking products and do not work with cryptocurrency: our part is taking payment at the device and accounting for it honestly.

Our evidence

Over 14 million payment transactions processed by the self-service car wash network system. Years under load, cash and cards together, reconciled daily.

Frequently asked

Do you build a payment service?
No. We build payment acceptance at the device and the accounting around it: integration with your existing acquiring, cash acceptor handling, reconciliation. We are not a licensed payment operator and make no such claim.
Can we take payment without a terminal?
Yes, via QR: the customer points the camera, pays in their banking app, the device receives confirmation and delivers. Cheaper than a terminal at every site.
What about fiscalisation?
It depends on your activity and obligations. Technically the integration is possible; what exactly you need is a question for your accountant, and we do not replace one.
Do you accept cryptocurrency?
No. That is a deliberate decision: we do not work with crypto projects.

Plain explanations without marketing — useful even if you never hire us.