API for embedded tax validation infrastructure for payment ecosystems
Embed real-time IRS TIN matching, EIN lookup, address validation, and sanctions screening directly into your onboarding and payout workflows. Designed for fintechs, marketplaces, payroll platforms, and vendor onboarding systems — REST in, JSON out, no IRS enrollment.
Generate an API key from your account. First call in minutes.
curl -X POST "https://www.tincomply.com/api/v1/validate/irs-tin-name-matching" \
-H "X-API-Key: YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"tin": "123456789",
"name": "NORTHWIND TRADING CO"
}'Part of every TIN Comply plan from $20/mo — not a separate purchase. See pricing
Bad payee data is cheapest to fix at the moment it's entered
Payment platforms, marketplaces, and payroll systems usually discover invalid TINs late — during 1099 prep, payout exceptions, or vendor remediation. By then the account is active, the money has moved, and the correction is a campaign rather than a form field. Validating at onboarding collapses all of that into one API call.
Catch mismatches early
Validate TIN and legal name at onboarding to cut CP2100 and B-Notice risk, and prevent payout and filing delays that surface at the worst possible moment in the calendar.
Designed for integration
Simple REST endpoints, predictable JSON responses, and explicit error handling — including telling you what it couldn't validate and why, rather than silently omitting it.
Audit trails & controls
Every call is logged with timestamps, source, and outcome, so risk, finance, and compliance have visibility into validations that no human initiated.
Where teams embed TIN Comply
Add validation at the exact points in your workflow where bad data creates the most cost.
-
1
Seller / contractor onboarding Validate TIN and name and prompt remediation before the account is activated — while the payee still has a reason to respond.
-
2
Payout & payee management Block payouts on mismatches or route them to exception handling automatically, rather than discovering the problem at year end.
-
3
Vendor master data & ERP sync Standardize and validate upstream, then sync clean records into your ERP and finance systems.
-
4
1099 readiness checks Run bulk validations to find and remediate issues well before year-end deadlines.
{
"id": "ZfPjt...",
"request": { /* echo of submission */ },
"irsTinNameMatchingResult": {
"message": "TIN and Name combination matches IRS EIN records",
"result": 7,
"completed": true
},
"listMatchResult": {
"message": "No matches found",
"completed": true
}
}Building blocks, or an end-to-end validation pipeline
Use individual endpoints where you need them, or submit everything at once and let the response tell you what resolved.
IRS TIN matching
Validate TIN and name and interpret the result code inside your onboarding workflow.
EIN lookup & entity signals
Fill gaps in payee data and improve accuracy before vendor records are created.
Compliance screening
Support risk workflows with sanctions and watchlist screening across 330+ lists.
Bulk + real-time
Scale via individual calls or bulk workflows depending on use case and throughput.
Audit-ready logging
Every call stored with timestamps and IDs for traceability and compliance review.
First call to production embed
Create an account
Generate an API key and configure your environment. No IRS enrollment, no provisioning wait.
Test endpoints
Start with TIN matching, then add address validation and screening as your workflow needs them.
Embed into workflows
Enforce validation gates during onboarding, payouts, and year-end readiness checks.
One thing worth knowing before you build a retry loop. The IRS locks accounts for 96 hours on duplicate submissions — trivially easy to trigger from a retry, a replayed webhook, or two services validating the same payee. TIN Comply de-duplicates before anything reaches the IRS, so ordinary integration behaviour doesn't take your validation offline for four days.
Questions engineering teams ask first
How do I authenticate?
An API key in the X-API-Key header over HTTPS. Keys are generated from your TIN
Comply account — there's no separate IRS e-Services enrollment or credential provisioning step
before your first call.
Is there an official IRS TIN matching API?
No. The IRS's free e-Services program offers an interactive screen limited to 25 name/TIN combinations at a time, and a bulk file upload returning results in roughly 24 hours. Neither is callable from application code.
TIN Comply exposes IRS TIN matching as a REST endpoint returning JSON in real time, which is what makes it embeddable in an onboarding flow at all.
What does a response contain?
A request identifier, an echo of the submission, and a result object per validation performed. The IRS TIN matching result carries a numeric result code, a plain-language message explaining what that code means, and a completion flag. Screening and other selected validations return alongside it in the same response.
Can I run several validations in one call?
Yes. Submit a TIN, legal name, and address and every validation that data supports runs, with a result object for each in the response.
Anything that couldn't run — GIIN validation when no GIIN was supplied, for instance — is reported explicitly rather than silently omitted, so your code never has to infer the difference between "clean" and "not checked."
Does API activity appear in the audit trail?
Yes — every request is logged with source, timestamp, and result exactly like portal activity, and history can be filtered specifically to API requests. That matters when validation is embedded in an ERP and no individual user initiated the call.
How do I avoid the IRS 96-hour duplicate lockout at scale?
You don't have to design around it. The IRS locks accounts for 96 hours on detected duplicate submissions — easy to trigger from a retry loop or two services validating the same payee. TIN Comply de-duplicates before anything reaches the IRS.
What you can call
Build validation into your platform in days, not months
Start with the API docs, generate a key, and embed tax validation where bad data actually costs you — at onboarding, at payout, and before filing season.
REST in, JSON out. No IRS enrollment.