Brazil: dLocal payout bank details UX — stakeholder briefing

Audience: Business stakeholders
Purpose: Standalone read — what we ship under REVPAY-6359, why smoother Brazil dLocal payout-bank capture matters for doctors and payouts, and where to find the formal scope (Jira + request).
Formal scope / ACs: dp-payments-ai — request.md

At a glance — what this is & why we’re doing it

REVPAY-6359 improves Brazil dLocal payout bank capture in the revenue dashboard (first-time setup and payout settings) with a searchable bank list aligned to dLocal’s official Brazil payouts catalog, clearer placeholders, always-on CPF/CNPJ / BRL guidance, and bank-specific branch/account hints—so fewer bad details reach dLocal.

Why now: payout bank is a high-friction step: doctors must match bank code, agency/branch, and account to what dLocal expects. In Brazil we repeatedly see tens of merchants per month slowing down or failing that leg (support and ops see bank-validation and “account not found”-class outcomes). REVPAY-6359 is a focused UX upgrade that makes the path clearer and easier to complete—searchable bank list, stronger guidance, and bank-specific hints aligned to dLocal’s Brazil documentation.

1. Executive summary — headline for stakeholders

2. What we are delivering (short)

• Autocomplete bank code — find bank by code or name; options follow dLocal’s official Brazil bank list (e.g. 033 — Banco Santander Brasil S.A.).
• Placeholders that match how doctors read agency/account on statements or banking apps.
• Always-visible guidance — account must match CPF/CNPJ on file; BRL account required; incorrect details can cause failures.
• Conditional help for major banks (BB, Santander, Caixa, Bradesco, Itaú, HSBC Brasil, Inter) + generic fallback — same UX in onboarding and payout settings.

Prototypes: Onboarding · Payout settings

Demo — first-time bank account setup (onboarding)

~47 s recording (silent) of the improved bank-account flow during first-time setup — shows autocomplete, bank-specific guidance, placeholders, and interaction patterns end to end.

Direct link to MP4 · Absolute URL (for embedding elsewhere).

Demo — bank account update (payout settings)

~25 s recording (silent) of the same improved flow when a doctor updates their bank account in the payout settings configuration — same autocomplete, guidance, and bank-specific hints.

Direct link to MP4 · Absolute URL (for embedding elsewhere).

3. Why this is a major business blocker

1. Activation ≠ only identity (KYC) — without valid payout bank details accepted by dLocal, the doctor is not in a “clean” end state for marketplace payouts.
2. Errors are expensive at scale — support load, repeated submissions, and calendar days without payouts erode trust with high-value clinics.
3. High leverage fix — primarily doctor-facing UX + copy + maintained bank list, aligned to dLocal’s own documentation.

4. References

• Jira: REVPAY-6359
• Scope / ACs: dp-payments-ai — request.md
• dLocal doc: Brazil payouts

Prepared for stakeholder circulation. Authoritative delivery spec: Jira REVPAY-6359 + linked request.md in dp-payments-ai. Personal workflow note — not affiliated with the company dLocal (the payments provider).