How the flow works with the Establishment’s QR Code
Customer chooses to pay with a specific Digital Wallet
(Digital Wallet 1 – see Figure 1)
After CliSiTef requests the necessary information, such as value, payment method and number of installments, among others, the transaction continues for processing at the Digital Wallet authorizer in question. In the meantime, CliSiTef returns a string of the Merchant's QRCode to be displayed by the commercial automation
(only if the QRCode is of the dynamic type and if CliSiTef did not display it on the PIN pad)
.In this case, CliSiTef returns the command 50
(see item 11)
with the QRCode string; it must be converted into QRCode(image)
and displayed on the POS screen.Note 1: CliSiTef does not have a screen to display the QRCode, therefore commercial automation is the one who must make this display
(from the string provided by CliSiTef)
if it is of interest to the Commercial Establishment and there is no compatible pinpad for its display .Note 2: the display of the QRCode on the screen by the POS must not block the processing of the transaction, that is, the process must be continued by the ContinuaFuncaoSiTefInterativo function
(command 50 is not blocking)
, allowing the transaction on CliSiTef to proceed until its completion, that is, until it returns a value other than 10000.Note 3: if the POS does not yet have any QRCode processing treatment (most commercial automation already handles QRCode for printing Electronic Invoice/SAT/MFE), we suggest using the libqrencode library (https://fukuchi .org/works/qrencode)` to transform the string into QRCode itself together (http://www.libpng.org/pub/png/libpng.html) for image generation. with libpng
The customer opens the application on their cell phone and scans the QRCode displayed on the POS
(or on the pinpad, if it has display capacity; or on the plate with the printed QRCode)
and submits the transaction to the authorizer.The authorizer makes a “match” between the transaction that arrived from SiTef and the transaction sent by the client's App, processes them, and returns the response to both the client's application and SiTef.
CliSiTef returns the command to remove the QRCode from the POS screen
(command 51)
, if it was treated as having been previously displayed(command 50)
.
Note: If the POS has space available to display a footer message while the QRCode is displayed on the screen, it can process command 52, displaying the dynamic message (identified by TypeField 4128)
so that the operator can know that the POS is not locked. The display of this message is optional, and it is up to the commercial automation to display it or not. If the POS wants, it can make its own adjustments, placing an hourglass or other dynamic message, just to let the operator know that the terminal is operational and has not crashed.