Deferred Payment

The Deferred transaction flow processes a payment request in two distinct phases:

This two-step approach is particularly useful for transactions where the final amount or details may change after the initial card interaction.

Transaction Flow

To understand the Deferred transaction flow, consider the following sequence of events:

Steps inside the green area are performed online, and the ones inside the red area are performed offline.

Here’s a breakdown of each step:

After the client application (POS) performs its doPeriodic() to settle the stored card transactions.
setConfig() will switch the device to work in deferred mode, using offline mode.
The POS sends a doTransaction() request to the Nayax Device, triggering a new transaction.
The CardHolder taps their contactless card.
The Nayax Device checks for “Deferred pre-conditions” and, upon approval, returns the transaction result as Approved->Pending. This means the transaction is approved.
Once the deferred mode is finished working, continue to step 6.
The client application calls setConfig() setting off-line mode to false.
The client application calls the authorizePendingTransactions(), sending the pending transactions to Nayax’s device asking to settling them (but no settlement is performed yet).
The Nayax Device communicates with SHVA to initiate the pending transaction authorization.
The transaction results are returned to the Device.
The transaction results are returned to the client application.
The flow concludes with a final doPeriodic() call from the client application, to settle all authorized transactions.