Moving to Production

Configure production credentials

After successfully integrating and testing the integration in your development environment, you'll need to make a few changes to move to production. This guide outlines the key steps to ensure a smooth transition.

1. Update the CDN Script (iBranch)

If integrating iBranch, replace the development CDN script with the production version:

HTML

<script src="static.golendica.com/v2/lendica.js"></script>

2. Use the Production Partner Name

When initializing iBranch, or in any other API calls where the partner_name variable is used, use your production partner name instead of the development one. For example:

JavaScript

const credentials = {
  partner_name: "partner_name", // Use your production partner name here
  partner_company_uuid: "...",
  company_name: "..."
};

Your production partner name will be provided by Lendica during the onboarding process.

3. Ensure Dynamic Data

Make sure that all data passed to Lendica is dynamically fetched from your production database. This includes:

• partner_company_uuid: Should be the unique identifier for the logged in company in your system
• company_name: The actual name of the company using your platform
• Any other data used in API calls

Example of dynamic data usage:

JavaScript

function initializeIBranch(companyData) {
  const credentials = {
    partner_name: "your_production_partner_name",
    partner_company_uuid: companyData.uuid,
    company_name: companyData.name
  };

  lendica.init(credentials).then(() => {
    lendica.ibranch.render();
    console.log('iBranch initialized successfully');
  }).catch(error => {
    console.error('Error initializing iBranch:', error);
  });
}

// Fetch company data from your backend
fetchCompanyData().then(companyData => {
  initializeIBranch(companyData);
});

4. Update API Endpoints

Ensure that all API endpoints used for backend integration are pointing to your production servers, not development or staging environments.

5. Thorough Testing

Before fully launching in production:

1. Test the integration thoroughly in a staging environment that mirrors your production setup.
2. Perform end-to-end testing of all Lendica features (PayLater, FundNow, etc.) using real company data.
3. Verify that all data being sent to Lendica is accurate and up-to-date.

6. Monitoring and Support

Once in production:

1. Implement logging and monitoring to track iBranch usage and any potential issues.
2. Ensure your support team is prepared to handle any Lendica-related queries from users.
3. Keep communication channels open with Lendica's support team for any questions or concerns.

By following these steps, you'll ensure a smooth transition from development to production for your Lendica integration. If you encounter any issues or have questions during this process, don't hesitate to reach out to Lendica's support team.