MDB 4.3 remote vend: what changes from MDB 4.2

MDB 4.3 remote vend can request a specific product on a machine that supports and enables the feature. A compatible credit-based setup can still let an MDB 4.2 machine serve a courier who presses the product button.

MDB versions and cashless levels describe different things

MDB is the communication link inside the machine. The VMC, or vending machine controller, manages the exchange with connected payment equipment. For an operator, it is the controller whose capabilities you need to establish.

MDB 4.2 and 4.3 are specification versions. Cashless Levels 1, 2 and 3 describe supported functions within that system. Basic payment exchanges sit at Level 1; Level 2 adds functions such as restoring value to a stored-value card. Level 3 includes additional optional functions.

The MDB 4.2 specification already includes cashless Level 3. A supplier saying “Level 3” therefore leaves the Remote Vend question open.

Most machines in the field use MDB 4.2; that is also what Vending on Track told PickVend in October 2026. Confirm your own fleet rather than assigning a version from its age.

Credit-based pickup leaves the product choice to the courier

Separate permission to vend from the choice of product. In the credit-based flow, the connected device authorises the purchase and the courier makes the selection at the machine.

Vending on Track confirmed to PickVend in October 2026 that its default flow is courier-selects: one credit per item, followed by the courier pressing the product button.

Treat that as the provider’s stated default flow. Confirm support on your particular machine and ask how each item’s authorisation is handled.

Also ask what happens if the courier presses the wrong button. Check whether the selected product is matched to the order before approval, and how a failed vend affects the remaining credit.

MDB 4.3 remote vend needs an enabled Remote Vend feature

For product selection through the MDB cashless interface, check Level 3 support and the Remote Vend option on the controller and connected device.

Check both the controller’s feature level and whether remote selection is enabled. That is more specific than a label saying “MDB compatible.”

With the feature working, the connected device can request the required product selection. The controller still handles the vend and its outcome. The MDB 4.3 specification describes that selection-request exchange.

Ask your telemetry supplier to demonstrate the cloud command reaching the correct selection. Check the product mapping and the result reported back after dispensing.

An office-lobby machine shows what the courier must do

For illustration, take a snack machine in an office lobby. The order contains a packet of crisps and a chocolate bar.

With the confirmed courier-selects flow, the system authorises the crisps purchase. The courier presses the crisps button and collects the packet. The process repeats for the chocolate bar.

With supported remote selection, the integration requests the relevant product selections at collection. The courier collects the released items. Design the process so products are released when collection is ready.

In either case, test the actual machine. Check that the order names match the labels and selections. Confirm what happens if the crisps fail to drop or the courier collects an incomplete order.

Ask the manufacturer about the VMC and its firmware

Start with the manufacturer or its authorised service partner. Give them the machine model, serial number, controller details and current VMC firmware version.

Ask where to find the firmware version in your machine’s service information. Request the supported MDB specification version, cashless feature level and explicit confirmation of the Remote Vend option.

Use a direct question: “Can this controller, running this firmware, accept a product-selection request from the connected cashless device?”

Then ask your telemetry supplier whether its hardware, firmware and cloud interface support that function on the same setup. A replacement payment reader needs checking against the controller too.

If an update is proposed, request the applicable firmware and a demonstration on your configuration. Do not assume that installing new telemetry changes the VMC’s capabilities.

Test the collection flow before choosing an integration

Run a supervised order through the complete setup. Check product selection, authorisation, dispensing, failure handling and the record returned to the order system. Test stock availability separately.

If you use courier selection, verify the instructions and how credit is issued for each item. If you use cloud selection, verify the exact product requested. Agree how the system handles incomplete collection.

Ask your machine or telemetry supplier about a supported connection, or assess a direct integration you can maintain.

PickVend is built to the published APIs and is another practical option to assess. Platform access is opened one by one. Its intended flow sends orders to the machine, syncs stock from the machine’s cloud and uses a one-time collection code. The intended handover needs no staff or tablet. Check which selection method your installed machine supports.

Check whether your machine qualifies: pickvend.com/compatibility

Does cashless Level 3 guarantee remote product selection?

No. Check explicit Remote Vend support and whether the feature is enabled. Level 3 alone leaves that question unresolved.

Can an MDB 4.2 machine support delivery collection?

Potentially, through a compatible credit-based flow where the courier selects locally. Confirm the VMC, connected device and provider’s workflow.

Will a firmware update add remote selection?

Ask the manufacturer to confirm that for your controller and proposed firmware. Require a working demonstration before treating the machine as compatible.