bronID’s Distributor subscription empowers organisations to establish hierarchical structures by creating 'on-behalf' accounts. These accounts conveniently allow organisations to divide KYC and KYB submissions across various business units according to their specific organisational logic. This could include different companies, internal departments, or distinct products, depending on the desired segregation within the organisation.
On-behalf accounts cannot see submissions made by other on-behalf accounts; they can only access their own submissions. However, the primary (master) account that creates these on-behalf accounts has complete visibility into all submissions across all on-behalf accounts. For example, if your organisation holds an Australian Financial Services Licence (AFSL) and is regulated under the Australian AML/CTF Act, you might provide authorised representatives with their own on-behalf accounts. These representatives and their employees can perform verifications independently, while your organisation, as the AFSL holder and regulated entity, retains comprehensive oversight of all submissions, ensuring compliance and regulatory accountability.
What Are On-Behalf Accounts?
On-behalf accounts under bronID Distributor subscriptions offer:
- Separate Access: Individual bronID portal and tools.
- Independent Operations: Handle KYC/KYB submissions autonomously.
- User Invitations: Capability to invite users directly to their workspace.
- Customisable Rules and Branding: Set up independent IDV Rules and configure Whitelabel Forms uniquely, allowing distinct branding and customised setups separate from the master account and other on-behalf accounts.
- Ideal Usage: Suited for internal departments, clients, authorised representatives, or affiliates. For example:
- Internal Departments: Compliance, legal, or risk management teams.
- Funds: Separate funds managed by your organisation.
- Subsidiaries or Affiliates: External entities that manage their own customer onboarding.
- Product Lines: Different products or services offered by your organisation, each requiring separate verification processes.
Setting Up an On-Behalf Account
There are two ways to set up an on-behalf account—either via the bronID portal or via the API.
1. Setting Up an On-Behalf Account via Portal
- Access Settings: Click your account icon (top-right), select Settings.
- Navigate: Go to Basic Info → On-behalf users.
- Add User: Click Add User and complete the form:
- Account Email (use organisational emails, e.g., operations@company.com).
- Country, Company Name, Company Number (e.g., ABN, ACN).
- Contact Person details (First Name, Last Name).
- Financial Services/Credit Licence (FCL).
- Regulatory Number (AML/CTF registration).
Learn more and access detailed documentation.
2. Setting Up an On-Behalf Account via API
Use the following API request to programmatically create KYC user accounts:
1const apiEndpoint = 'https://dev.bronid.com/createUser';
2
3const createUserData = {
4 "metadata_version": "4",
5 "metadata_serviceUid": "YOUR_SERVICE_UID",
6 "metadata_secretKey": "YOUR_SECRET_KEY",
7 "fields": {
8 "country": "AUS",
9 "email": "operations@company.com",
10 "companyName": "ABC Pty Ltd",
11 "companyNumber": "123456789",
12 "firstName": "Jane",
13 "lastName": "Doe",
14 "FCL": "123456789",
15 "regulatoryNumber": "123456789"
16 }
17}
Learn more and access detailed documentation.
Submitting Verification via On-Behalf Accounts
The KYC API, Whitelabel Forms API, and Standalone PEPs and Sanctions Screening via on-behalf accounts (not part of KYC/KYB) APIs all have the same format as standard API but include one extra parameter (metadata_onBehalf), which is the UserId value of your on-behalf customer. Verifications submitted with this parameter will also be visible to the on-behalf accounts through their portal accounts.
1. Using KYC API
Perform verification submissions by including the metadata_onBehalf parameter, linking submissions to the respective on-behalf accounts:
1const apiEndpoint = 'https://dev.bronid.com/verify';
2
3const kycData = {
4 "metadata_version": "4",
5 "metadata_serviceUid": "YOUR_SERVICE_UID",
6 "metadata_secretKey": "YOUR_SECRET_KEY",
7 "metadata_userId": "yourUniqueUserId",
8 "metadata_onBehalf": "ON_BEHALF_USER_ID",
9 "metadata_tags": ["internal", "high-priority"],
10 "type": "individual",
11 "fields": {
12 "country": "AUS",
13 "firstName": "Jane",
14 "lastName": "Doe",
15 "gender": "female",
16 "dateOfBirth": "20/10/1980",
17 "address": "95 Lennox Street, CASINO, NSW 2470",
18 "email": "jane.doe@example.com"
19 }
20}
Learn more and access detailed documentation.
2. Using Whitelabel Forms
Generate KYC forms for your customers via the Whitelabel Forms API by including the metadata_onBehalf parameter:
1const apiEndpoint = 'https://dev.bronid.com/idform';
2
3const kycData = {
4 "metadata_serviceUid": "YOUR_SERVICE_UID",
5 "metadata_secretKey": "YOUR_SECRET_KEY",
6 "metadata_version": "4",
7 "metadata_userId": "yourUniqueUserId",
8 "metadata_onBehalf": "ON_BEHALF_USER_ID",
9 "metadata_tags": ["tag1", "tag2"],
10 "bronLink_dataAccessType": "idForm",
11 "type": "individual",
12 "fields": {
13 "country": "AUS",
14 "firstName": "Jane",
15 "middleName": "ok",
16 "lastName": "Citizen",
17 "gender": "female",
18 "dateOfBirth": "20/10/1980",
19 "address": "125 york st",
20 "email": "email@gmail.com"
21 }
22}
Learn more and access detailed documentation.
Standalone PEPs and Sanctions Screening via on-behalf accounts (not as part of a KYC/KYB)
Run standalone PEPs and Sanctions screening on behalf of your customers:
1const apiEndpoint = 'https://dev.bronid.com/screen';
2
3const screeningData = {
4 "metadata_version": "4",
5 "metadata_serviceUid": "YOUR_SERVICE_UID",
6 "metadata_secretKey": "YOUR_SECRET_KEY",
7 "metadata_onBehalf": "ON_BEHALF_USER_ID",
8 "metadata_tags": ["tag1", "tag2"],
9 "type": "individual",
10 "fields": {
11 "firstName": "John",
12 "lastName": "Person"
13 }
14}
Learn more and access detailed documentation.
Using Tags in bronID
In bronID, tags function as markers to effectively organise your KYC and KYB submissions. Tags can represent different business elements like products, funds, departments, or organisational categories. Nested tags allow for intricate classification. For instance, under a primary 'Products' tag, you might have nested tags for 'Remittance', 'Investment', and 'Corporate Trustee' or under a primary 'Funds' tag, you might have different nested funds e.g. 'ABC Defensive Fund', 'FFC Credit Fund' and 'QQ Wholesale Fund'.
Tags help with:
- Filtering and searching verification histories by specific customers/products/departments
- Billing organisation by customer/product/department
- Structuring verifications according to business requirements
Creating Tags
Tags can be created via the bronID Portal or programatically via an API submission.
Portal:
- Navigate to Settings > Tags.
- Click 'Create new tag', enter details, and save.
API:
- Submit a KYC/KYB request with new tags; they are automatically created.
Editing Tags
- Navigate to Settings > Tags.
- Click the menu icon next to a tag and select 'Edit' to modify details.
Nested Tags
Nested tags can be created via the bronID Portal or API.
Portal:
- In Settings > Tags, select 'Create nested tag' from the parent tag's menu.
API:
- Append nested tag names using '>>>' between parent and child tags (e.g., 'Products >>> Remittance').
Deleting Tags
Tags and nested tags can only be deleted via the bronID Portal. Deletion is permanent and affects all associated submissions.
Editing Tags on Verifications
You can modify tags on individual verifications via the history page in the bronID Portal.
For detailed guidance, see our Help Center article.
Benefits of Distributor Integration
Integrating bronID Distributor subscriptions with on-behalf accounts streamlines verification workflows, offers granular control, and improves compliance and reporting efficiency. If you would like to learn more to access the bronID Distributor subscription or need integration assistance you can book a free demo consultation.
