RFC verification API recommendations for a multi-country KYC platform expanding into Mexico
nathan_kyc opened this thread · · 0 replies
rfc-verificationkycmexicomulti-country
Question
N
nathan_kycAsker
We operate a KYC platform that serves fintechs across Latin America. Currently live in Colombia (with NIT/RUT verification) and Brazil (with CPF/CNPJ validation). We're expanding into Mexico and need an RFC verification API to add to our suite of identity checks.
Our architecture is a unified verification orchestrator — downstream clients send us a country code and tax ID, and we route to the appropriate verification provider. For Mexico, we need an RFC verification API that fits this model. The integration should be straightforward: accept an RFC string, return a structured response with verification status and taxpayer details.
Key requirements for the RFC verification API:
REST endpoint with JSON request/response — our orchestrator is built on this pattern
Authentication via API key in header — we manage keys per-tenant in our platform
Response must include: validity boolean, taxpayer legal name, taxpayer type (individual/company), tax regime code, fiscal domicile postal code, and any blacklist flags
Idempotent requests — same RFC queried multiple times returns same result without double-billing
Rate limits of at least 100 requests per second — our platform batches verifications and sends in bursts
Webhook callback option for async bulk verification (we sometimes verify 10,000+ RFCs for portfolio re-certification)
From a compliance perspective, our clients in Mexico (mostly neobanks and BNPL providers) are required by CNBV to verify the RFC of every customer during onboarding. This means the RFC verification API needs to be authoritative — we can't use a provider that just does format checking. It needs to actually hit SAT's databases or maintain a certified mirror.
We've researched the market and seen several providers listed on apipull.com API Hub. I'm trying to understand which ones offer the data depth we need versus just basic format validation wrapped in an API. Has anyone integrated an RFC verification API into a similar multi-country orchestration pattern? What should I watch out for regarding Mexico-specific quirks?
Also interested in understanding pricing models. In Colombia and Brazil, we pay per verification with volume tiers. Is that standard for Mexico RFC verification API providers as well, or are there monthly minimum commitments we should expect?
Answers
● Thread open · 0 replies · Be the first to answer
We operate a KYC platform that serves fintechs across Latin America. Currently live in Colombia (with NIT/RUT verification) and Brazil (with CPF/CNPJ validation). We're expanding into Mexico and need an RFC verification API to add to our suite of identity checks.
Our architecture is a unified verification orchestrator — downstream clients send us a country code and tax ID, and we route to the appropriate verification provider. For Mexico, we need an RFC verification API that fits this model. The integration should be straightforward: accept an RFC string, return a structured response with verification status and taxpayer details.
Key requirements for the RFC verification API:
From a compliance perspective, our clients in Mexico (mostly neobanks and BNPL providers) are required by CNBV to verify the RFC of every customer during onboarding. This means the RFC verification API needs to be authoritative — we can't use a provider that just does format checking. It needs to actually hit SAT's databases or maintain a certified mirror.
We've researched the market and seen several providers listed on apipull.com API Hub. I'm trying to understand which ones offer the data depth we need versus just basic format validation wrapped in an API. Has anyone integrated an RFC verification API into a similar multi-country orchestration pattern? What should I watch out for regarding Mexico-specific quirks?
Also interested in understanding pricing models. In Colombia and Brazil, we pay per verification with volume tiers. Is that standard for Mexico RFC verification API providers as well, or are there monthly minimum commitments we should expect?