If your vending brief says “choose the product, then pay,” write that sequence into the purchase requirements. The label MDB Level 3 is useful technical information, but the supplier still needs to confirm how the proposed controller and payment reader will operate together.
Nayax’s VPOS Media MDB Level 3 Always Idle guide describes a device that waits for the customer to select a product on the machine before initiating payment. It calls this Selection First operation. That is a concrete workflow to discuss with an equipment supplier.
The guide’s quick reference lists Card Reader MDB Level, Transaction Start Method and MDB Level 3 Optional Features as separate fields. The example specifies level 3, Product as the start method and the Always Idle state as an enabled optional feature. These separate entries are a reason to ask about the complete configured mode, rather than accepting the level number as the whole answer.
Nayax’s MDB levels reference warns that not every vending machine supports every level. It says to verify the machine firmware and vending machine controller compatibility before changing a level, because incorrect configuration can prevent transactions.
For a new order, request the proposed controller, firmware and payment reader references. Ask the responsible suppliers to confirm the selection-first sequence for that combination. For an existing cabinet, provide its actual identification before requesting a change. This article does not confirm Always Idle support on an unidentified WEIMI machine.
The VPOS Media example also includes other attributes and an operator-set Default Credit value. Its notes describe the table as essential configuration and say additional attributes may be required. It is a guide for a named system, not a universal recipe for all MDB readers.
Have the payment integrator identify the applicable instructions and configuration for your equipment. Keep the agreed settings with the handover record. A purchasing review can establish what must be demonstrated without asking an operator to change live payment parameters from a general article.
Ask for a demonstration on the offered configuration: show the ready screen, select an available product, follow the payment prompt and complete the purchase. Record the selected product, displayed price, charged amount and delivered item. Agree checks for cancellation and unsuccessful payment with the provider as well.
These are proposed acceptance checks, not completed WEIMI tests. They answer whether the demonstrated system provides the requested journey. They do not establish settlement timing, offline operation or every payment method; include those separately if they matter to the project.
For the wider distinction between device communication, reporting and application integration, see our MDB, DEX and API comparison. For this purchase decision, the key deliverable is a confirmed selection-first workflow tied to identified hardware and configuration.
Share your destination, equipment format, payment provider and intended customer sequence with WEIMI. Ask for the supported configuration and a clear demonstration scope. Get My Custom Quote.