Signup fraud prevention

Stop signup fraud with CPF lookup

At signup, the user gives a CPF (and optionally name and date of birth). You call the API and compare. The matching rule stays in your system.

Start for free Read the docs See solutions by industry

JTBD: Match at signup
Compare the CPF given with the name and date of birth returned by the API, at the moment of signup.
Not a credit bureau, no scoring
We do not provide a credit score, a restrictive list or risk analysis. Only basic registration data.
Not biometric KYC
No selfie, document OCR or face match. The CPF lookup feeds the rule you implement.
E-commerce, fintech, marketplaces
The same GET serves checkout, account opening and seller onboarding. There are pages by industry.

Example

One GET and the full JSON comes back

x-api-key header. Base https://api.cpfhub.io. No version in the URL.

cURLGET /cpf/{cpf}

curl -X GET \
  'https://api.cpfhub.io/cpf/12345678909' \
  -H 'x-api-key: YOUR_API_KEY'

JSON response200 OK

{
  "success": true,
  "data": {
    "cpf": "12345678909",
    "name": "Fulano de Tal",
    "nameUpper": "FULANO DE TAL",
    "gender": "M",
    "birthDate": "15/06/1990",
    "day": 15,
    "month": 6,
    "year": 1990
  }
}

By industry

The same lookup, examples from your industry

Signup fraud prevention works the same in any business. If you want cases and data specific to your industry, see the dedicated page below.

E-commerce

Delivery

Streaming

Adult Content

Social Networks

Healthcare & Pharmacies

Clinics & Medical Offices

HR & Hiring

Real Estate

Insurance

FAQ

Frequently asked questions

Does it replace KYC?

No. It is a registration lookup for your system to compare CPF, name and date of birth. No selfie, OCR or biometrics. For biometric KYC you need another provider.

Does it query Receita Federal live?

For signup fraud prevention, the recommended route is GET /cpf/{cpf}, which has a typical time of ~150 ms (not an SLA) from our database. The real-time query to Receita Federal (Brazil's federal tax authority) is the Real-Time Lookup, which requires the holder's date of birth, takes about 1 second (typical time, not an SLA) and costs 1.5 credits. See /en/cpf-lookup-federal-revenue.

Does it work for e-commerce?

Yes. At signup or at checkout you compare the data and apply your own rule. If your business is e-commerce, also see /en/solutions/ecommerce, with examples specific to the industry.

Still have questions?

Get in touch

Stop fake signups
at the door.

Compare CPF, name and date of birth through the API. 50 free credits to test your matching rule.