iBranch post data integration usage guide to enable full functionalities.


Make sure you have completed these steps:

Enable full functionalities for iBranch

Once the steps from the previous section are complete, the credentials to initialize the iBranch will be ready.

partner_namestringThe name of the partner service - you will receive this from Lendica during onboarding'partner_dev', 'partner'
partner_company_uuidstringThe unique ID of the company in the partner system'uuid'
company_namestringThe name of the company'Example Inc.'
partner_tokenstringAn API key that can be used to retrieve company and invoice data'access_token'


To initialize iBranch with credentials, use the following code:

// Partner and company credentials
const credentials = {
	partner_name: 'partner_dev', // use 'partner' when moving to production
	partner_company_uuid: '538b4643-a4fc-4b55-84c1-83448451fff9', // unique id for the company in your system
	company_name: 'example inc',
	partner_token: '12345' // if universal token is not available, this is the individual token for each company

// Init with credentials to use full funcionalities of iBranch
lendica.init(credentials).then(() => {

In this code, the credentials object contains the necessary information for initializing iBranch with full functionalities.

The lendica.init(credentials) function initializes iBranch with the provided credentials.

The lendica.ibranch.render() function renders the iBranch interface with all features enabled.

User Access Control

If you have different user access types in your client base, and you want to allow only certain admin users to activate and use Lendica products, you can choose to initialize with or without credentials to trigger different modes.

// Init with credentials to trigger admin access with full functionalities
lendica.init(credentials).then(() => {

// Init without credentials to trigger Betalist mode, where users can express their interests
// Refer to the Betalist API above
lendica.init().then(() => {