RFCCheck is a REST API that validates Mexican RFC numbers against the SAT database in real time. Use it from your invoicing pipeline, your CRM, or any flow that needs to confirm a taxpayer exists before you bill them.
What you can do
Each endpoint is scoped to what you already know. Skipping the cert lookup saves 1–3 s; skipping the zip search saves 7–9 s. Pick the one that fits the data you already have.
/rfc/validate
Full pipeline: registration, name, zip, certs, and SAT lists. Optional include_curp adds RENAPO identity for 5 additional credits.
/rfc/profile
Name, CURP, legal rep, and the email SAT has on file.
/rfc/find-zip
RFC + name in, SAT-registered postal code out.
/rfc/verify
Padrón check, or full RFC + name + zip combo verification.
/rfc/sat-lists
Article 69 / 69-B / 69-B Bis listings. Sub-second.
/rfc/verify-batch
Bulk verify up to 5,000 records in one round-trip.
/rfc/commerce-registry
Beta
Commerce registry records: legal regime, shareholders, and acts.
/cfdi/verify
Whether SAT has a CFDI (factura) and if it is current or cancelled.
/csf/verify
A Constancia de Situación Fiscal read and checked with SAT.
Part of MexCheck
RFCCheck is part of MexCheck, one API for Mexican identity and tax checks. One key, one plan, and one balance cover every MexCheck check: RFCs, invoices (CFDI), and Constancias de Situación Fiscal with SAT, CURPs with RENAPO, voter IDs with INE, electricity receipts as proof of address with CFE, and zip codes. See everything in the MexCheck docs .
Conventions
- All endpoints are POST, accept JSON, and return JSON.
- Base URL:
https://rfccheck.com/v1 -
Authentication: pass
x-api-keyon every request. -
Long-running endpoints (validate, find-zip, commerce-registry) accept an optional
webhook_urlto deliver the result async; verify-batch requires it.
Next steps
- Quickstart : make your first call in five minutes
- Authentication : generate and use API keys
- API Reference : browse every endpoint