Get the latest payment updates and learn about new integrations and features in your region.

Deferred Online

We are introducing a new feature, enabling operators to accept payments even when connectivity is limited or unstable (e.g. on trains and buses), and facilitating faster checkout in high-traffic environments (e.g. parking and public restrooms). Deferred Online has two modes, Always Deferred Mode and Deferred as Backup Mode.


| Always Deferred Mode

Nayax enables operators to offer faster checkout and avoid long queues, by allowing up to 60 taps per minute in heavy traffic environments, such as parking exits or public restroomsA device that is set to Always Deferred will defer a pre-defined number of transactions, or send transactions after 10 minutes in idle mode. For example, where an operator sets the transaction count for a given machine to 50, cardholders paying at the device will receive immediate approval (unless the card is expired, or its number is not compliant), and transactions will be sent for authorization and settlement once the device has been in idle mode for 10 minutes, or after the 50th transaction, whichever happens first. This way, 50 checkouts can go through, with a shorter waiting time. The risk for declines can be managed by adjusting the maximum transaction count to the most suitable level. 


| Deferred as Backup Mode

Nayax enables operators to accept payments in areas with unstable connectivity. Installations on trains, light rails or buses going through areas with limited cellular connectivity, can be configured with the deferred mode as backup. Where an online authorization is not possible, the device enters Deferred Online mode. The cardholder paying at the device receives immediate approval (unless the card is expired, or its number is not compliant), the transaction is then deferred and will be sent to the relevant server once the device reconnects. The device will remain in Always Deferred Online mode for the time defined (in minutes) by the operator in Nayax Core, or until a pre-defined maximum number of transactions is reached. The risk of declines can be managed by changing the maximum duration for which the machine may be in this mode, or adjusting the maximum transaction count to the most suitable level. 


| Prerequisites

Deferred Online can be configured for single-vend MDB and Marshall machines, in pre-selection or pre-authorization mode. It applies to EMV Contactless/NFC Card transactions only. Extra Charges or Discounts may not be processed while the machine is in Deferred Online mode. 

The feature can be activated upon request to Nayax Support and will be enabled after signing an addendum to the Nayax agreement.  

Version support:
VPOS Touch:


| Configuration

  1. Prerequisites
    1. A legally-binding agreement covering Deferred Online mode must be signed with Nayax before activation. 
    2. Relevant permissions must be granted by the Nayax support team.
    3. The operator must configure the relevant machines.
  2. In the Payment Tab of the Machines page, click Add Payment Method and select Deferred Authorization from the drop-down menu. On the Extra Charge field, enter 0. Then click Save.
  3. Under the Deferred Authorization Definition, choose one of the Deferred Authorization modes, and click Save.Deferred Authorization modes:
    • Always Deferred: Activates Deferred Authorization for every EMV Contactless/NFC transaction.
    • Deferred as Backup: Activates Deferred Authorization in the event of online transaction fails due to unstable connectivity.
  4. In the General tab of the Machine Page, click Device Features and define the two attributes for Deferred Authorization:
    • Always Deferred Timeout defines how many minutes the device will stay in the deferred online mode after failing to complete the transaction online. This attribute is relevant only if Deferred as Backup is selected under Deferred Authorization Definition. When the value configured is 0, the device will always try an online transaction first. Recommended Value: 10
    • Max Allowed Transaction Count is the maximum number of transactions that can be deferred and held in the device at a given time. Recommended Value: 20

Extended Refund Period

Extended Refund Period

Enabled in Australia, Canada, Emirates, Israel, New Zealand, Turkey, USA 

Nayax has extended the purchase refund period to 180 days, meaning that payments can be refunded to the cardholder account for up to 180 days from the date of the original transaction. 

This new policy is enabled for billing providers that support Refund 2.0*. The number of days until the refund is made may vary, depending on local regulations and billing-provider policies.
Transaction refunds can be made by clicking on the arrow in the furthest-right column of the Dynamic Transaction Monitor (DTM). They are then displayed as a negative amount in a new line on the Dynamic Transaction Monitor.  

* The following billing providers support Refund 2.0:
Heartland Nayax EMV, Heartland Direct EMV, Chase Direct, Chase – Facilitator, Ashrait, Ashrait – Direct, Ashrait Retail Tandem, Bank of Tahiti, Network International, WorldPay, Coriunder Ecomm, ipayafrica, ProvisionPay
Note: The 180 days will run from the date on which Refund 2.0 was originally enabled.

Developer Zone Update

We are constantly improving our Cortina API documentation to simplify integration processes with our partners. We recently updated the Developer Zone to make integration processes more accessible to acquirers and payment brands.

| Decline Reason Codes

Decline Reason Codes vary according to integration type. Permitted Decline Reason Codes are now described separately for each integration type in the information section, showing only the codes relevant to that specific integration type.

| Enabling Discounts for Cortina External Prepaid

The Discount feature enables integrators to change the settlement value of an External Prepaid transaction by sending a new settlement value in the sale/settlement response (after authorization of a higher amount). Descriptions and instructions for use of the new Discount features can be found in the Cortina API documentation.

| Cortina Static QR documentation

We have updated the Notify Request command name (formerly “Notify”, now “Start”) to improve consistency across the documentation. This also includes further clarification of the TerminalId and UniQR fields. This change does not affect any existing implementations.

Any feedback? Please use the new feedback form in the Developer Zone.

Enhanced Prepaid Reporting

We are pleased to inform that we have enhanced the ability to view transaction status information regarding prepaid transactions on Nayax Core and MoMa.

As of the end of May 2024, operators will have direct visibility into declined prepaid transactions via all transaction reports, Last Sales and DTM. This includes prepaid transactions done via Nayax Prepaid Cards, key fobs, NFC stickers, QR Codes, and Monyx Prepaid.

The decline reason “Declined during Authorization” may appear for the following reasons:

  • Card Exceeded Daily, Weekly, or Monthly Limits
  • Card Exceeded Group Limit
  • Card Exceeded Machine Location Limit
  • Card has Insufficient Credit
  • Prepaid Card Authorization Failed
  • Card Blocked

The Decline reasons can be seen in the Last Alerts report by searching for the transaction ID.

Note: Prepaid transactions that are not completed as a result of not reaching Nayax Servers (e.g. due to connectivity), and transactions of cards, that have never processed any successful transaction, will not be displayed in reports.

action / 9 - action, cancel, close, delete, exit, remove, x icon
action / 9 - action, cancel, close, delete, exit, remove, x icon