As per selection of the payment method, SmartPix option can be listed alongside the other payment methods. The Open Finance iconography and the indication that the payer will connect their account to any bank. Here is an example that must be followed by the merchant:

The next step is to present the authorization settings that will be granted by the payer. It can be a screen that continues the list of banks or a separate screen, as long as it presents:

1. Trigger. The description of the authorization that will be given by the payer to allow automated transactions.
2. Regulatory disclaimer.
3. A Call to Action button (“Mais configurações”) that optionally allows users to set transaction limits and the authorization period in the following steps.

Below is an example of this screen and, following, an explanation of each of the fields:

1. Trigger

It is necessary to present the payer with an explicit description of the authorization that will be given to allow automated transactions to happen. This trigger, or authorization, must represent the transactions that the merchant expects to make under the payer's authorization.

The required wording is: “A [merchant] poderá realizar transferências automáticas da minha conta bancária para adicionar saldo à minha conta dLocal e concluir pagamentos solicitados por mim.”

2. Regulatory disclaimer

One regulatory disclaimer is required before the user is redirected to the chosen bank for authorization:

• The message for the payer regarding the opening of the payment account that will be opened in the payer's name with dLocal, as well as the presentation for terms and conditions. The required wording is: “Ao confirmar, você concorda com a abertura de uma conta de pagamento na dLocal, de acordo com termos e condições disponíveis aqui.”
  • The terms and conditions should be linked to the wording above and are available here.

3. Call to Action button

This refers to an option that must be presented to users as a button labeled "Mais configurações".

The button does not block the main payment flow. Users can choose to skip it if they do not want to customize any settings.

When the user clicks this button, they are taken to one or more screens where they can: set transaction limits and define the authorization period.

These fields indicate the maximum limit the payer allows for payments. The limits can be:

1. total_allowed_amount. The total amount that can be charged using this consent is in local currency.
2. limit_per_payment. Max amount allowed in each charge in local currency.
3. periodic_limits. Represents the maximum value for each periodic limit (day, week, month, year), which still counts the number of transactions allowed and the maximum value for each transaction.

Configuration options

There are 3 possible configurations regarding the transaction limits:

1. The user can define all the limits. In this case, the payer can edit the limits on the limit editing screen. It's possible to create an authorization without defining these fields, which means that no authorization limits have been set. Therefore, payments can be requested in any amount and will not be blocked by this validation. Even so, the information that no limit has been set should be displayed on the screen.
2. The Merchant defines a limit_per_payment. In this case, the Merchant will define the limit_per_payment and the payer will not have access to the limit editing screen, but we should display the limit_per_payment that was defined. Besides that, two regulatory messages must be displayed:
   1. “Os próximos débitos serão no valor de produtos e serviços contratados por mim, com limite máximo de [R$ XXX,XX] por transação.”
   2. “Não é possível definir um limite para essa autorização.”
      The limit value must be provided in the field limit_per_payment of the requests. All the other limit fields in the request should remain empty.
3. All limits are undefined, and the merchant does not allow the payer to define them. In this case, the payer will not be able to access the limit editing screen, but we should display that no limit has been set. Moreover, two regulatory messages must be displayed:
   1. “Os limites são indefinidos para permitir que o valor de sua assinatura ou compra seja debitado.”
   2. “Não é possível definir um limite para essa autorização.”

All limit fields below in the request should remain empty:

{
  "limit_per_payment": null,
  "total_allowed_amount": null,
  "periodic_limits": {
    "day": {
      "max_payments": null,
      "total_allowed_amount": null
    },
    "week": {
      "max_payments": null,
      "total_allowed_amount": null
    },
    "month": {
      "max_payments": null,
      "total_allowed_amount": null
    },
    "year": {
      "max_payments": null,
      "total_allowed_amount": null
    }
  }
}

UX configurations

Here are examples of the screens for the three possible configurations.

The next setting is the duration of the authorization, for which the start date and end date must be displayed on screen for the payer.

• wallet.recurring_info.start_date indicates the start date of the authorization, and it is recommended to use the date when the authorization was created.
• wallet.recurring_info.end_date indicates the expiry date of the authorization, which can be undefined, indicating that the authorization will not expire until the customer requests cancellation: i) from the merchant, ii) from dLocal, or iii) from their home banking.

The expiration date must always be editable by the payer.

After the step described above, the user will be redirected to the bank to complete the authorization. Once this is successfully completed, dLocal will receive the redirect from the payer's bank and then redirect to the address indicated by the merchant, which will display the success screen.

In this step, it is required to show a confirmation screen in which the payer must be shown the authorization settings that have just been created (trigger, transaction limits, and term), in addition to the following information:

• Payer account data created in dLocal (branch and account number)
• Payer's name and tax ID
• Payment method: Pix
• Payment Initiation Service Provider: dLocal
• Authorization ID: identifier linking the payer to dLocal and its authorized bank.
• Regulatory disclaimer: “Importante: Os pagamentos sempre respeitarão os limites do seu banco ou os limites definidos aqui, o que for menor. Além disso, é necessário ter saldo em conta no momento em que cada pagamento é solicitado.”

Full screen content

It could be a single screen with all the information:

Expandable screen

Or a combination of a confirmation screen and a “More information” option that takes the payer to more information: