Capture the merchant identity
Collect the legal name, trading name, country, tax ID, registration number and registered address.
MERCHANT ONBOARDING & ACQUIRING
Merchant onboarding and acquiring controls.
Put identity evidence into the workflow.
Resolve the legal business behind a merchant’s VAT, EIN, or tax ID before underwriting, activation, or settlement configuration.
START WITHMerchant identity + country + tax IDREVIEWResolved legal entity + underwriting signals
Design the control around your systems and policy.Define countries, inputs, match rules, exceptions, evidence and delivery before integration.
WHEN TO USE IT
Reduce the risk of underwriting, configuring or settling the wrong legal merchant entity.
Use the company match as structured evidence inside the operating workflow. Keep inputs, results, source, retrieval time and exceptions together.
- A merchant applies under a trading name that differs from the contracting company.
- The merchant’s submitted tax ID must be reconciled with company registration details.
- An acquirer, PSP or marketplace needs consistent legal-entity data across onboarding systems.
THE WORKFLOW
Four steps. One clear result boundary.
Resolve the legal business
Match the submitted identifiers to the most likely registry-backed company record.
Compare application fields
Surface legal-name, identifier, address and status differences for underwriting review.
Pass evidence downstream
Send the resolved entity and exception signals into KYB, risk and merchant-activation rules.
WHAT YOU CAN REVIEW
The record, not just the number.
Fields vary by country and company. VATFind labels absent information instead of inventing a result.
- 01Merchant legal entity
- The registered company associated with the submitted business identity.
- 02Tax-ID association
- Whether the number is linked to the returned company record.
- 03Registration context
- Company number, legal form, address, incorporation date and status when available.
- 04Application discrepancies
- Differences between submitted fields and the resolved company record.
- 05Source evidence
- Source and retrieval context for underwriting and audit workflows.
READ THE RESULT CORRECTLY
Company identity is not merchant risk approval.
A company-record match does not establish transaction risk, expected volumes, MCC suitability, sanctions clearance, beneficial ownership, bank-account ownership or the merchant’s right to process payments. Those controls remain separate.
Review data and limitationsCOMMON QUESTIONS
Before you implement the workflow.
These answers define where company identity evidence fits—and what controls must remain separate.