Integrations
No single kind of hardware fits every location — a busy lobby, a gym, a 24-hour plant floor and a four-person office rarely want the same thing. Different hardware across your fleet is what growing looks like. Connect each one and its sales land in the same place, reconciled against the same counts.
No readers, no cellular plan, no payment rail. Nothing in our pricing is recovering the cost of a device, so we have no reason to push you toward one vendor or away from another.
Everything above the connection branches on what a provider can do, never on who it is. Adding the next one is a new adapter beside the others, not a rewrite of anything that already works.
Vending, micro markets, kiosks and smart coolers sit side by side in the same fleet and the same reports. Whatever you add next, it belongs to the same operation.
Connect with a read-only token you generate yourself in Nayax Core — we never ask for your password, and we only ever read. Sales arrive on a schedule through the day, matched to the market and the product, and your shelf figures update without anyone counting anything.
The adapter is written and registered; what remains is switching it on against a real account. Cantaloupe sends new data going forward rather than backfilling history, so an upload path for your existing reports is part of the same work.
Crane · 365 Retail Markets · Coinco · AirVend · Greenlite
VDI is a published NAMA standard rather than a vendor, which is why it is a single entry instead of five. Any provider that implements it can deliver to the same endpoint, and we record which one actually sent each reading — so adding the next provider on the list is configuration, not another integration project.
Early access
Nayax connections are in early access. We are onboarding the first operators by hand so we can sit with you through the setup and fix anything your fleet turns up — tell us what you run.
Being straight with you
Every automatic sales feed has edges. Here are ours, before you find them.
A card reader reports what it processed. On a market that also takes coins, the feed is a floor rather than a total — so we show the reader’s own stock figures beside ours, and the gap between them is the part nobody is metering.
We read; we never move money. A QR support ticket from a customer lands with the time of their visit so you can find the transaction quickly, but the refund itself happens where it always has.
Without one, a reader takes payments the provider cannot attach to a product: revenue arrives and stock never moves. This is the setup step that quietly breaks everything downstream, so we check for it and say so plainly rather than leaving you to notice over weeks.
Automatic sales replace your restock estimate only for a period the feed demonstrably covered end to end. Any gap and your count stays authoritative. That is the conservative direction on purpose — a number on a document you may hand to an accountant should never quietly come from an incomplete feed.
Everything works on your own counts from day one. Connect a feed whenever you are ready — it only ever adds to what you already have.
