MDB Protocol Settings
The MDB protocol settings allow you to configure the MDB protocol capabilities of the terminal. The majority of these settings are considered advanced configurations, meaning they can only be adjusted on the advanced settings page.
See MDB 4.3 spec documentation for more information about the MDB protocol and detailed explanation about the settings.
Setting the MDB device address
The MDB device address setting can be configured in the basic and advanced settings page. This setting configures the terminal to work as either Cashless 1 or 2 device. This can be done by setting the value to the cashless command device address.
MyPayter Key | Expected Value |
|---|---|
address | For Cashless device 1 = 16 For Cashless device 2 = 96 |
Setting the MDB protocol Level
The MDB level can be configured in both the basic and advanced settings. This setting determines the highest level of MDB communication that the terminal will support.
MyPayter Key | Expected Value |
|---|---|
level | 1, 2 or 3 |
Setting the MDB protocol Country / Currency Code
The country/currency code setting configures the terminal's response to the SETUP - Config Data command. When the VMC sends a SETUP - Config Data command to the terminal, it will receive a response containing the configured currency code.
MyPayter Key | Expected Value |
|---|---|
country-currency-code | See MDB 4.3 spec sheet appendix A1 for ISO 4217 code. |
Setting the MDB protocol to inline
The inline setting controls whether communication occurs inline. When the setting is set to true, the response will be sent directly after the request, while setting it to false will result in the response being sent after the next poll.
MyPayter Key | Expected Value |
|---|---|
is-inline | true or false |
Setting the MDB protocol scale-factor
Th scale-factor setting is primarily employed for currencies with significantly high denominations, such as the Iranian rial, where 42,000 rials equal 1 euro. Such values may not fit well on vending machine segment displays. This setting allows for scaling down such values.
For more information, refer to the MDB 4.3 spec sheet for details on the scaled price formula.
MyPayter Key | Expected Value |
|---|---|
scale-factor | integer value |
Setting the MDB protocol decimal-places
This setting determines the precision of the price, specifying the number of decimal places it should have. For instance, when configured with two decimal places, a scaled price of 145 will have an actual price of 1.45 euros.
For more details on the scaled price formula, please consult the MDB 4.3 spec sheet.
MyPayter Key | Expected Value |
|---|---|
decimal-places | integer value |
Setting the MDB session state timeout
The session state timeout setting controls when the terminal return to MDB enabled state. When the terminal is in MDB session state and there is no activity within the time-limit, the terminal will send a session cancel request.
MyPayter Key | Expected Value |
|---|---|
mdb-session-state-timeout | Time-out in seconds |
Setting the MDB vend state timeout
The MDB vend state timeout settings control when after a vend request neither a "vend approved" nor a "vend failed" is received, the terminal will return to enable/session state after the defined time-limit period.
MyPayter Key | Expected Value |
|---|---|
mdb-vend-state-timeout | Time-out in seconds |
Setting the MDB protocol response-time
This refers to the maximum amount of time the terminal will need to respond to any command issued by the VMC (Vending Machine Controller).
MyPayter Key | Expected |
|---|---|
response-time | response-time in seconds |
Setting the MDB protocol default session payment media id
When the terminal is not in always-idle mode, the user must press a start button to enter the session state. If the button is pressed, the terminal will send a BEGIN SESSION message to the VMC, which will include the value of this setting.
See Begin Session, Level 2/3, Z4-Z7 in the MDB 4.3 spec sheet for more information.
MyPayter Key | Expected |
|---|---|
default-session-payment-media-id | Media ID in integer (e.g value 3000 is send to the VMC as 00000BB8) |
Setting the MDB protocol default session payment type
When the terminal is not in always-idle mode, the user must press a start button to enter the session state. If the button is pressed, the terminal will send a BEGIN SESSION message to the VMC, which will include the value of this setting.
See Begin Session, Level 2/3, Z8 in the MDB 4.3 spec sheet for more information.
MyPayter Key | Expected |
|---|---|
default-session-payment-type | payment type in integer(e.g set the value to 3 for Discount percentage factor) |
Setting the MDB protocol default session payment data
When the terminal is not in always-idle mode, the user must press a start button to enter the session state. If the button is pressed, the terminal will send a BEGIN SESSION message to the VMC, which will include the value of this setting.
See Begin Session, Level 2/3, Z9-Z10 in the MDB 4.3 spec sheet for more information.
MyPayter Key | Expected |
|---|---|
default-session-payment-data | See MDB 4.3 spec sheet |
Setting the MDB protocol multi-lingual
This setting is part of the Optional Feature Bits in 4.3 spec sheet. It is used to enable the capability of the terminal for expanded currency mode.
MyPayter Key | Expected Value |
|---|---|
feature-multi-lingual | true or false |
Setting the MDB protocol always-idle
This setting is part of the Optional Feature Bits in 4.3 spec sheet. This setting enables the terminal capability for always-idle mode.
MyPayter Key | Expected Value |
|---|---|
feature-always-idle | true or false |
See MDB Example configuration use cases | Non-Always-Idle and MDB Example configuration use cases | Always-Idle for the difference between the settings.