KYC verification of public companies (USA)

Use this API call to perform KYC verification of public companies.

Parameters

NameTypeDescription
country
(required)
stringUSA
name
(required)
string
entityNumber
(required)
string
exchangeListedOn
(required)
stringdomesticExchange / internationalExchange / unlisted
incorporatedState
(required)
stringUSA states
publicCompanyType
stringCorporationIncorporated / FederallyIncorporated
ticker
string

Parameters only when verifying from Australia

Include these parameters only when verifying the company as a reporting entity in Australia. If your business is not a reporting entity for AML/CTF purposes in Australia, and the verification is not required for compliance with Australian AML/CTF laws and regulations, you may omit these fields entirely.

NameTypeDescription
ARBN
stringThe Australian Registered Body Number (ARBN) is a unique, nine-digit identifier issued by the Australian Securities and Investments Commission (ASIC) to foreign companies or registrable Australian bodies that operate in Australia. It is used to identify these entities, which may not require an Australian Company Number (ACN) but still need to be registered to conduct business legally within the country.
registeredInAusOfficeAddress
stringaddress
principalPlaceInAusAddress
stringaddress

Note on submitting stakeholders

For each company, the same individual can hold multiple stakeholder roles. For example, in a company, a person can be both a director and a shareholder. We strongly recommend submitting an individual in only one stakeholder role. If there is a specific role that must be included (i.e., is required), submit the individual in that role to avoid running multiple KYCs (identity verifications) for the same person within a single KYB, which would be redundant. This is a cost-effective approach. For instance, if John ok Citizen is both a director and shareholder of MY COMPANY, submit John ok Citizen as either a director or a shareholder, but not both. This will prevent duplicate charges for verification. Even if the individual is submitted under one role, bronID will map any additional relevant roles in the background and include them in the documentation.

Tags

You can add tags to your verification requests to help you organise your verifications by using the metadata_tags parameter. Read more about tags here.

Runnable example

const apiEndpoint = 'https://dev.bronid.com/verify'; // request body const kycData = { "metadata_version": "4", "metadata_serviceUid": "XL7ULiU6B4QE9Y2iWFZnhtMDKFN2", "metadata_secretKey": "api_sec_NJAtNcRtUrPlf7xYDrMNP9URI-ZfN314", "metadata_userId": "yourUniqueUserId", "metadata_tags": ["product1", "client1"], "type": "publicCompany", "fields": { "country": "USA", "name": "entity name", "entityNumber": "123456", "publicCompanyType": "FederallyIncorporated", "exchangeListedOn": "domesticExchange", "incorporatedState": "CA", "ticker": "TCK" }, }; console.log('Running request...') // submit the KYC data to the bronID API try { const response = await fetch(apiEndpoint, { method: 'POST', headers: { 'Content-Type': 'application/json', }, body: JSON.stringify(kycData), }); if (!response.ok) { const errorData = await response.json(); console.log('error! click the results to expand them'); console.log(JSON.stringify(errorData, null, 2)); } else { const bronIdResult = await response.json(); const printResult = 'bronId API response: ' + JSON.stringify(bronIdResult, null, 2); console.log(printResult); } } catch (error) { console.log('Fetch error: ', error); } // Click “▶ run” to try this code live and run your first KYC.