Aadhaar, CURP, PhilSys: why US compliance tools can't read foreign IDs

US KYB tooling is optimized for US documents: passports, driver licenses, EINs, SOS filings. That works until your corridor leaves the US. Stablecoin payment companies moving value to India, Mexico, or the Philippines run into national ID systems that US vendors only partially understand. The file is real. The vendor still rejects it.

What these IDs actually are

Aadhaar is India's biometric national ID, issued under UIDAI, widely used as identity evidence in financial onboarding. RBI sets the rules for how regulated entities treat customer due diligence. CURP is Mexico's unique population registry code. RFC is the tax ID. CNBV sits in the supervisory picture for financial entities. PhilSys is the Philippines' national ID program. BSP supervises payment and banking participants that rely on that identity layer.

Those are not exotic edge cases for a cross-border stablecoin company. They are the default identity anchors on the corridors that matter for payroll, supplier payouts, and B2B remittances. We list them as example corridors because that is where format friction shows up first.

Why US tools fail the read

Failures are usually not "the document is fake." Failures are schema and coverage. A registry-based KYB tool that shines on US SOS data may only shallow-parse Aadhaar fields. A document upload portal may accept a PDF and still fail downstream OCR rules written for US licenses. An API verification service may return a pass for a passport and a soft fail for PhilSys because the template library is thin.

Even when Vendor A reads Aadhaar correctly, Vendor B may require a different crop, a demographic XML sidecar, or a linked entity document that Vendor A never asked for. The payment company is left explaining to a client why the same card needs to be photographed three times.

What that means for corridor strategy

Corridor expansion is a compliance product decision, not only a liquidity decision. When you add India, you inherit Aadhaar-centric evidence patterns and RBI-shaped expectations from partners. Mexico brings CURP and RFC packages. The Philippines brings PhilSys. If your stack assumes every KYB vendor speaks US document dialects, each new corridor becomes a custom engineering project.

The durable approach is to treat foreign IDs as first-class inputs and to own translation across vendor formats. That is the KYB gap in concrete form: the document is fine, the handoff is broken.

Practical takeaway

Before you promise a corridor in sales decks, ask each infrastructure partner which KYB vendor they use and whether that vendor has production-grade support for the national ID on that corridor. Then ask what package shape they require. If the answers diverge, you do not have a document problem. You have an orchestration problem.

Syntex reads those documents natively so your compliance stack doesn't have to pretend they don't exist.