We can't find the internet
Attempting to reconnect
Something went wrong!
Attempting to reconnect
Verify RFC registration with the SAT, look up digital certificates, and validate taxpayer names - all through a simple REST API.
Six endpoints scoped to what you already know. Skip the slow steps when you have part of the answer.
RFC in, everything out: registration status, name, zip, digital certificates, and SAT contributor-list presence. ~30s (cert lookup + zip search). Webhook supported.
RFC in, SAT-registered personal data out: name and CURP for individuals; company name plus legal representative RFC + CURP for companies; the contact email SAT has on file. ~1-3s. For KYC, account onboarding, and pre-filling customer records.
RFC + name in, SAT-registered zip out. Critical for CFDI 4.0 invoicing where the customer name is already on file but the zip is missing. Skip cert lookup, save 1-3s. Webhook supported.
RFC alone for a quick padrón check, or RFC + name + zip for a full combo verification. Single SAT roundtrip, ~1-2s. Use to confirm customer-supplied data or re-validate an existing record.
RFC in, 69-B / 69 / 69-B bis listings out. Local DB lookup, milliseconds. Use for compliance dashboards, KYC, and counterparty screening.
Up to 5000 records per call in ~10-15s, so the per-record cost is tiny when amortized. Use for periodic compliance sweeps over your customer database. Webhook required.
An RFC (Registro Federal de Contribuyentes) is Mexico's federal taxpayer identification number, issued by the SAT (Servicio de Administración Tributaria). Every individual and business operating in Mexico is assigned a unique RFC used for tax filings, electronic invoicing (CFDI), and commercial transactions.
RFC validation is essential for e-invoicing compliance, KYC (Know Your Customer) processes, and verifying business partners. The RFCCheck API connects directly to the SAT database to provide real-time validation, taxpayer name verification, and digital certificate lookup in a single API call.
A single API call is all you need
curl -X POST https://rfccheck.com/v1/rfc/validate \ -H "x-api-key: rfc_your_api_key" \ -H "Content-Type: application/json" \ -d '{"rfc": "XAXX010101000"}'{ "rfc": "XAXX010101000", "valid": true, "message": "RFC válido, puede ser utilizado en comprobantes", "zip": "06600", "name": "EMPRESA EJEMPLO SA DE CV", "certs": [ { "serial": "00001000000500000001", "status": "Activo", "type": "FIEL", "valid_from_utc": "2020-01-15T00:00:00Z", "valid_to_utc": "2024-01-15T00:00:00Z", "email": "[email protected]", "legal_representative_rfc": "UIOJ750110R13", "legal_representative_curp": "UIOJ750110HDFRRN09", "cer_base64": "MIIF..." } ], "sat_lists": [ { "article": "69", "sub_list": "cancelados", "situation": "CANCELADOS POR INSOLVENCIA", "name": "EMPRESA EJEMPLO SA DE CV", "person_type": "M", "state": "CIUDAD DE MEXICO" } ]}Pay by credits, not by request. Cheap endpoints cost less; /sat-lists is free under any plan.
Extra credits at $0.015 USD each. No plan required; prepaid balance works too.
| Endpoint | Credits | USD overage |
|---|---|---|
/rfc/sat-lists |
Free / 1 no plan | $0.00 / $0.015 |
/rfc/verify |
1 | $0.015 |
/rfc/profile |
3 | $0.045 |
/rfc/find-zip |
5 | $0.075 |
/rfc/validate |
10 | $0.15 |
/rfc/verify-batch |
1 × N records | $0.015 × N |
Need more? Extra credits cost $0.015 USD each. Free users can also use the API with prepaid balance.
RFCCheck is a REST API that validates Mexican RFC (Registro Federal de Contribuyentes) numbers against the SAT database in real-time. It returns registration status, the registered taxpayer name, and digital certificate information including serial numbers, validity dates, status, contact email, legal representative RFC and CURP, and the base64-encoded certificate.
Plans are denominated in credits. Basic: $110/month for 10,000 credits (~1,000 /validate calls). Pro: $2,150/month for 200,000 credits. Business: $9,900/month for 1,000,000 credits. Extra credits cost $0.015 USD each (no plan required; prepaid balance works too). /sat-lists is free on any plan; pay-as-you-go callers pay 1 credit per call. New users get a $5 USD signup bonus.
The API returns whether the RFC is valid and registered with SAT, the official taxpayer name, the postal code, an array of digital certificates (CSD/FIEL) with their serial numbers, validity dates, active/revoked status, contact email, legal representative RFC and CURP, and the base64-encoded .cer file, plus a list of SAT published contributor lists (Articles 69, 69-B, 69-B Bis) the RFC appears in, if any.
Yes. RFCCheck validates both persona fisica (individual, 13-character) and persona moral (business, 12-character) RFC numbers. The API automatically detects the RFC type and queries the appropriate SAT records.
When your monthly plan credits are exhausted, requests start drawing from your prepaid balance at $0.015 USD per credit. If neither has capacity, the API returns 402 (Payment Required). You can add prepaid balance from your dashboard to continue making requests without upgrading your plan.
Include your API key in the x-api-key header with every request. You can generate API keys from your dashboard after creating a free account. Example: -H "x-api-key: rfc_your_api_key"
Match the endpoint to what you already know. /rfc/validate runs the full pipeline if you only have an RFC, or in ~12 seconds if you pass an optional name. /rfc/profile returns the SAT-registered personal data: name and CURP for individuals, company name and legal representative for companies, plus the contact email on file, all in 1-3 seconds. /rfc/find-zip skips the cert lookup when the customer name is already on file. /rfc/verify confirms a complete RFC + name + zip combination in 1-2 seconds. /rfc/sat-lists is a millisecond local lookup. /rfc/verify-batch handles up to 5000 records in one call for periodic compliance sweeps.
For companies (persona moral) submit the razón social WITHOUT legal-entity suffixes. Strip S.A. de C.V., SAPI de C.V., SAB de C.V., S de RL de CV, SOFOM, AC, SC, SAS, and similar regimen tags. For individuals (persona física) submit the legal name as registered with SAT: apellido paterno, apellido materno, then nombres, with no honorifics. The server safety-cleans known company suffixes, but pre-cleaned names yield faster, more reliable matches.
Create an account, get your API key, and start validating RFCs in minutes.
Sign up now and get a $5 USD signup bonus - limited time offer!
Create Free Account