Identity and tax verification for Mexico

# Verify every Mexican customer, company, and invoice against the official record.

MexCheck connects your onboarding, credit, payroll, and accounts-payable workflows to SAT, RENAPO, INE, and CFE, through one contract and one API.

[Talk to sales](#contact)

[Create an account](/users/register)

Already use RFCCheck, CURPCheck, or INECheck? [Log in with that account](/users/log-in) - it is the same MexCheck account.

Customer onboarding · example

Persona física

5 of 5 checks passed

- RFC registered with SAT

Name and postal code match the taxpayer record 1–2 s
- CURP matches RENAPO

Registered identity and certification status ~2 s
- Voter ID is current

INE reports the credential as vigente 4–15 s
- Address confirmed by CFE

Electricity receipt matches CFE's own copy 2–10 s
- Not on the SAT 69-B list

No listing under 69, 69-B, or 69-B Bis ms

Answers come from the registry that owns the data

SAT RENAPO INE CFE

Solutions

## Built for the teams that carry the risk when a record is wrong.

Each workflow needs a different mix of registries. MexCheck covers all of them on one account, so compliance, operations, and engineering work from the same source.

### Banking and fintech

Open accounts for people whose identity RENAPO and INE confirm, with a tax ID SAT confirms.

CURP · INE · RFC

### Lending

Check applicants and their employers before a credit decision, including the SAT lists.

RFC · SAT lists · INE

### Marketplaces and gig platforms

Onboard sellers, drivers, and hosts without reviewing documents by hand.

CURP · INE · RFC

### HR and payroll

Confirm every hire's CURP and RFC before their first payroll is stamped.

CURP · RFC · Batch

### Procurement and accounts payable

Vet suppliers' tax status and the SAT lists, and confirm an invoice is still current before you pay it.

RFC · SAT lists · CFDI

How each one works: [KYC and customer onboarding](/solutions/kyc-onboarding) [Proof of address](/solutions/proof-of-address) [Supplier verification](/solutions/supplier-verification)

Products

## Four registries. One platform.

SAT

### RFC

Registration, taxpayer name and profile, postal code, digital certificates, the SAT 69, 69-B, and 69-B Bis lists, and batches of up to 5,000 records.

[API reference →](/docs/endpoints#sat) [Guide: Supplier verification](/solutions/supplier-verification)

SAT

### CFDI status

Whether an invoice is current or cancelled, by folio or from its XML, with the folio that replaced it.

[API reference →](/docs/endpoints#sat) [Guide: Supplier verification](/solutions/supplier-verification)

RENAPO

### CURP

The identity RENAPO has registered for a CURP, or the CURP of a person found from their name, birth date, sex, and state of birth.

[API reference →](/docs/endpoints#renapo) [Guide: KYC and customer onboarding](/solutions/kyc-onboarding)

INE

### Voter ID

Whether INE reports a credencial para votar as current, with the elector key, districts, and the date it expires.

[API reference →](/docs/endpoints#ine) [Guide: KYC and customer onboarding](/solutions/kyc-onboarding)

CFE

### Proof of address

Whether CFE issued an electricity receipt, the address on CFE's own copy, and whether the file was edited.

[API reference →](/docs/endpoints#cfe) [Guide: Proof of address](/solutions/proof-of-address)

Each product also has its own site with developer docs. One account and one API key work on all of them. [Developer documentation](/docs)

Building with an AI assistant? Connect Claude, Cursor, or any MCP client and it reads the docs, runs real checks, and sets up your API key. [MCP server](/docs/mcp)

Security and privacy

## We check the record. We don't keep it.

Your customers' identifiers go from MexCheck to the registry and back. Your legal team gets a clear processor role to put in your privacy notice.

### No identifier storage

RFCs, CURPs, voter ID numbers, and the registries' answers are not stored. Only request metadata is kept, for billing and abuse prevention.

### Data processor under the LFPDPPP

MexCheck acts as your encargado and you stay the responsable. A Data Processing Agreement is available on request.

### Organizations and keys

Invite your team, give each system its own API key, and pay from one organization balance.

### Support in English and Spanish

The documentation and dashboard are in both languages, and so is our team at [help@mexcheck.com](mailto:help@mexcheck.com)

## One contract for every registry.

Prepaid credits cover every check. Enterprise agreements add volume pricing, a dedicated SLA, and support.

Self-serve

From $99 USD/month

10,000 credits a month for every endpoint, or pay as you go at $0.015 USD per credit.

[See plans and prices →](/pricing)

Enterprise

Volume pricing

Above 300,000 credits a month: up to 66% off, with a dedicated SLA and support.

[Talk to sales →](#contact) [hello@mexcheck.com](mailto:hello@mexcheck.com?subject=MexCheck%20Enterprise)

## Frequently Asked Questions

What is MexCheck?

MexCheck is one REST API for the checks Mexican onboarding, KYC, and invoicing need: RFC registration and taxpayer data with SAT, CFDI (invoice) status, CURP identity with RENAPO, voter ID (INE) status, and proof of address with CFE. One account, one API key, and one balance cover all of them.

Which checks can I run?

RFC: registration, taxpayer name and profile, postal code, digital certificates, SAT lists (69, 69-B, 69-B Bis), and bulk verification. CFDI: whether SAT reports an invoice as current or cancelled. CURP: the identity RENAPO has registered, or a CURP found from personal data. Voter ID: whether INE reports a credencial para votar as current. Proof of address: whether CFE issued an electricity receipt, and the address on its own copy.

How much does it cost?

Every check is priced in credits from one balance: 1 credit for an RFC verify or SAT-list check, 5 for a CFDI status, 10 for a full RFC validation, a CURP lookup, or an INE verification. Plans start at $99 USD/month for 10,000 credits, and extra credits cost $0.015 USD each without a subscription. New users get a $5 USD signup bonus.

What are RFCCheck, CURPCheck, and INECheck?

They are MexCheck's single-product sites, for teams that need just one check. They share MexCheck's accounts, API keys, and balance: sign in on any of them with the same email and password, and the same key calls every endpoint on any of the four domains.

Do you keep the RFCs, CURPs, and voter IDs we check?

No. MexCheck acts as your data processor (encargado): the identifiers you send and the registry's answers are not stored. Only request metadata is kept (the account, the endpoint, the HTTP status, and the time) for billing and abuse prevention. A Data Processing Agreement is available on request.

How do I authenticate?

Include your API key in the x-api-key header with every request. Create a free account, generate a key from your dashboard, and call any endpoint with it.

## Talk to our team.

Tell us which checks your workflow needs and how many you expect to run each month. We reply by email.

Or write to [hello@mexcheck.com](mailto:hello@mexcheck.com)