Home

Introduction

  • Target Audience

    • Goals

      • Payment method Digital Wallet

        • Field Codes

          • Menu Codes

            • Discount Value Treatment

              • Rounding in the Calculation of the Discount Granted

                • Digital Wallet ID Table

                  • New Command Codes

                    • Transactional flow

                    • Histórico de Alterações

                      Aborting the transaction with QRCode if the customer or cashier gives up on the current transaction.

                      2.1 Reasons why a transaction with the Merchant's QRCode may take time to complete processed

                      The transaction with the Establishment's QRCode is a transaction that depends on some factors to happen:

                      • Customer cell phone signal
                      • Customer agility to open the Digital Wallet App in question and read the QRCode
                      • POS screen resolution (if the POS displays the QRCode on the screen) / QRCode printing quality (if the QRCode is fixed on a plate next to the POS) / pinpad screen resolution (if the Pinpad has the capability to display the QRCode and CliSiTef treats the protocol with the pinpad to be able to display it)
                      • The POS screen may face the operator and thus make it difficult to read by the customer's App (in this case QRCode display on the POS screen). As a result, the transaction may take time to occur or the customer may give up on carrying out the transaction due to whatever the reasons. If there is no operator intervention in this case, there will be need to wait for the transaction to time out, which can take from 30 seconds to 1 minute (or more).

                      2.2 Procedure that the POS must implement in case of withdrawal of the transaction with the Merchant's QRCode

                      In cases where the transaction is abandoned, the procedure that the POS must perform is to send the value -1 in the function “ContinuaFuncaoSiTefInterativo” in the parameter “Continua”. As a result, the transaction will be interrupted (the CliSiTef will return the -2 return for this function indicating that the transaction was canceled by the operator) and the undoing it will be sent in the next transaction (processing carried out internally by CliSiTef), to ensure that the customer will not be charged for the transaction under any circumstances.

                      2.3 Points to the POS to display an Abort/Cancel button on the screen while the transaction is taking place with Establishment QRCode with SiTef is in progress

                      • If the POS processes the QRCode string to display it on the POS screen

                      If the POS is treating the QRCode string with its display on the screen, CliSiTef will return the command 52 to optionally display a message on the screen, along with the QRCode. While this command is being returned, the Abort/Cancel button may remain on the screen so the operator can abort the transaction.

                      • If the POS has a plate with QRCode printed next to the POS

                      If this is not the case, that is, if it is a transaction with QRCode but the POS does not handle the return of the string QRCode (there is a QRCode printed next to the POS), the moment the automation could display a button to Canceling/Aborting the transaction would be when CliSiTef returns the value 0 in the Command parameter (it is returning a value to, if desired, be stored by the automation) and in the FieldType parameter the value 0 (the routine is being called to indicate that it has just collected the transaction data and will start interacting with SiTef to obtain authorization) - both parameters are from the “ContinuaFuncaoSiTefInterativo” function.

                      2.4 Indication to the POS to remove an Abort/Cancel button on the screen The time to remove the Abort/Cancel button screen would be when the function ContinuaFuncaoSiTefInterativo returns a value other than 10000, indicating the end of the transaction with CliSiTef.