Retailer Operations

A retailer's POS system does not require them to accept partner notifications upon scanning the QR code. Retailers do not need to grant partners access to their internal systems to receive these notifications at the POS.

Operations and Messages

To enhance customer transactions, your POS system must implement the following key operations:

Creating a QR code:

• Request payload: createQrCode
• Response payload: CreateQrCodeResponse
• Error payload: ErrorDetail

Processing transactions:

• Request payload: PaymentRequest
• Response payload: PaymentResponse
• Error payload: ErrorDetail

Confirming payments:

• Request payload: confirmPayment
• Response payload: PaymentConfirmation
• Error payload: ErrorDetail

Reversing payments:

• Request payload: reversePayment
• Response payload: PaymentReversal
• Error payload: ErrorDetail

When you submit a payment request to Electrum, it associates the request with a scan notification from a payment provider. In the response message, the POS system informs which payment provider processed the payment. This allows the POS system to learn about the payment provider after processing the request.

Since your POS system does not need notifications for QR code scans, it won't receive the partnerPaymentTokenthat a payment provider sends in a scan notification. However, Electrum receives the notification and will include the necessary information in the payment request to the payment provider.

Where To Display the QR Code

The QR code can either be displayed on the POS or the PED. For QR code-initiated payments, the POS receives a Base64 string representation of the QR code. Similar to capturing numeric digits, eSocket.pos (application) requires a driver with instructions to enable retailer-specific QR behaviour.

• You will receive a Base64 string from a QR issuer (depending on the use case).
• The POS converts the Base64 string into a bitmap image.

If you want to display the QR on a PED, you can leverage the PED capabilities to display an image to customers to initiate a payment. After the POS converts the Base64 string into a bitmap image, it will:

• Display the transaction by sending an instruction to the PED to display the bitmap image.
• The customer can scan the image to initiate the payment.
• Once scanned/consumed, the POS has to instruct the PED to clear the image and reset to the default state.