Integrated POS

Version 4.0.24.3

New Features

| Added Currency Code in Pulse Modes

We have added a display of the currency code to improve the way we display prices in all pulse modes (Single Pulse, Multi Price, Multi Pulse and Count Up). From now on, a currency code (i.e.: USD, EUR, GBP, ILS…), taken automatically from the currency payment definition of the machine, will be displayed next to the price.

Below is the updated appearance of the screens, now including the additional currency code:

Single Pulse:	Linear Increment:	Count Up:
Multi Pulse:	Multi Price:

Improvements

| Improved haptics (audio beeps) in contact transaction flow

To make our beeps more precise and meaningful for the customer, we have removed one beep from the contact transaction flow.
This beep, which indicated successful authorization, caused the consumer to remove their card, even though the transaction was not yet complete.
From now on, at the “approved” stage, there will only be one beep to indicate that the transaction is complete, and the card may be removed from the slot.

Bug Fixes

• Fixed an issue with Germany country code ISO number which caused AMEX cards not to be accepted in Germany.
• Fixed an issue with the cellular modem which could cause communication fault M02. This fix identifies a specific issue in the modem and fixes it automatically.
• Fixed an issue in which the transaction was cancelled when using the contactless read source, due to accidental touches on the device buttons.
• Fixed an issue in Marshall protocol where Discover card data was identified as Diners.
• Fixed an issue in which specific types of CNOUS cards were not recognized correctly.
• Fixed an issue in which the device was reset after receiving incoming pulses in a short time frame.
• Fixed a known issue in Pulse Count-Up mode that was found on the last version, 4.0.24.1, in which prepaid cards were given a negative value during a revalue.
• Fixed an issue in which internal device errors triggered an event of “File System Error” in the Last Alerts report, preventing devices from working correctly.

Known Issues

• A GUI issue in Pulse Count-Up mode, in which the counter is overlapping after pressing the STOP button.

Version 4.0.24.1

New Features

| New Self-Service Screens!

We’ve elevated your troubleshooting experience with the latest firmware release by making our guides easily accessible directly from the VPOS Touch and ONYX screens. Instead of displaying the traditional Cash Only error screens, your card readers will feature dynamic QR codes which, when scanned, will direct you to a troubleshooting guide to help you resolve the issue. This feature is designed to save you valuable time, allowing you to resolve issues independently and to promptly resume product sales.

Old Layout                                    New Layout

This is what the troubleshooting guide looks like:

Improvements

| New Inhibit Screen on Single Pulse Mode

Inhibit is an indication from the machine that means it is either in use or in fault.

In the event of an inhibit indication in Single Pulse mode (when one machine is connected to one device), this new screen is displayed to better describe the machine’s condition, whether there is an error or it is in use.

Old Layout                                    New Layout

Bug Fixes

