Skip to main content
Closed-loop transactions use MIFARE cards. The merchant reads the card UID and processes the transaction on their own application server, without involving bank networks. Since no bank operations are required, closed-loop transactions do not use the Nayax servers. Instead, your host machine uses the EMV reader to read the card and EMV Core to interact with it.
Your application does not know whether the user will present an open-loop (credit or debit) or closed-loop (MIFARE) card until the reader scans it. Your application must be prepared to handle both.

​
Transaction Flow

The following diagram shows the transaction flow for a closed-loop transaction:
Where:
  1. The host machine calls the PreAuthorize method using the EMV Core API. This is the only action performed by the host machine.
  2. The EMV Core sends the amount to the Reader.
  3. Your application prompts the user to tap their card.
  4. The shopper taps the card into the EMV reader.
  5. The Nayax EMV Reader pulls the Response with the encrypted card data to the Nayax EMV Core.
  6. Nayax EMV Core identifies it as a MIFARE card (closed-loop transaction) and informs the host application that the transaction is complete, returning the card UID and optional card data.
By default, MIFARE card data is shared locally with your host machine. You can also configure the SDK to send the data to Nayax servers for processing through Nayax Prepaid.
  1. Your application uses the card UID to authorize the transaction with your application server.
  2. Once approved, the transaction is complete.
  3. The product is successfully delivered to the buyer.
  4. EMV Core allows transactions to be reported to the Nayax server, which sends the proprietary payment amount and UUID.