With our Biometric Pix product, your users can approve payments without ever needing to leave your application. After enrolling their device, they will be able to make Pix payments using biometric authentication such as facial recognition or fingerprint.

Enrollment

For each device and bank account that your users want to use for Biometric Pix payments, they will need to go through an enrollment. An enrollment is essentially the process of registering the user's device and biometric data with their institution.

Payments

After your user has at least one enrollment, you can start making instant as well as scheduled or recurring Pix payments! Below you can see a sample implementation, where the entire process occurring entirely in the application (no redirection to the bank) and only requiring three clicks from the user:

1. Select to pay using biometric data.
2. Confirm the payment request (which initiates the biometric scan)
3. Done!

Integration options

For Biometric Pix, we offer one integration option:

Direct API and Payments Web SDK

Customize the user experience according to your brand needs and use our:

• Payments Web SDK to retrieve device information and biometric data.
• API to create and process payments.

Due to the required interaction between your application's front end (using the Web SDK) and server (Belvo API), at the moment we only offer this integration option.

Check out our dedicated Direct API (Biometric Pix) guide for the step-by-step instructions.

FAQs

Do my users need to enroll each of their devices separately?

Yes. Each device your user will use to make biometric payments (phone, tablet, computer) must be enrolled separately.

Will my users need to re-enroll a device after an operating system update?

Yes. For security purposes, institutions will require users to re-enroll a device after its operating system has been updated.

In what situations will an institution reject or revoke an enrollment?

A financial institution may reject or revoke an enrollment if its risk model detects factors that could compromise the security of the payment.

Do I need to collect the risk signals for each Payment Intent request?

Yes. Financial institutions require the risk signals to be sent with each payment request as part of the risk modelling.

Are there any daily or transactional limits?

Yes. Currently:

• The daily transaction limit is set by the user's institution’s Pix limit.
• The per-transaction limit is set by the user, with a maximum of 500 BRL per transaction.

Can a user have more than one enrollment per financial institution?

Yes. Users may have multiple enrollments if they are paying using multiple devices.

Is there a limit on the number of enrollments a user can have?

At present, there is no limit on the total number of enrollments a user can have.

How long until an enrollment expires?

By default, an enrollment expires after 5 years. However, users can set a shorter or indefinite expiration period when granting authorization for an enrollment.

Can I revoke an enrollment?

Yes. Belvo is currently developing a solution to allow you to revoke an enrollment. Users can also revoke an enrollment directly with their financial institution.