Skip to main content
Release Type: Enhancement

​
Summary

Tax ID support is now extended beyond the entity itself:
  • Account KYB — the business being onboarded, its representative, and its owners can now provide a tax_id and tax_id_type.
  • Entity representatives — each entry in the Entity object’s representatives array now supports tax_id, tax_id_type and email.
Tazapay validates each tax ID against the country it belongs to, using the same rules as the entity-level tax_id_type.

​
What Changed

​
Account KYB

​
Entity representatives

Each entry in representatives[] of the Entity object supports:

​
tax_id_type values

Representatives (of both the Account KYB business and the Entity object) and owners are always validated as individuals, even when the parent entity or KYB is a business. They accept individual types only: ssn, itin, pan, cpf, others. Business types (ein, cnpj) are rejected with a tax_id_type error.

​
Validation

  • tax_id and tax_id_type must be provided together.
  • A person’s tax ID (representative or owner) is validated against the country in that person’s own address, not the registration country. For example, a US-based director of a Singapore company can provide an ssn.
  • Country-specific types must match the country. For example, pan is rejected outside India, and a US registration cannot use pan, cpf or cnpj.
  • ssn, itin and ein must be 9 digits, and itin must start with 9. pan, cpf and cnpj are format-checked for their country. others is not format-validated.
  • For countries without a dedicated type, use others.

​
Affected Endpoints

Entity
  • POST /v3/entity — Create Entity
  • PUT /v3/entity/{id} — Update Entity
  • POST /v3/entity/{id}/submit — Submit Entity
  • GET /v3/entity/{id} — Fetch Entity (each representative now includes tax_id, tax_id_type and email)
  • Entity webhooks — each entry in data.representatives now includes tax_id, tax_id_type and email.
Account KYB
  • Account KYB in the Tazapay Dashboard — tax ID fields for the business, the representative and owners.

​
Compatibility

This is a backward-compatible enhancement. All new fields are optional, so existing integrations and KYB applications that do not provide them are unaffected.
  1. Create Entity API Documentation
  2. Entity API Documentation
  3. Entity Webhooks
  4. KYB Overview
  5. Tax ID Type Support for the Entity Object