• Fixed an issue in which no indication screen was displayed during the Inhibit state in single pulse mode.
• Fixed an issue found in the previous version (4.0.23.11) regarding Pulse Mode in which dummy cash reports were sent due to ghost transactions. This happened because of the Pulse Invert or Pulse IN Counters parameters configuration.
• Fixed an issue found in the previous version (4.0.23.1) regarding Multi Inhibit in Pulse Mode. When Inhibit was triggered on a specific machine (i.e. machine #2), all other machines were considered as the following number (i.e. machine #3 was considered as machine #4 and so on).
• Fixed an issue regarding Pulse Count In mode, in which Prepaid cards got a negative value during the Revalue process.
• Fixed a known issue with the cut text on the revalue screen in Hungarian, Latvian and Russian.
• Fixed a known issue of an incorrect Dutch translation of the error message “Try Another Card”.
• Fixed a known issue in which the remote start functionality didn’t work with VPN communication mode.

Known Issues

• In Pulse Count Up mode, Prepaid cards may get a negative value during the Revalue process.

Version 4.0.23.11

New Features

| Enhanced LAN Communication Capabilities

We implemented new LAN communication capabilities giving it functionality similar to that of cellular communication.

This means that from now on, it is possible to use Monyx Wallet, MoMa 2.0, and Marshall communication services along with the current LAN benefits.

These LAN communication capabilities make it possible for customers to pay with Monyx Wallet and for operators to use MoMa 2.0 to manage their operations in installations such as underground parking lots with poor cellular coverage or in laundromats where many laundry machines require internet connections and cellular data is not cost effective. Machines that use the Marshall Protocol can now also use LAN communication services for external communication.

| New Screens that Display Tariffs and eReceipts for EV Charging Transactions

The law requires that tariffs and eReceipts for EV (electric vehicle) charging transactions be displayed. We’ve therefore added a tariff screen to the device for integrations that use the “remote start” API.

The Tariff screen, which displays the information sent by the 3^rd party integration server, is displayed right after the terminal is remotely activated.

In addition to the Tariff screen, a URL can also be sent and displayed as a QR code for the consumer to scan. Though this option was already available, it has been technically enhanced and improved for this transaction flow.

An example of the new screens:

This feature helps improve the user experience for your consumers and ensures you comply with local regulations. This feature can be configured in one of two ways:

1. Automatically – configuring the screen to display the tariff screen for a certain amount of time (in seconds) and then having it automatically continue onto the payment option screen. In this scenario, the transaction can be canceled at any time by pressing the red X button.
2. Manually – giving the consumers manual control of the process steps. In this scenario, the tariff screen includes a button that brings the consumer to the payment screen when pressed on. If the button is not pressed, the action will be canceled after a timeout.

To activate and configure the Tariff and eReceipt screens in Nayax Core according to the desired experience, you need to configure the following attributes:

1. For the Tariff screen:
   1. Attribute 216 – Approve button UI display duration – on the Machines page – under VPOS Touch.
      This attribute is used to set the amount of time the OK button will be displayed.If the value is 0 – the OK button will not be displayed, and the attribute 206 configuration will be considered (see below).If the value is between 1 to 60, then the OK button will be displayed for the given duration (in seconds) and the transaction will be cancelled if the button is not pressed.
   2. Attribute 206 – Informative State Display Timeout – on the Machines page – under VPOS Touch.
      This attribute is used to set the amount of time for the Tariff screen to be displayed before continuing to the “Present your card” screen (In the case of attribute 216, it is set to 0).

2. For the eReceipt screen with a dynamic QR code:
   1. Check the “Enable eReceipt on Transaction end” checkbox – on Machines page – under the Payments tab.
      
   2. Attribute 76 – Vend Flow Options – on the Machines page – under VPOS Touch.
      Sets the vend flow to include the dynamic eReceipt.
      
   3. Attribute 1220 – Receipt Button Display Duration – on the Machines page – under Print Receipt Format.
      Sets the time the ‘Press for Receipt’ button is displayed at the end of the authorization stage.
      The range is between 0 to 60. Choosing 0 will disable the button and automatically display the receipt’s QR code.
   4. Attribute 1221 – Receipt QR Display Duration – on the Machines page – under Print Receipt Format.
      This attribute is used to set the time the QR code is displayed at the end of the authorization stage.
      The range is between 0 to 60. Choosing 0 will prevent the display of the QR code. Other values will set the duration of the QR code display.
      

| Age Verification – Machines with Mixed Products

We implemented new LAN communication capabilities giving it functionality similar to that of cellular communication.
The new capability of Age Verification feature supports MDB machines that contain products with mixed age restrictions.
In these machines, each product has its own age restriction so it can be uniquely validated. For example, cigarettes restricted to 16 years, alcohol restricted to 18 years, and a bottle of water with no age restriction will be validated and approved for dispensing separately.

Important note:  This feature is currently available in Austria only, where a full integration was done.

Improvements

| New Firmware Download Message

We have improved the message displayed on the device’s screen when a new firmware version is downloaded, making the message clearer and minimizing confusion.

The previous message was: “gloader 80%”
The new message is:
“Downloading Firmware 80%
Do not shut down!”

| Age Verification – Added a Voice Message to Present Age Verification Card

We’ve also added a new voice message for the Age Verification feature: “Please Present Card.” This feature serves as a clear prompt to notify the consumer that they must present an age verification card. This enhancement not only improves the age verification process but also enhances accessibility for consumers. This improvement is currently available in English and German.

| MONET+ Cards Support

We have added support for MONET+ cards in the Czech Republic.

Bug Fixes

• Fixed an issue in which the POS version could not be fully downloaded if there was a cellular communication loss.
• Fixed an issue in which POS version updates were delayed for a few minutes when done with a LAN connection.
• Fixed an issue in which the device would get temporarily stuck with the message “Please Remove Card” after a card was presented and the X button was selected.
• Fixed an issue in which the device would get stuck during a version update if there was a communication fault. Now, when the communication is reestablished, the download process will resume.
• Fixed a cash report issue that occurred with Pulse machines in which the product information sent for settlement was incorrect. The cash report will now display the correct product information.
• Fixed a Remote Start issue (for example, when Monyx Wallet was used) in pre-selection mode where the product ID was sometimes missing or incorrect during settlement process.
• Fixed an issue in deferred online mode in which the device would show an idle screen rather than an error screen.
• Fixed an issue with the Multi-Pulse mechanism in which pulse lines 1 and 2 had to be configured even when not in use. It is now possible to use pulse lines 3, 4, 5, or 6 without configuring pulse lines 1 or 2.
• Fixed the cut text on the revalue screen in Romanian and Italian.

Known Issues

• On the Revalue screen, text in the following languages is cut at the top and bottom: Latvian, Russian and Hungarian.
• “Try Another Card” error message has a wrong translation for Dutch.
• Remote start functionality doesn’t work with VPN communication mode.

Version 4.0.23.9

New Features

| MDB – Age Verification

The age verification feature gives VPOST/ONYX the ability to verify the card holder’s age during the transaction stage, allowing for the purchase of age restricted products such as alcoholic beverages, cigarettes, etc.

This feature follows the MDB protocol (age verification device) and only works with supported machines.

For a full age verification solution, an integration with a state or other authority that has the relevant database to approve/decline appropriate age must take place.

To activate this feature in Nayax Core, you must configure attribute 621 – MDB flags – on the Machines page – under MDB:

Important notes:  This feature is currently available in Austria only, where a full integration was done.

Improvements

| Marshall – Supported Deferred Online Mode

As we continue to improve the Deferred Online feature that was first introduced in version 4.0.12.23 in December 2022, we are pleased to announce that it is now supported by the Marshall protocol for EMV contactless payments.

This means that Marshall machines that operate in areas of unstable cellular communication such as parking lots are now able to complete transactions with Deferred Online and continue their service even if they are temporarily offline.

Important note: The Deferred Online solution comes with the inherent risk that transactions may not be approved, even though the product has already been dispensed (or the service given). Therefore, to enable this feature, a legally binding agreement must be signed with Nayax.
Instructions for use are available upon request.

Bug Fixes

• Fixed an issue with the Reload Configuration process in which a large number of parameters needed to be updated. Now, the reload configuration process works well in any number of parameters.
• Fixed an issue with the Remote Start feature for single pulse configuration that was found in version 4.0.23.5. Now, the product price is displayed correctly.
• Fixed an issue with Maestro credit card payments in which 4 red lights and a “try another card” message was displayed. These cards can now be used correctly.
• Reintroduced anti vandalism feature that is supported by old VPOST HW and is based on a specific accelerometer chip. The default status is now disabled (No Alerts) and can be enabled by selecting an alert type by configuring attribute 57 – Accelerometer alerts bit map – on the Machine page under Device Features.

Known Issues

• On the Revalue screen, text in the following languages is cut at the top and bottom: Romanian, Italian, Latvian, Russian and Hungarian.

Version 4.0.23.8

New Features

| MDB – New price configuration for sales reports

DEX is often used to audit sales of products, cash and cashless transactions, and income. Some operators rely on the information in DEX to fully manage the accounting matters of their business.

When an MDB transaction takes place, the Nayax reader informs the vending machine of the charged price through the “Vend Approved” command, and this is then relayed to the counter in DEX. However, sometimes the operator adds a convenience fee, resulting in a difference between the “machine price” and the “actual price” charged.

Some machines add the “actual price” (which includes the convenience fee) to the counter of the “total cashless income”, while others override the “actual price” and add the “machine price” instead. It is completely machine based, so it can be difficult to know which machines/VMC/FW behave in which way, especially in a large fleet.

To overcome this challenge, Nayax has added the ability to send the common denominator of the “machine price” through the “Vend Approve” command, instead of the “actual price” charged. This creates uniformity in sales reports throughout the entire fleet of machines. Meanwhile, any convenience fee charged by the operator is noted in the Core platform.

To implement this ability, go to the Machines page, and under MDB select attribute 621 – MDB Flags.

Then select either:

16384 Use VMC price for “Vend Approve”; or

16386 Use VMC price for “Vend Approve” + Preselection

Improvements

| MDB – Manual selection of DEX protocol communication

EVA-DTS standard defines the file transfer (DEX) protocol between POS device and VMC.

Among many technical definitions the protocol defines the “blocks” of transmitted message data and their maximum size.

Some machines expect each sentence in a message to be in its own “block”, whereas some machines require the entire message with all its sentences to be in the same “block”.

The behavior of the machines can be unexpected with regards to the above ways of transmission. For example, some machines will not accept Remote Price Change if the message is sent sentence by sentence.

To support this difference in machine behavior, we have added a new parameter to toggle the transmission method between Nayax device and VMC.

To implement this flow, go to the Machines page, and under DEX/DDCMP select attribute 689 – DEX/DDCMP Readout Options.
Then select one of the options that include – Enable large data blocks.

Bug Fixes

• Fixed an issue found in the previous version (4.0.23.6) causing the device to be non-responsive when pressing the “X” button after running the “Init DEX Passcode” process from the technician menu.
• Fixed an issue found in the previous version (4.0.23.6) causing DEX counter to reset all prices on M4000 machines. This fix is explained in the additional improvement above.
• Fixed an RPC (Remote Price Change) issue found in the previous version (4.0.23.6) on Vendo Machines that caused a blank screen on the machine.
• Fixed an issue of glitches occur once on each power cycle of the Nayax animation.

Known Issues

• On the Revalue screen, text in the following languages is cut at the top and bottom: Romanian, Italian, Latvian, Russian and Hungarian.

Version 4.0.23.6

New Features

| RPC – New Features for Remote Price Change

The Remote Price Change (RPC) feature enables efficient and reliable remote updating of machine prices. Saving you precious technicians’ time and effort, while ensuring that your fleet of machines is set with the correct prices.

We have developed this feature further, so that it now supports additional machines and features, including:
1. Machines that require a passcode to manage price updates and DEX reading such as some models of Dixie Narco, Vendo and Royal.
2. Machines with a large number of bins (approximately- up to 60).
3. Additional feedback of the RPC status and success to improve user experience and confidence.

An autonomous mechanism implemented in the device now recognizes the need of the machine for a passcode and enables a successful RPC process. This passcode is self-managed by the device and does not require any management. From this version on, you are able to carry out the RPC process for any machine model, (Given that the machine’s board supports the RPC feature).

For machines that require a passcode, or if it is unknown, all that is needed to enable this feature is to simply connect a DEX connector (part of the MDB cable) to the machine’s board, and run an initialization process in one of the following two ways:

1. Nayax Core: use attribute 1422 – Init DEX Passcode – on the Machines page, under DEX/DDCMP.
   
   Mark both check boxes as shown below, and press SAVE button at the top of the page.
   In the new version of Nayax Core, attribute 1422 – Init DEX Passcode – can be found on the Machines page under Settings > Parameters:
   
2. Device Technician Mode: press the Init DEX Passcode button in the device menu.
   
   Then, run a remote price update from the Products Map screen on the Machines page:

| Deferred Online – fallback from online mode

The Deferred Online feature enables your customers to carry out vending machine transactions even in areas where communication is unstable, for example where the machine is in a mobile location, such as on a train.Since this feature was first announced in the December 2022 Release Notes, we have continued to make improvements and are pleased to announce additional functionality.As an alternative to the Always Deferred Online mode, there is now a new Deferred Online Fallback mode. This mode enables an immediate, automatic fallback to Deferred Online when the device experiences a communication outage or instability.This new mode optimizes the use of the deferred online feature, to allow device to perform online transactions and perform the “riskier” transactions only when needed.

Important note: This feature is supported only on MDB machines and for contactless EMV payment solutions. The Deferred Online solution comes with the inherent risk that transactions may not be approved, even though the product has already been dispensed. Therefore, to enable this feature, a legally-binding agreement must be signed with Nayax.
Instructions for use are available upon request.

Improvements

| Improved cash report for Dixie Narco machines

Following complaints of false reporting of cash values (such as the number 655.21), we have found that the issue arises with some Dixie Narco (DNC) machines.

This behavior is mostly observed when VPOST/ONYX is set to preselection mode. The machine reports a cash report command after each cashless transaction, causing a false cash report to appear as a cash transaction in the last sales report section on Nayax Core. In this new, updated version, such reports are not sent to the servers, so you will see only accurate transaction reports in Nayax Core, without the false cash reports.

Customers who reverted to pre-authorization mode to avoid this issue can now switch back to the more desirable preselection flow.

| CONECS cards supported by Marshall protocol and SDK

Marshall protocol now explicitly recognizes the CONECS cards, allowing Marshall VMC’s to act on this information if desired.

Bug Fixes

• Fixed an issue caused by upgrading to FW version 4.0.23.4 or to 4.0.23.5, resulting in read failures of some credit cards.
• Fixed an issue found in the previous version (4.0.23.5) whereby, in Deferred Online mode in areas with poor communication, it was not possible to make any other transactions after a credit card had been declined.
• Fixed a GUI issue found in the previous version (4.0.23.5) whereby, in Deferred Online mode in areas with poor communication, the device remained on the Decline screen for about a minute after a prepaid card had been declined.
• Fixed a GUI issue found in the previous version (4.0.23.5) whereby flickers appeared on the screen during contact or contactless transactions.
• Fixed a GUI issue related to Marshall Multisession whereby a final price screen was displayed following an unwanted of Charging was successful
• Fixed a GUI issue found in the previous version (4.0.23.5) in which a black screen would appear when the device was in idle mode.

Known Issues

• In Australia, an issue was observed in which the pending-vend mechanism (the failsafe process before a transaction is finalized) would fail due to especially long credit card data, causing the information to be corrupted and the later settlement to fail.
• Glitches occur once on each power cycle in the Nayax animation.
• On the Revalue screen, text in the following languages is cut at the top and bottom: Romanian, Italian, Latvian, Russian and Hungarian.

Version 4.0.23.5

New Features

| Prevent expired credit cards from being used in deferred online mode

The deferred online capability enables your customers to carry out vending machine transactions even in areas where communication is unstable, for example in cases where the machine is in a mobile location, such as on a train.
While legitimate transactions are approved once connectivity is resumed, this new feature ensures that payment attempts using an expired EMV credit card are immediately denied, before the product is dispensed from the machine.

Note: This feature is currently supported only on MDB machines and will be enabled after the signing of a legally-binding agreement with Nayax.

Improvements

| New graphics enhance customer experience

In the idle screen, we have replaced the ApplePay and Monyx logos to reflect the new look of these payment solutions. We have also changed the Nayax animation displayed as the device powers up.
Note: This change is applicable to devices produced with this and future versions. (Images are not updated as part of the FW OTA update process).

Bug Fixes

• Fixed a known issue found on the previous version (4.0.23.4) – on pulse machines, when the clock symbol is in use, it doesn’t duplicate itself on the Present Card screen.
• Fixed a known issue found on the previous version (4.0.23.4) – the technician card now opens the Technician Menu.
• Fixed a GUI issue with the eReceipt button – text displayed in French no longer overflows beyond the button size.
• Fixed an issue in which some credit cards were recognized as MiFare.

Known Issues

• An issue observed in Australia, in which the pending-vend mechanism (the failsafe
  process before a transaction is finalized) would fail due to especially long credit card
  data, causing the information to be corrupted and the later settlement to fail.
• Glitches occur once on each power cycle in the Nayax animation.
• On the Revalue screen, the text in the following languages is cut at the top and bottom:
  Romanian, Italian, Latvian, Russian and Hungarian.

Version 4.0.23.4

New Features

| The New Pulse “Count-Up” Mode, “Pay-As-You-Go”, Gives You Full Control Over Your Machines

Pulse count-up is a Pay-As-You-Go purchase flow in which the consumer presents a card and uses the machine for as long as they want. The charge is accumulated as time passes and stops when the cap is reached, or when the consumer uses the cancel button to stop using the machine.

The existing solution required that the VPOST/ONYX be connected to the machine at a different point than the coin mechanism – directly before a motor, which caused some logistical issues. We have therefore improved the count-up feature to allow for a “Pay-as-you- go” experience with regular pulse-connectivity logic, allowing for the connection to be made in parallel to the coin mechanism. The Count-Up Pay-As-You-Go feature is enabled by the sending of a pulse burst at a constant rate, just before the machine stops, to keep it going.

This new feature allows to connect the Nayax device with a straightforward pulse connectivity. It also helps improve the user experience and product reliability, allowing your customers to stop at any time and to pay for the exact time that they used the machine.

Note: This feature is applicable for preauthorization flows only because the final price isn’t known when the transaction is initiated.

The below diagram shows the Nayax devices’ connectivity points for each of the Count-Up modes:

The previous “count-up as a relay” behavior:

The new “count-up as pulse” behavior functionality:

Edit Your Pulse Options on Nayax Core:

Operations > Machines > click on a specific machine > click on “Pulse/ ccTalk” category > Attribute 722 – “Pulse Options” > choose “Count Up – Pulse”:

Count-Up “Pay-As-You-Go” Transaction Flow Example:

In this example the machine’s activation cost is 0.75 and each 10 second pulse is worth 0.25. During the first 30 seconds, the price is fixed at 0.75, but starting at the 31^st second, the price will increase by 0.25 for every 10 seconds until the total price of 7.50 (equivalent to 5 minutes) is reached, or until the customer stops using the machine by pressing on the cancel button.

This is what the backend looks like for this example on Nayax Core:

Improvements

| Improved “Discount” Functionality When a Discount Card is Used

We’ve improved the discount price support for MDB and Pulse multi-price machines so that you can manage it more quickly and easily.

For MDB machines, there are two scenarios:

• If a product map is configured: the “Basket” icon will only display the total price.
  Note: Previously, a wrong calculation of the total price was displayed.

• If a product map is not configured: The original price, the discount, and the total price will be displayed.

For Pulse multi-price, we’ve improved the discount card reading for cases in which the transaction began with a press of the button.
The discount card will be recognized correctly, and a transaction can now be initiated when a discount card is read.

For your reference: discount cards for the above improvement are configured in 2 steps:

• On Nayax Core, go to Consumers tab -> cards page and define a discount card for your operator.
• On Machine page -> General tab ->Payment, define the “Payment Flags” (attribute 588) with value: “Server Discount for Cashless”

Bug Fixes

• Fixed a known issue from the previous version (4.0.23.3) – Screen is stuck and buzzer
  is permanently on after many card presentations.
• On JVMA machines, we fixed a POS reset issue accompanied by a long beep when an EMV or prepaid card is presented.
• Fixed a known issue found on the previous version (only 4.0.23.3) – When swiping a card with the magnetic stripe reader (MSR), an error message “Please tap again” was displayed for a moment.
• Fixed an issue in multi-vend with prepaid cards where transactions occasionally failed.
• Fixed a known issue found on the previous version (4.0.23.3) – When the available device menu entries were customized, the “technician mode” button wouldn’t work in the following cases: menu items include “technician mode” and 1 to 5 other entries.

Known Issues

•  GUI – On Pulse machines, when the clock symbol is in use, it duplicates itself on the
  “Present Card” screen.
•  The technician card doesn’t open the Technician Menu.

Version 4.0.23.3

New Features

| We now support the new Inepro RFID Reader too

For those using the Inepro reader, we have added support for Inepro’s new external Spider RFID reader – 200017-N (Nayax’ ItemCode R270002). The external Spider can now be connected to the VPOST/Onyx

| A prepaid QR Code Prefix Configuration to accept also alphanumeric QR/bar codes from external readers has been added.

The “disabled Auto Prefix for QR Prepaid” feature has been modified to support more modes and is renamed as “Configure Auto Prefix for QR Prepaid”.
Up until now, the prefix “NYXPP;” was added automatically to QR codes and Barcodes only to numeric codes. There is also an option to disable this automatic addition.
Now, in order for you to be able to read QR codes and Barcodes more flexibly from external readers, we’ve extended this ability to alphanumeric codes as well. Four options are now available as shown in the picture below.

Attribute 159 – “Disable Auto Prefix for QR Prepaid” on the machine page under “Device Features” category was previously shown as:

Attribute 159 – The attribute has a new name: “Configure Auto Prefix for QR Prepaid “on the machine page under the “Device Features” category:

Improvements

| Improved GUI Animations

We have improved the distortion that appeared occasionally in the animations of the Idle and transaction steps.

| Quicker Contactless Reading Time and Card Classification

Our card classification algorithm has been improved.
As a direct result, the contactless reading time for credit cards has been decreased and rare incorrect classification of Credit Cards as Prepaid or MiFare will be avoided.

| Improvement to MDB Protocol – Cancel Transaction in Case the “Vend success” Message is Not Received

Change the protocol to fit your needs – you can now add transaction cancellation in case a product didn’t dispense.
To understand this feature, let’s look at the flow:

1. Vend Request – Machine requests to charge the
2. Vend Approved – The payment reader approves the
3. Vend Success – The machine dispenses the
4. Transaction – The reader finalizes the transaction with the

Now, there is an option to change this logic and have the device cancel the transaction in case it does not receive the “vend success” message.
To do so, open Nayax Core (formerly the DCS) and Go to the “Machines” tab – “MDB flags” (Attribute 621) under the MDB category and choose the correct option.

Bug Fixes

• Fixed an issue where, on rare occasions, the Onyx device got stuck when entering a POS download fallback mechanism.
• eReceipt – Fixed a GUI issue in which the “press for receipt” text overlapped on the button icon in the following languages: Estonian, Latvian, and Lithuanian.
• Fixed a message display issue in the new “pre-paid weekly limitation” feature in the following languages: Italian, Croatian, Romanian, and Portuguese.
• Fixed issue found in version 4.0.23.2 in which the wrong price was charged when Monyx was used with Pulse machines (the first product price would be charged instead of the selected product price).

Known Issues

• Important Update: For all machine types configured with Japanese or Chinese languages, when using EMV Contact, contactless, or using Prepaid cards, the device is stuck in the authorization screen with a long beep noise until it resets itself.
• On Revalue screen, the bottom and top of the text are cut in the following languages: Romanian, Italian, Latvian, Russian, and Hungarian.

Version 4.0.23.2

New Features

| Pulse Fiscalization – Fiscal Monitoring on Pulse Machines

Fiscal monitoring is now possible on pulse machines with the use of a supporting external Fiscal device.
We differentiate between two types of payment methods:

• Fiscalized payments: Credit Card/Apple Pay/Google Pay and other payment apps
• Non-fiscalized payments: Prepaid/Monyx/QR

Using Nayax Core platform we offer a selection of 2 modes of operation:

1. Mode 1 – Fiscalized payment methods use pulse line 1, while non-fiscalized methods use pulse line 2.
   
   An example use case for this method:
2. Mode 2 – Fiscalized payment methods use pulse lines 1 and 2, while non-fiscalized methods use only pulse line 1.
   
   An example use case for this method:Attribute 601 – “Pulse Fiscal” under the Pulse/ccTalk category.

| Improvement to Marshall Protocol – Cancel Transaction in Case “Vend success” Message is Not ReceivedThe basic transaction flow between a machine and the payment reader is:

1. Machine requests to charge the customer (“vend request”).
2. The payment reader approves the request by sending a “vend approved”
3. The machine dispenses the product and sends a “vend success” message to the
4. The reader finalizes the transaction with the

Traditionally, if for some reason the machine does not send the “vend success”, the reader would still finalize the transaction.
Now, there is an option to change this logic and have the device cancel the transaction in case it does not receive the “vend success” message.

* On multisession flows – this is always the default behavior.

Attribute 621 – “MDB flags” under the MDB category

| Added Message Indication for the New “Weekly Limit” Pre-Paid Feature

Pre-paid cards have a new “Weekly Limit” feature, and the following message is displayed in case the transaction is declined – “Card Exceeded Weekly Limit”.

| Improved User Experience by Directing the Consumer to Tap Their Card When Contact Interface is Disabled

Once the Contact interface is disabled, a new message – “Tap Card” will be displayed immediately on the VPOST screen when a payment card is inserted to the contact slot.

Previously it displayed “please remove card” after approximately 10 seconds. It did not clearly indicate that the contact interface is disabled and that contactless should be used.

Example configuration for disabling the contact entry mode in Nayax Core:

Improvements

| Improved MQTT Stability

Based on new observations about several cellular providers, we reduced ping time intervals for MQTT to improve robustness and decrease disconnections.

Bug Fixes

• Fixed Polish audio message for “Please select a product”.
• Fixed Pulse line cash report with wrong product ID – now sends the correct product ID.

Known Issues

• For the new Weekly Limitation feature, the message is displayed out of screen bounds in the
  following languages: Italian, Croatian, Romanian, and Portuguese.

1. Version 4.0.23.1

2. Improvements

   | Deferred Online – Faster Vending, Now with More Payment Options

   Added support of NFC transactions using smartphones in addition to EMV contactless. Payments with Google Pay (Google Wallet), Apple Pay and other smartphone applications will now follow the Deferred Online scenario when activated.

   | Marshall – Display Final Price in Case of Campaign (for preauthorization flows)

3. For all types of campaigns such as discounts, the final price will be transferred to Marshall VMC that can be displayed to the user.
   Added support for preauthorization flows (pure preauthorization integrations or preauthorization due to Nayax backend implementation). The final price value is transferred in a new “Transfer Data” command before the “End Session” command.Marshall SDK version update would also be required.
   For more information, please contact support.

4. Bug Fixes

   • Fixed occasional “lock” scenarios in which the device is required to be restarted after using the “reload configuration” command.