🇮🇹 Italy eKYB
Earlier in our docs is an overview of our Know Your Business here. Now, this page is focused specifically on eKYB in the Italy (IT). eKYB in IT leverages the government sources of truth to validate the legitimacy of businesses, including their taxID (either Vat No or Reg No), business name, business address, along with UBOs.
Integration
User input flow
Module Configuration
Module configuration gives various options to specify different KYB criteria you would like to check (eg. Business name, Business Address, and Business taxID).
Direct API Approach
All module configurations and user data can be forwarded directly in the request for performing an KYB search. This will override existing configuration and data collected about the user.
API Authentication
All endpoints require authentication headers to be specified as stated in Incode API Documentation
POST /omni/externalVerification/ekyb
This endpoint performs an KYB check for the business specified. Note: Endpoint can have empty body {} and in that case information will be pulled from module configuration and session details.
- plugins: must be ["ekyb"]: (mandatory)
- businessName:: (mandatory) String. Name of the business.
- street: (optional) String. Street name of the business.
- houseNo: (optional) String. Building or house number on the street.
- addressLine2: (optional) String. Address line 2 of the business. (eg. apartment or unit number)
- city: (optional) String. City of the business of the business address.
- state: (optional) String. State of the business of the business address
- postalCode: (optional) String. postalCode formatted based on per-country postalCode basis. (IT has 5 digits)
- country: (mandatory) String. Two letter Alpha-2 country code. (Must be IT)
- uboNames: (optional) String. Full legal name(s) of Unique Beneficial owners to check against list of legal business associations
- directors: (optional) String. Full legal name(s) of directors to check against list of legal business associations
- taxId: (mandatory) String. Tax ID of the business (VatNo or RegNo)
Business Tax ID in IT
Business Tax ID supports either CCIAA/NREA (companies id in chamber of commerce), TAX_CODE, VAT_NUMBER, CS_COMPANY_ID.
Business Tax ID Formats:
- CCIAA/NREA: CCIAA represents the province code where company is registered (2 char); NREA is a progressive number which identifies a single company (6 integers).
- TAX_CODE: 11 integers or 16 char (in case of sole traders) mixed letters and integers.
- VAT_NUMBER : 11 integers.
- CS_COMPANY_ID: ‘IT’ + 8 integers.
REQUEST FORMAT EXAMPLE
{
"plugins" : ["ekyb"], //required field
"businessName" : "LUXOTTICA GROUP SPA", //required field
"street" : "PLE LUIGI CADORNA",
"houseNo" : "3",
"addressLine2" : "",
"city" : "MILAN",
"state" : "",
"postalCode" : "20123",
"country" : "IT", //required field
"taxId" : "XXXXXXXXX", //required field
"uboNames" : ["Stella Smith", "Sarah Smith" ],
"directors" : ["Andrew Martin", "Mike Martin" ]
}
Response
All module configurations and user data can be forwarded directly in the request for performing an eKYB search. This will override existing configuration and data collected about the user.
API Authentication
All endpoints require authentication headers to be specified as stated in Incode API Documentation
RESPONSE EXAMPLE
"kyb": [
{
"key": "name",
"sub_label": "Verified"
},
{
"key": "tin",
"sub_label": "Verified",
"reasonCodes": [
"VATNO"
]
},
{
"key": "address_verification",
"sub_label": "Verified"
},
{
"key": "cityMatch",
"sub_label": "Verified"
},
{
"key": "postalCodeMatch",
"sub_label": "Verified"
},
{
"key": "registrationStatus",
"sub_label": "Active"
},
{
"key": "ubo_name_match",
"sub_label": "Unverified",
"uboName_input": "Stella Smith"
},
{
"key": "ubo_name_match",
"sub_label": "Unverified",
"uboName_input": "Sarah Smith"
},
{
"key": "directors_name_match",
"sub_label": "Unverified",
"directorsName_input": "Andrew Martin"
},
{
"key": "directors_name_match",
"sub_label": "Unverified",
"directorsName_input": "Mike Martinr"
}
}
Please refer to error response to see conventional HTTP response codes to indicate the success or failure of an API request.
Custom 400 error messages if businessName, taxId, or country is “ “ or null:
message: businessName, taxId, and country are minimum required fields.
BR API Key | Status | Definition |
---|---|---|
name | Verified, Approximate Match, Unverified | Submitted business name is verified, approximate match, or unverified against the business name associated with the business Tax ID in the government database. |
tin | Verified, Unverified | Submitted Tax ID is found or not found in the government database. |
address_verification | Verified, Approximate Match, Unverified | Submitted address is verified, approximate match, or unverified against the address associated with the business Tax ID in the government database. |
cityMatch | Verified, Approximate Match, Unverified | Submitted city is verified, approximate match, or unverified against the address associated with the business taxID in the government database. |
postalCodeMatch | Verified, Unverified | Submitted postal code is verified, approximate match, or unverified against the address associated with the business taxID in the government database. |
registrationStatus | Active, Inactive | Submitted business is active or inactive |
ubo_name_match | Verified, Approximate Match, Unverified | Submitted UBO is an exact match against the UBO associated with the business Tax ID in the government database. In situations where user has submitted multiple ubo names to be verified against the government source of truth, you will see additional fields called ubo_name_match. You can distinguish ubo_name_match when looking at uboName_input |
directors_name_match | Verified, Approximate Match, Unverified | Submitted Directors is an exact match against the DIrectors associated with the business Tax ID in the government database. In situations where user has submitted multiple ubo names to be verified against the government source of truth, you will see additional fields called directors_name_match. You can distinguish directors_name_match when looking at directorsName_input |
Learning more about Approximate Match : Approximate Match is generated through Incode's proprietary fuzzy matching algorithm. If approximate match is returned, the algorithm has identified a similar match with the string submitted in relation to the string stored in the government source of truth for a particular field. Approximate Match is returned when exact matches are not possible due to misspellings, typographical errors, or slight variations in input data.
Single Session Dashboard Results
They are available on Single Session view under Business tab
Updated 29 days ago