Skip to main content
The two-phases transaction flow for the SHVA payment service divides a single transaction into two distinct steps:
  • An initial information retrieval phase
  • A subsequent authorization phase
This flow is often used by clients who implement a loyalty mechanism, as it allows for user interaction between the two phases, such as canceling or changing transaction values.

​
Transaction flow

To understand the 2 Phases transaction flow, consider the following sequence of events:
Here’s a breakdown of each step:
  1. The client application (labeled as DC) initiates the first phase of the transaction by sending a doTransactionPhase1 request to the Nayax Device.
  2. The Nayax Device prompts the CardHolder to present their card by either inserting, showing, or swiping it.
  3. The Nayax Device responds to the DC with a doTransactionPhase1 response, which contains the card and transaction properties.
  4. After any necessary user interaction (e.g., changes or cancellations), the DC sends a doTransactionPhase2 request to the Nayax Device to complete the transaction.
  5. The Nayax Device sends an authorization request to the Payment Server.
  6. The payment server processes the request and sends an authorization response back to the Nayax Device, which then relays the Authorization response to the DC.
  7. At the end of the day, the DC sends a doPeriodic request to the Nayax Device, which communicates with the payment server to complete the day’s batch process. The Nayax Device then sends a doPeriodic response back to the DC.

​
See also

Regular transaction

Process and authorize a payment request in a single step.

Pre-authorization (Israel)

Process and authorize a transaction, then settle or cancel it based on the payment server’s response.

Deferred payment

Run a pre-authorization phase followed by a final authorization phase.

Split transaction

Split a transaction’s payment across multiple sub-merchants.