API Reference

Product Flow

Lendica Backend Integration Guide

This document provides an overview of integrating your platform with Lendica using a backend-only integration. It outlines the integration flow, API endpoints, data models, configuration options, and best practices to ensure a seamless and scalable implementation.

Table of Contents

Introduction

Lendica provides two core financing products:

  • PayLater: Allows companies to finance their accounts payable, providing flexibility to pay vendors over time.
  • FundNow: Enables companies to finance their accounts receivable, providing immediate access to cash from outstanding invoices.

This guide is intended for partners who wish to integrate with Lendica's products through a backend integration. The integration enables partners to offer financing options to their customers seamlessly within their platform.

Terminology

TermDefinition
PartnerYour platform integrating with Lendica.
CompanyYour customer who will be using Lendica's financing via your platform.
VendorThe supplier or entity to whom the Company owes money (for PayLater).
CustomerThe entity that owes money to the Company (for FundNow).
PayLaterA Lendica product that allows companies to pay vendors later by financing their bills.
FundNowA Lendica product that allows companies to receive immediate funds on outstanding invoices.
Partner NameThe name for your platform in Lendica's system.
Partner Company UUIDThe unique identifier for your customers within your platform.

Integration Overview

The backend integration with Lendica involves the following key components:

  • Application Submission: Collecting and submitting your customer's information to Lendica for underwriting.
  • Approval Retrieval: Fetching approval statuses and credit details for your customers.
  • Transaction Submission: Submitting bills (PayLater) or invoices (FundNow) for financing.

By integrating with Lendica's products, you can offer your customers:

  • Extended payment terms and improved cash flow management (PayLater)
  • Immediate access to funds from accounts receivable (FundNow)

Integration Flow

The integration process consists of three main steps:

  1. Company Application Submission
  2. Fetching Approval Details
  3. Transaction Submission for Financing

1. Company Application Submission

📘

View the Submit Application API documentation here:

Submit Application

When a new customer (Company) is onboarded to your platform, you need to submit their application details to Lendica for underwriting.

  • Purpose: To onboard the Company and apply for an Approval (credit line) in Lendica's system.
  • API Endpoint: /submit/application
  • Data Required: Application details including company and contact information.

Flow:

  1. Data Collection: Collect the necessary information from your customer during onboarding or application.
  2. API Request: Send a POST request to Lendica's /submit/application endpoint with the application data.
  3. Underwriting Process: Lendica processes the application and performs underwriting to assess creditworthiness.
  4. Response Handling: Lendica responds with the ID of the created Company.

☁️

Submitting Documents:

To submit documents along with the application, first submit the Application details. Upon success, you can submit files using the Submit Document API route

2. Fetching Approval Details

📘

View the Approval Status API documentation here:

GET Approvals

After the underwriting process, you need to retrieve the approval status and credit details for your customer.

  • Purpose: To determine financing eligibility and available credit limits.
  • API Endpoint: /partner/status/approvals (from Lendica's Status API)
  • Data Required: partner_company_uuid to identify the customer.

Flow:

  1. API Request: Send a GET request to Lendica's /partner/status/approvals endpoint with the partner_company_uuid.
  2. Data Retrieval: Lendica responds with the approval details.
  3. Integration Logic: Use this information within your platform to enable or disable financing options, display credit limits, etc.

3. Transaction Submission for Financing

Based on your product integration, submit either bills for PayLater or invoices for FundNow:

PayLater Bill Submission

📘

Create PayLater deal

  • API Endpoint: /submit/paylater/bill
  • Data Required: Bill details, Company information, and Vendor information

FundNow Invoice Submission

📘

Create FundNow deal

  • API Endpoint: /submit/fundnow/invoice
  • Data Required: Invoice details, Company information, and Customer information

Flow:

  1. Data Preparation: Gather the transaction details from your platform.
  2. API Request: Send a POST request to the appropriate endpoint with the transaction data.
  3. Financing Process: Lendica processes the request and evaluates the financing terms.
  4. Response Handling: Lendica provides a response with deal confirmation.
  5. Customer Interaction: Display confirmation within your platform.

Configuration Options

When submitting transactions for financing, you can configure how funds are disbursed and collected using the following flags in your request:

  • pay_partner_platform:

    • PayLater Purpose: Determines whether Lendica should disburse funds to your platform's bank account instead of the vendor's bank account.
    • FundNow Purpose: Determines whether Lendica should disburse funds to your platform's bank account instead of the company's bank account.
    • Usage:
      • Set to true if you want funds to be disbursed to your platform.
      • Set to false for direct disbursement to the vendor (PayLater) or company (FundNow).

  • collect_from_partner_platform:

    • Purpose: Determines whether Lendica should collect repayments from your platform's bank account instead of from the customer's bank account.
    • Usage:
      • Set to true if you will handle collecting repayments from the customer.
      • Set to false if Lendica should collect repayments directly from the customer.

PayLater-Specific Options:

  • partner_is_vendor:
    • Purpose: Indicates whether your platform is also the vendor of the bill.
    • Usage:
      • Set to true if your platform is the vendor (vendor details not required).
      • Set to false if the vendor is a separate entity (include vendor details).

Example Scenarios:

PayLater Scenarios:

  1. Platform as vendor, with direct customer repayment:

    • partner_is_vendor: true
    • pay_partner_platform: true
    • collect_from_partner_platform: false

  2. Platform handling all transactions:

    • partner_is_vendor: false
    • pay_partner_platform: true
    • collect_from_partner_platform: true

FundNow Scenarios:

  1. Direct disbursement to company, platform handles collections:

    • pay_partner_platform: false
    • collect_from_partner_platform: true

  2. Platform handles all transactions:

    • pay_partner_platform: true
    • collect_from_partner_platform: true