Additional KYC/KYB data required for EEA customers In Europe, Bridge is transitioning to a dual-licensed Electronic Money Institution (EMI) and Crypto-Asset Service Provider (CASP) under the MiCA framework, which will offer enhanced consumer protections and new product capabilities in the region. As part of this transition, Bridge will be updating KYC/KYB onboarding and verification requirements for EEA individual and business customers beginning June 15th. This will require you to collect additional data if you are using the Customer API. For existing EEA resident customers, we will provide personalized KYC links for customers with missing data in the Bridge Dashboard for you to send to your customers. They will need to submit the missing data by June 26th.Documentation Index
Fetch the complete documentation index at: https://apidocs.bridge.xyz/llms.txt
Use this file to discover all available pages before exploring further.
API requests in scope
You will need to adjust create/update payloads when onboarding new customers and provide additional information for existing customers who fall under EEA scope:- The individual’s residential address is in the EEA
- The business’s incorporation address is in the EEA, or
- The business’s physical operating address is in the EEA, or
For live reference on the APIs mentioned here, see Create a customer, Update a single customer object, and Create a new associated person.
POST | PUT /v0/customers — individual / associated persons
Live reference: Create a customer Update a single customer objectSummary of changes (to be enforced starting June 15th for new customers; required for existing customers by June 26th)
The following fields will be newly required or need to be adjusted for individuals with an EEA country of residence OR UBOs/Associated Persons mapped to a business incorporated or physically located in the EEA:| Requirement | New requirement (to be enforced June 15th for new customers; June 26th for existing customers) | Current state | Sample code |
|---|---|---|---|
| Country of birth and city of birth | Country of birth is a new required field. We also recommend collecting the city of birth, as this will be required by EU law in 2027. | Country of birth and city of birth are not required. | Link |
| Nationalities | All nationalities of the individual will be required in a new field: “nationalities”. The existing “nationality” field that optionally collects only one nationality will be deprecated. | Providing nationality in the “nationality” field is optional. | Link |
| Account purpose | Account purpose is required for all individuals (not applicable for associated persons or UBOs). | Account purpose is only required for high risk individuals. | Link |
| National Identification Number AND Tax ID Number (TIN) Tax ID Number due December 31st, 2026 | Must collect both a valid National ID number and a valid Tax ID Number (TIN) Please refer to valid National ID number and Tax ID Number (TIN) types by country below | Can collect National Identification number OR Tax Identification Number | Link |
| TIN issuing country and country of residence match Due December 31st, 2026 | Tax ID Number (TIN) must be issued by the country of residence submitted; customers may not claim “no valid tax ID” | The Tax Identification number (TIN) does not need to be issued by the country of residence submitted. | Link |
| Tax residency status Due December 31st, 2026 | If an individual has tax registrations with any tax authority outside the country they reside in, tax registration information for each of those additional countries is required. | Collecting tax registration information for foreign tax registrations is not required. | Link |
| Identify verification | No additional data required. However Bridge will perform a database check on the individual. If the database check does not pass, Bridge will require more information to be submitted. | Individuals must only submit and verify a photo ID. | |
| Expired government IDs | Customers with an expired government photo ID will lose access to their endorsements. | Do not require refreshing expired government photo IDs. |
Country of birth and city of birth
Place of birth takes country and city. country is now required in the following format. While only country is required, we recommend you start collecting city as well; it will be required under EU law in 2027. Code SampleNationalities
It is now required to provide all existing nationalities for an individual, ISO 3166-1 alpha-3. During migration we will still honor what you send through field nationality (single string) along with field nationalities. Afterwards we will be deprecating the nationality field. Code SampleAccount purpose
The field account_purpose is now required. account_purpose_other: free text should only be used when account_purpose is other. Code SampleNational Identification Number AND Tax ID Number (TIN)
It is required to provide both a National ID number and, by December 31, 2026, a Tax ID Number (TIN) for each individual. See list of tax IDs and national IDs by country. Code SampleTIN issuing country and country of residence match + tax residency (foreign registration)
Supported National and Tax Ids
Supported National and Tax Ids
Universal Tax ID Types: [tin]
Universal National ID Types: [national_id, passport, nin, pan, other]
Please use a universal type if no type is specified for your customer’s country in the tables below.
| Country | National Id | Tax Id |
|---|---|---|
| AUT | si | si |
| BEL | nrn | nrn |
| BGR | ucn | ucn |
| CYP | - | - |
| CZE | rc | rc |
| DEU | - | - |
| DNK | - | - |
| ESP | nie | nie |
| EST | ik | ik |
| FIN | hetu | hetu |
| FRA | nir | nir |
| GLP | nir | nir |
| GUF | nir | nir |
| MAF | nir | nir |
| MTQ | nir | nir |
| MYT | nir | nir |
| REU | nir | nir |
| GRC | - | - |
| Country | National Id | Tax Id |
|---|---|---|
| HRV | oib | oib |
| HUN | nin | nin |
| IRL | ppsn | ppsn |
| ISL | tin | tin |
| ITA | cf | cf |
| LIE | - | - |
| LTU | ak | ak |
| LUX | - | - |
| LVA | - | - |
| MLT | icn | icn |
| NLD | bsn | bsn |
| NOR | fn | fn |
| POL | pesel | pesel |
| PRT | nin | nin |
| ROU | - | - |
| SVK | rc | rc |
| SVN | emso | emso |
| SWE | - | - |
POST | PUT /v0/customers — business
Live reference: Create a customer (business payload), Update a single customer object (business payload)Summary of changes (to be enforced starting June 15th for new customers; required for existing customers by June 26th)
The following fields will be new or newly required for businesses that are incorporated in or operate within the EEA.| Requirement | New requirement (to be enforced in the Customer API starting June 15th) | Current state (no longer valid starting June 15th) | Sample code |
|---|---|---|---|
| Ownership document | Ownership document is required at the business level. | Ownership document can be skipped if an associated person who has control attests to the ownership structure (attested_ownership_structure_at). | Link |
| Business registration number and business tax ID number Tax ID Number due December 31st, 2026 | Must collect both Business Registration Number and Business Tax Id Number. Refer to valid numbers by country below | Can collect Business Registration Number OR Business Tax ID Number | Link |
| Business registration number and incorporation country match | The issuing country of the business registration number must match the incorporation country. | - | Link |
| Business Tax ID country and incorporation country match Due December 31st, 2026 | The issuing country of the business tax ID must match the incorporation country. | Business tax ID was required, but did not need to match the incorporation country. | Link |
| Foreign tax registration status Due December 31st, 2026 | If a business has tax registrations with any tax authority outside the country they are registered for, tax registration information for each of those countries is required. | Collecting tax registration information for foreign tax registrations is not required. | Link |
| Business Registry | If Bridge is unable to verify the business with an automated registry check, both an evidence of good standing document and a business formation document are required. | Can collect Evidence/certificate of good standing OR a business formation document (i.e. Articles of Incorporation) if automated business registry verification is unsuccessful. | Link |
Ownership document
Business registration number and business tax ID number
It is required to provide both a Business Registration Number and, by December 31, 2026, a Business Tax Id Number.Supported Business registration and Tax Ids
Supported Business registration and Tax Ids
| Country | Business registration | Tax Id |
|---|---|---|
| AUT | fn | uid |
| BEL | bce, kbo | bce, kbo |
| BGR | uic | uic |
| CYP | crn | tin |
| CZE | ico | ico |
| DEU | crn | ust_idnr |
| DNK | cvr | cvr |
| ESP | cif | nif |
| EST | rc | rc |
| FIN | y_tunnus | y_tunnus |
| FRA | siren, siret | siren, siret |
| GRC | aom | gemi |
| HRV | oib | oib |
| HUN | crn | tin |
| IRL | cro | trn, chy, rcn |
| Country | Business registration | Tax Id |
|---|---|---|
| ISL | id | id |
| ITA | cf | cf, partita_iva |
| LIE | peid | peid |
| LTU | cc | cc |
| LUX | matricule | matricule |
| LVA | rn | rn |
| MLT | crn | vat |
| NLD | kvk | vat |
| NOR | org, orgnr | orgnr |
| POL | krs | nip |
| PRT | nipc | nif |
| ROU | cui | cui |
| SVK | ico | ico |
| SVN | ms | tin |
| SWE | org, orgnr | orgnr |
Business registration number and tax ID country and incorporation country match
In this example,siren is valid as both a business registration number and tax identification number and the issuing_country matches the registered_address.country.
Business foreign tax registration status
If a business has tax registration outside its country of incorporation, provide tax registration information for each foreign country.Business Registry
If Bridge is unable to verify the business with an automated registry check, you must provide both:POST|PUT /v0/customers/{customerID}/associated_persons/{id}
Live reference: Create a new associated person
Summary of changes (to be enforced starting June 15th for new customers; required for existing customers by June 26th)
The following fields will be new or newly required for Businesses or Legal Entity Customers, either EEA-incorporated or EEA-resident.| Requirement | New requirement (to be enforced starting June 15th for new customers; June 26th for existing customers) | Current state | Sample code |
|---|---|---|---|
| Complete director list | All associated persons are required to specify whether or not they are a director and provide full name and DOB. | Sending is_director field value is not required. | Link |
| KYC for additional associated members | Full KYC required on: all UBOs; at least two directors if at least two directors exist (otherwise KYC required only on the sole director); all authorized signers. | Full KYC required on all UBOs. | Link |
| Ownership % per UBO | Ownership % for each UBO with 25% or more ownership is required. | Ownership % is not required. | Link |
| Letter of Authority (LOA) | Letter of Authority is required for all authorized signers who are not listed as a director, owner, or control person. | Letter of authority is not required. | Link |
Complete director list
Every associated person is required to have a value for is_director and provide full name and DOB. Code SampleKYC for additional associated members
Full KYC is now required on:- All UBOs
- At least two directors if at least two directors exist (otherwise KYC required only on the sole director)
- All authorized signers
