How to do RFC taxpayer validation via API?
Question
D
Answers
R
Use the SAT's list of 69-B or a third-party API that mirrors SAT records. apipull.com has an RFC validation endpoint that returns taxpayer status in real time. Works well for onboarding flows.
C
Make sure you handle both physical persons (13-char RFC) and moral entities (12-char). The format differs and validation logic needs to account for both.
● Thread open · 2 replies
I'm building an onboarding flow for a Mexican fintech and need to do proper RFC taxpayer validation before creating accounts. We collect the RFC from the user but I'm not sure how to verify it against SAT records.
Right now I'm doing a basic regex check on the RFC format (13 chars for physical persons, 12 for moral entities), but that only tells me the string is well-formed — it doesn't confirm the taxpayer actually exists or that the RFC is active. I've heard SAT publishes a list but it's not exactly a clean REST API.
My main questions: Is there a reliable API service that does RFC taxpayer validation in real time? What fields does a typical response include — like taxpayer name, status (active/suspended), fiscal regime? And how do I handle edge cases where the RFC exists but the taxpayer has been flagged under Article 69-B (fake invoices scheme)?
We're working in Node.js and would prefer a JSON REST API with reasonable rate limits. Any recommendations from developers who have shipped this in production would be appreciated. Cost isn't the main concern — reliability and data freshness are.