Nayax MDB Flag Change Saved but Not Applied? Check Send to Queue

You have saved a new MDB flag in Nayax Core, but the vending machine still behaves as before. Start by checking whether the update was sent to the physical device. In its MDB flags guide, Nayax explicitly says that saving stores the configuration in Core; saving alone does not update the machine.

Check the two stages separately

The documented route is Operations > Machines, then the relevant machine name and its MDB tab. The operator selects the appropriate MDB Flags value and saves. At that stage, Nayax describes the setting as stored in Core but not yet applied to the physical device.

The guide then directs the operator to select the MDB attributes to update and use Actions > Send to Queue. It says this step is required for the flag change to take effect. If your review stops at the save confirmation, it has not established that the reader is using the requested setting.

This is a description of the provider's workflow, not evidence that an update has reached your device. Keep the machine identity, intended setting and update action together when asking the responsible technician to investigate. A saved screen alone cannot explain the physical machine's current behavior.

Confirm the flag is appropriate before sending it

Nayax lists Administration access and knowledge of the target machines among the prerequisites. It also warns that older machines may need specific flags and may fail to process card transactions with an incompatible selection. Have the machine manufacturer and payment provider confirm the required setting for the identified controller and reader.

A protocol level and an MDB flag are different configuration questions. Our MDB Level 3 selection-first guide explains why the customer sequence must be confirmed alongside the level. Do not infer a suitable flag from the words MDB-compatible alone.

Unchanged behavior is not a reason to try every flag

The official reference includes advanced flags that ignore controller messages or override vend-success verification. Nayax warns that some can charge a customer even when no product is delivered. Those settings should not be treated as routine fixes for an update that has only been saved in the cloud.

First establish the intended mode and whether the documented update action was completed. If behavior remains wrong, give support the machine and device references, the observed customer sequence and the steps already taken. Ask for the applicable diagnosis rather than changing unrelated payment options by trial and error.

Verify the transaction after the update

Nayax calls for a test transaction after each flag change. Agree a provider-approved check on the actual installation and record what the customer does, the displayed amount, payment outcome and delivered product. The purpose is to verify the requested behavior before returning the machine to normal trading. This article reports no completed field test or configuration change.

For a new equipment order, include configuration ownership and the final transaction demonstration in the handover scope. A useful completion record distinguishes the setting saved in Core, its update to the device and the observed result.

Request Get My Custom Quote with your destination, product format, proposed payment reader and required customer sequence. Compare the equipment range against that brief. The Nayax instructions do not establish that every WEIMI model includes Nayax Core or supports any particular MDB flag.