🇺🇸 US eKYB Advanced
Earlier in our docs is an overview of our Know Your Business here. Now, this page is focused specifically on eKYB Advanced in US. eKYB in US leverages the government sources of truth to validate the legitimacy of businesses, including their taxID (9 digit EIN), 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. in US 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. (US has 5 digit postal codes)
- country: (mandatory) String. Two letter Alpha-2 country code. (Must be US)
- taxId: (mandatory) String. Tax ID of the business (9 digit EIN number assigned by the IRS)
- uboNames: (optional) String. Full legal name(s) of Unique Beneficial owners to check against list of legal business associations
REQUEST FORMAT EXAMPLE
{
"plugins" : ["ekyb"], //required field
"businessName" : "Delta International Inc.", //required field
"street" : "SW 72nd Ave",
"houseNo" : "4856",
"addressLine2" : "",
"city" : "MIAMI",
"state" : "FL",
"postalCode" : "33155",
"country" : "US", //required field
"taxId" : "XXXXXXXXX", //required field
"uboNames" : ["Jose A Santos"]
}
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",
"status": "success",
"sub_label": "Verified",
"message": "Match identified to the submitted Business Name"
},
{
"key": "tin",
"status": "success",
"sub_label": "Found",
"message": "The IRS has a record for the submitted TIN and Business Name combination"
},
{
"key": "address_verification",
"status": "success",
"sub_label": "Verified",
"message": "Match identified to the submitted Office Address"
},
{
"key": "ubo_name_match",
"status": "success",
"sub_label": "Verified"
},
]
}
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 EIN in the government database. |
tin | Verified, Unverified | Submitted Tax ID (EIN) is verified or not verified in the government database. |
address_verification | Verified, Approximate Match, Unverified | Submitted address is verified, approximate match, or unverified against the address associated with the EIN in the government database. |
ubo_name_match | Verified, Approximate Match, Unverified | Submitted UBO is an exact match against the UBO associated with the Business taxID (EIN) 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 |
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
Differences between Advanced and Advanced+ for US eKYB
The main difference is around the responses you will get from both requests. Advanced does not include Address Deliverability, Address Property Type, or the full list of UBOs associated to the business. Only Advanced+ will include this information
Updated 2 months ago