🇲🇽 Mexico
RFC data, legal representatives and background checks for Mexican businesses
Overview
AiPrise verifies Mexican businesses by their RFC against the tax administration (SAT). A business verification returns the company profile, legal representatives when listed, and background checks on the company.
Coverage
| Data point | Returned | Note |
|---|---|---|
| Company profile | Yes | Legal name, status, registered address, email |
| Legal representatives | Yes, when listed | Listed for about 1 in 10 companies |
| Shareholders | No | |
| Ultimate beneficial owners | No | |
| RFC check | Yes | The RFC is the lookup key, so a match confirms it |
| Background checks | Yes | Business, legal and criminal background, tax and finance records, international lists and media alerts |
| Document | Returned |
|---|---|
| Register extract | No |
| Articles of association | No |
| Financial statements | No |
Speed
| Step | Typical | 9 in 10 within |
|---|---|---|
| Business verification (company data, legal representatives, background checks) | 45 seconds | 3.5 minutes |
These are typical times from production, not a service-level commitment: set timeouts well above them, or use callbacks.
Company types
Companies registered with the SAT under a company RFC (persona moral) are covered. Individuals with a business activity (persona física) are not.
| Company type | Legal forms | Covered | What to expect |
|---|---|---|---|
| Company (persona moral) | For example S.A. de C.V., S. de R.L. de C.V., S.C., S.A.P.I. de C.V. | Yes | Profile, and legal representatives when listed |
| Individual with a business activity (persona física) | 13-character personal RFC | No | Not covered |
Sources
| Register | What it gives |
|---|---|
| Servicio de Administración Tributaria (SAT) | Company profile, RFC check |
| Background databases | Business, legal and criminal background, tax and finance records, international lists, media alerts |
Identifiers
Send the RFC as tax_identification_number, with country_code set to MX.
| Identifier | Format | Example |
|---|---|---|
| RFC (company) | 12 characters: 3 letters, the incorporation date as YYMMDD, and a 3-character code | ABC010203XY1 |
Statuses and legal forms
Every result carries the register's own status in registration_info.status and an AiPrise status in registration_info.normalised_status. The normalised status is one of Active, Suspended, Dormant, Dissolved / Struck Off, In Liquidation / Insolvency or Unknown.
| Register status | Normalised status |
|---|---|
| found | Active |
The legal form is not returned as a separate field. It is usually part of the legal name, for example S.A. de C.V.
Quirks and gotchas
Country-specific behaviour to know before you integrate.
| Quirk | Details |
|---|---|
| Company RFC only | The RFC must be the 12-character company RFC. Anything else (for example a 13-character personal RFC) is not sent to the register and comes back with the warning COMPANY_NUMBER_NOT_VALID_FORMAT. About 1 in 14 checks hit this. |
found status | The status is found when the RFC exists. It maps to Active. Other statuses are rarely returned. |
| Postal code mismatches | About 1 in 8 checks flag ADDRESS_ZIPCODE_MISMATCH because the postal code sent differs from the registered one. Check the address you collected before declining. |
| Few legal representatives | Legal representatives come back for about 1 in 10 companies. Collect them in your onboarding flow when they are missing. |
Limits
- Shareholders, beneficial owners and register documents are not available.
- Individuals with a business activity (persona física) are not covered.
Updated about 20 hours ago