Business Identity API

When to use this API

Business Identity API resolves company identifiers and returns a normalized company profile for operational review. Depending on country and configured providers, lookups can include official registry data, EU VAT validation (VIES), local tax status signals, whitelist checks and bank account verification metadata. Results are source-backed signals, not legal advice, AML/KYC decisions or compliance guarantees.

• You need to validate company identifiers before creating records in your system.
• You want to reduce manual review in B2B onboarding flows.
• You need consistent identifier checks across multiple countries with country-specific capability control.

Typical use cases

• Business identity pre-checks in registration or onboarding flows.
• ERP/CRM data quality gates.
• Invoice recipient and vendor verification.
• B2B counterparty data review before invoicing or payout.

Billing and APIRAPTOR token model

Business Identity usage is metered per real business identity lookup through the `business_identity_lookup` service billing event.

• Tokens are the APIRAPTOR communication unit: 1 token = 100 subtokens.
• Trial availability, token amount and duration come from Billing configuration.
• All services are available from day one; Business Identity is not premium-gated per plan.
• This is service billing event metering, not ordinary API-call billing.

Tax status and VAT validation

EU VAT validation is handled through VIES where applicable, while local tax status is resolved from country-specific official sources when configured and available.

• VIES is used for EU VAT validity checks and reported separately in vatValidation.
• Local tax status is returned in taxStatus when official country sources expose it.
• VIES does not replace country tax registries or whitelist datasets.

Bank account and whitelist checks

Bank account and whitelist enrichment are country-dependent features controlled by runtime policy.

• Whitelist status is returned only when an official country source supports it.
• Bank account data is returned only when source availability and configuration allow it.
• Some countries support verification-only flows rather than full account listing.

Counterparty data review for invoicing and B2B operations

The normalized response helps reduce data-quality risk in onboarding, invoicing and operational review flows.

• Check supplier or buyer identity data before invoice issuance.
• Detect incomplete or inconsistent registration/tax data early.
• Use returned source signals as inputs to your own business policy, not as automatic legal, AML/KYC or compliance approval.

Decision boundary

Business Identity returns source-backed registry, VAT, tax, whitelist and bank-account signals for review workflows.

• It does not provide legal advice, sanctions screening, AML/KYC decisioning or a compliance guarantee.
• Official sources can be unavailable, incomplete or delayed.
• Regulated decisions should rely on your own human, legal and operational review process.

Country-by-country data availability

Coverage varies by country, official source access model and configured credentials.

• Some countries are fully live, others require credentials or remain disabled by default.
• Capability depth differs across company registry, VAT, tax status, whitelist and bank accounts.
• The dashboard and admin config expose effective runtime coverage per country.