Form of identification in the digital wallet flow

Like every financial transaction, transactions with Digital Wallets require a form of client ID. Each “Digital Wallet” has different collections to carry out this identification, which may occur in more than one form, such as “CPF + Token” or “Telephone + Token”.

If identification is by QR Code, it may contain customer information, establishment, transaction and/or terminal data. (For more details regarding the flow with QR Code, see details in Transactional Flow With Payment via Merchant QRCode).

Normally this identification will be requested immediately after choosing the Digital Wallet, in the flow of a payment transaction, cancellation, or other operations that accept this form of payment.

The main collections for customer identification are:

  • Digitized Token: Identifier token generated by the customer's Digital Wallet application.
  • CPF
  • CNPJ
  • Telephone
  • User Identifier: User identifier code managed by the Wallet application
  • Digital
  • Agreement Code
  • Facial Biometrics
  • Barcode: Barcode generated by the customer's Digital Wallet application. In this case, the Bar Code must be read by the POS using a Bar code reader or even typed (command 35 collection)
  • Customer QR Code: QR Code is generated by the Customer's Digital Wallet application and must be read by Automation using a QR Code reader. In this case, reading the QR Code will be identified by field type 740 and will be requested by collecting command 29.
  • Establishment QR Code: This can be static or dynamic, and may or may not be displayed on the POS screen depending on the settings of each Digital Wallet.

  • Static QR Code: The establishment has the QR Code image available visually somewhere close to the Cashier/POS. It is usually a sticker or plate which is exposed so that the customer can read it through their Wallet application Digital. Customer identification is then done indirectly.
  • Dynamic QR Code: The QR Code is generated dynamically and or is returned for automation in field 584 (See more details in Transactional Flow With Payment via Merchant QRCode), in this case it is displayed during the transaction flow on the POS screen through Automation, or is displayed on the pinpad display if it is supported.