A Nayax VPOS Touch is a contactless payment terminal built for unattended machines. It takes cards, phones and watches, it runs its own cellular or wi-fi connection, and it reports every result back to the machine over MDB. That last part is why it suits a photo booth: the booth learns whether the payment worked, rather than guessing. This is the install, in the order you actually do it, with the parts that trip people up called out.
Order it before you need it
The terminal will not do anything useful out of the box. Nayax has to provision it against your merchant account first, and that carries a lead time rather than being an instant activation.
Order early. Build and test your booth flow with a stand-in reader while you wait, because nothing about designing the screens depends on the physical terminal being present.
What you need alongside it
The reader alone is not a payment system. For a Windows photo booth you also need a bridge, because a PC has no MDB port.
- The terminal. Ships with an antenna, a cable and a QR sticker.
- A Qibixx MDB-USB interface. Converts the MDB harness to a serial port Windows can open.
- Power for the MDB side. The bus needs supplying, and this is where grounding problems begin.
- Booth software that speaks MDB. Not every product does. Some fake it with a keystroke box, which is a different thing.
Mounting it in the cabinet
Put the reader where a hand naturally goes, at roughly the height a card gets tapped without stooping, and on the same face as the screen. Guests look at the screen, so a reader on a side panel gets missed.
Keep the antenna clear of the cabinet steel. A metal enclosure is very good at blocking a cellular signal, and a terminal that cannot reach the network cannot authorise anything.
Leave slack in the harness. You will open this machine again, and a taut cable is how connectors get pulled.
Connecting it to the software
With the bridge in place, Windows sees a serial port. The software side is then two fields: which reader, and which port.
Get this wrong and the symptom is silence rather than an error, because the software is listening on a port with nothing on it. If the reader never responds, check the COM number before checking the hardware.
Deciding what happens after the tap
The interesting configuration is not the connection. It is what the booth does with an approval and a decline, because those are two different journeys and most setups only design one.
An approval should move the guest straight into the session. A decline should say something useful and offer another go, rather than dumping them back to a start screen with no explanation. Both need a destination set.
What the guest actually sees
Two screens carry the whole payment experience, and both are easy to neglect.
The first tells them the reader is live and waiting. Without it the screen sits unchanged after the tap, which reads as a fault. The second handles the decline, and it should be written in plain language rather than a processor error code.
Testing before you open
Run a real card through it yourself before the venue sees it. Not a test mode, an actual transaction on an actual card, then check it appears in your Nayax dashboard and settles.
Then run three or four sessions back to back. One proves very little. Several in a row surface heat problems, a paper path that catches, and a terminal that struggles to settle under repeated use.
What went wrong on our first install
Two things, and neither was the terminal.
The first was connectivity alerts at a university site, which looked like a hardware fault and turned out to be the venue network dropping. The second was a grounding issue on the bridge board that caused random resets, fixed by closing jumpers J1 and J6.
Both cost time because both presented as payment failures. Neither was.
Budgeting for it
Two costs, and operators reliably forget the second. There is the terminal itself, which drops in price as you order more of them, and there is a per machine monthly plan that runs whether the booth is busy or idle.
Add the bridge board on top, and card processing on top of that. We put the current published figures for all of it, sourced and dated, in the Nayax MDB write up rather than repeating them here.
Frequently asked questions
Does a Nayax VPOS Touch need wi-fi, or does it use cellular?
It can do either. Cellular is more reliable in a venue whose wi-fi you do not control, and venue wi-fi is exactly what caused our alerts.
Can one terminal serve two machines?
No. One terminal per machine, since it is reporting to that machine’s controller over the bus.
What happens to a session if the network drops mid payment?
The authorisation fails and no money moves. The important thing is that your software handles that as a decline rather than hanging.
Do guests need the Nayax app?
No. They tap a card or a phone the same way they would anywhere else. The QR sticker in the box is optional.
Building a booth around a VPOS Touch? VertexBooth talks to it over MDB through a Qibixx bridge, and ships a stand-in reader so the flow can be built before the terminal is provisioned. Download and test it.
The protocol underneath this is covered in Nayax MDB on a photo booth. Terminal pricing comes from the Nayax store, checked 8 September 2026.
