Reader always on
This configuration is relevant for peripherals that want to start the transaction with product selection (PreSelection flow) but don’t have a way to start a transaction from the peripheral. It means the transaction process is initiated from a consumer selecting a product on Nayax’s device screen, which then triggers the peripheral to send the product’s details. In rare cases, a consumer’s card presentation can trigger the peripheral to send the product selection, but this option isn’t common.Always idle
The transaction starts with the consumer selecting a product (PreSelection flow) on the peripheral, which then sendsVend Request without waiting for a Begin Session trigger. This flow is very commonly used in the Far East.
Transfer data
Transfer Data provides information during the transaction process about the transaction details: Nayax’s transaction ID and the consumer’s card details. For credit cards, this means the BIN, the PAN hash, and the last four digits. For proprietary cards, it means the UID (the card’s full number). The card details are sent automatically once a consumer presents their card and the authorization result arrives. Transfer Data also lets the peripheral send its own transaction ID, so it appears in the SDK’s logs. Nayax doesn’t use that information for anything else. For more detail, see Transfer Data.Display control
Display Control is a feature for peripherals that need the Marshall master to define different selection screens on the device before sending a request for a specific price. This way, product selection comes from Nayax’s device instead of the peripheral. It helps when the peripheral has no screen, or no way for consumers to select a product on its own end. For more detail, see Display Control.eReceipt
eReceipt generates a digital receipt file on the device once the transaction settles, and sends the file’s link to the peripheral via the SDK using a QR code. To enable it, set the following configurations in Nayax Core:- Payment tab > Transaction Options > Enable eReceipt on Transaction End: enabled
- Receipt Button Display Duration: 20
- Receipt QR Display Duration: 40
- Vend Flow Options: Dynamic Receipt
C
Fixing an unrecognized eReceipt product name
Product names come from your product map. You can create products in it and name them to match the product codes you send via the SDK. Marshall doesn’t use any other information in the product map, so it doesn’t affect the transaction flow, including prices. The only field that matters is the product code name, which appears in Last Sales and the eReceipt file. To add new products to your device’s product map, go to the Product Map tab and click Map > Add BIN. Add the product code, product group, PA code, and MDB code (the MDB code must match the product code in the SDK), then click Save.Info session
Info Session is an informative, non-vending session that provides the peripheral with the consumer’s card details when they present their card. The consumer isn’t charged, and receives aCard Read Successfully notification. The transaction ends with Vend Denied, since there’s no authorization and no need to proceed to vending.
Info Session is used chiefly for consumer re-identification, by having the consumer present the same card they used to start the transaction. It’s most relevant for rentals and EV chargers.
Important note: This feature requires the peripheral to have a screen, or another way to distinguish between a vending session and an info session, since the peripheral decides which type of session to start.
Incremental authorization
Incremental authorizations increase the total amount authorized when the estimated or initial authorization isn’t enough. An incremental authorization request can also be based on a revised estimate of the cardholder’s spending. Incremental authorizations don’t replace the original approval: they’re additional to previously authorized amounts. The sum of all linked estimated and incremental authorizations is the total amount permitted for a given transaction.How incremental authorization works
The incremental feature uses two Default Credit parameters: the regular one, and Maximum Default Credit. The consumer is initially authorized for the regular Default Credit amount, as in any PreAuthorization transaction. If there isn’t enough credit for the Default Credit amount, the transaction is cancelled at this step. If the consumer takes items worth less than the Default Credit amount, they’re only charged for those items, as usual. Example: With a Default Credit of 50.00: If the consumer takes items worth more than the Default Credit amount but less than the Maximum Default Credit amount (for example, 7.00):- If the second authorization is approved, the consumer is charged the full amount ($17.00). Last Sales shows this as one line record, with a settlement amount higher than the authorization amount:
- If the second authorization fails, the consumer is only charged the first authorization amount, the Default Credit ($10.00). In this case, the loss from the failed second authorization is the machine operator’s risk.