# Onboarding Brazilian Customers: A Fraud Prevention Checklist

> A practical checklist to stop onboarding fraud with Brazilian customers: CPF checks, name and birth date matching, document and selfie steps, and logging.

**Published:** November 22, 2026
**Author:** Lucas Vieira
**URL:** https://www.cpfhub.io/en/blog/brazil-onboarding-fraud-checklist

---


## Introduction

To prevent fraud when onboarding Brazilian customers, verify the [CPF](/en/blog/what-is-a-brazilian-cpf) (Brazil's individual taxpayer ID) against registry data at signup, compare the returned name and date of birth with what the user typed, and add document and selfie checks only where the risk calls for them. The checklist below turns that into concrete steps a product or risk team can ship.

It is written for teams outside Brazil that already run onboarding in other markets. Most of what you know still applies. What changes is the identifier, the data you can check against, and the fraud patterns that come with a number Brazilians share every day.

---

## Why Brazilian onboarding needs its own checklist

In Brazil the CPF is asked for at checkout, printed on invoices and on identity documents, and used as a Pix key. That makes it easy to collect and easy to steal. Knowing a CPF proves almost nothing about who is typing it.

Three patterns show up again and again in Brazilian signup fraud:

- **Made-up numbers.** A CPF generator produces numbers that pass the check digit algorithm but do not belong to anyone.
- **Borrowed or stolen identities.** A real CPF is typed with the fraudster's own name, or with the real holder's name copied from a leaked document.
- **Mass account creation.** Many accounts from the same device or network, often to farm signup bonuses or test stolen cards.

Each item in the checklist targets at least one of them.

---

## The checklist

### 1. Validate the format in the form

Check that the CPF has 11 digits and valid check digits before the user submits. It catches typos and lazy fake numbers with no network call. It does not prove that the CPF exists, so never stop here. The difference is explained in [CPF check digits vs a registry lookup](/en/blog/cpf-check-digit-vs-registry-lookup).

### 2. Look up the CPF on your backend

Confirm that the CPF exists and get the data linked to it. With [**CPFHub.io**](/en), the Simple Lookup is a `GET` request that returns the holder's name, gender and date of birth. Run it from your server, never from browser JavaScript, and read the key from an environment variable:

```javascript
// server-side only: the API key never reaches the browser
export async function lookupCpf(cpf) {
  const res = await fetch(`https://api.cpfhub.io/cpf/${cpf}`, {
    headers: {
      'x-api-key': process.env.CPFHUB_API_KEY,
      Accept: 'application/json',
    },
    signal: AbortSignal.timeout(10000),
  })
  if (res.status === 404) return null // not found: no credit used
  if (!res.ok) throw new Error(`CPF lookup failed: ${res.status}`)
  const body = await res.json()
  return body.data
}
```

A CPF that is not found returns 404 and does not use a credit. Treat it as "not verified" and ask the user to check the number.

### 3. Match the name and date of birth

This is the check that stops borrowed identities. Compare the date of birth exactly. For the name, normalize both sides (uppercase, accents removed, extra spaces collapsed) and compare with the `nameUpper` field. Brazilian names are long and often abbreviated, so allow for missing middle names instead of demanding an exact string. A real CPF with a different date of birth is one of the strongest fraud signals you will get.

### 4. Check the age

The date of birth from the lookup tells you whether the user is an adult. If your product is restricted to adults, decide the outcome here, not after the first transaction. See [age verification](/en/age-verification).

### 5. Check the registration status where the risk justifies it

For credit, payouts and regulated onboarding, also check the CPF's registration status at the [Receita Federal](https://www.gov.br/receitafederal/pt-br/assuntos/orientacao-tributaria/cadastros/cpf) (Brazil's federal tax authority). The [**Real-Time Lookup**](/en/cpf-lookup-federal-revenue) returns the status (regular, suspended, cancelled, holder deceased and others), the year of death when there is one, and a proof link. It needs the CPF and the date of birth.

### 6. Add document and selfie checks for high-risk actions

A matching CPF shows that the identity exists. It does not show that the user is its holder. For account opening at fintechs and exchanges, first withdrawals and large payouts, add liveness, face match and document reading. CPFHub.io's [**Identity Verification**](/en/identity-verification) runs those steps through the same API key, with RG, CNH and passport support. More in [document and selfie verification for Brazilian users](/en/blog/brazil-document-selfie-verification).

### 7. Limit one CPF to one account

Enforce a unique CPF per account in your database. A second signup with the same CPF is either a returning user who forgot their login or someone reusing an identity. Both deserve a different flow from a normal signup.

### 8. Watch device and network signals

Record the device, IP address and signup velocity. Several accounts with different CPFs from one device in a short window is a classic bonus abuse pattern, even when every CPF is real.

### 9. Log every decision

Store what you checked, when, and the outcome, without keeping more personal data than you need. Regulators, payment partners and your own disputes team will ask for it.

### 10. Tell users what you check and why

The [LGPD](https://www.planalto.gov.br/ccivil_03/_ato2015-2018/2018/lei/l13709.htm) (Brazil's data protection law) applies to foreign companies processing data of people in Brazil. Fraud prevention is a common legal basis for identity checks, and biometric data is sensitive data. State both in your privacy notice and confirm your setup with Brazilian counsel.

---

## Matching the checks to the risk

| Flow | Steps 1 to 4 | Step 5 | Step 6 |
|---|---|---|---|
| Marketplace buyer or delivery customer | Yes | No | No |
| Seller, courier or driver | Yes | Recommended | Optional |
| Betting or adult-only platform | Yes | Optional | At first withdrawal |
| Fintech or crypto account opening | Yes | Recommended | Yes |
| Credit and high-value payouts | Yes | Yes | Yes |

Regulated sectors have their own duties. Financial and payment institutions, for example, follow the Banco Central do Brasil's [Circular 3,978/2020](https://www.bcb.gov.br/estabilidadefinanceira/exibenormativo?tipo=Circular&numero=3978) on customer identification. See [Brazil KYC requirements](/en/blog/brazil-kyc-requirements) for the overview.

---

## Common mistakes

- **Trusting the checksum.** Valid check digits only mean the number is well formed.
- **Calling the API from the frontend.** It exposes your key. The browser calls your own route, and your server calls the API.
- **Blocking on a strict name match.** Abbreviated middle names and accents cause false rejections. Normalize first.
- **Running biometrics on everyone.** It adds friction to low-risk users. Escalate when the user reaches a risky action.

---

## Frequently asked questions

### What is the minimum check for Brazilian signups?

Check digit validation in the form plus a CPF lookup on the backend with name and date of birth matching. That blocks made-up numbers and most borrowed identities at a low cost per user.

### Should I reject a user when the CPF is not found?

Ask the user to review the number first, since typos are common. If it is still not found, do not activate the account until the identity is confirmed another way, such as a document check.

### Do I need the Receita Federal status for every user?

No. The registration status matters most for credit, payouts and regulated onboarding. For low-risk flows, the Simple Lookup with name and date of birth matching is usually enough.

### Can I test the checklist before going live?

Yes. The free plan has 50 credits per month and no credit card, enough to build and test the flow. See [pricing](/en/pricing) and the [signup fraud prevention](/en/solutions/signup-fraud-prevention) page.

---

### Read also

- [How to Verify a Brazilian CPF Number](/en/blog/how-to-verify-a-brazilian-cpf)
- [Brazil KYC Requirements in 2026: What Foreign Companies Need to Know](/en/blog/brazil-kyc-requirements)
- [CPF Check Digits vs a Real Registry Lookup](/en/blog/cpf-check-digit-vs-registry-lookup)
- [Document and Selfie Verification for Brazilian Users](/en/blog/brazil-document-selfie-verification)

## Conclusion

Onboarding fraud in Brazil starts with a CPF that is easy to find and easy to fake. Validate the format, look up the CPF on your backend, match the name and date of birth, and escalate to registration status, documents and biometrics only when the user's action carries real risk. Log what you decide and tell users why you check.

Build the flow with 50 free credits and no credit card at [cpfhub.io](/en).

