Skip to main content

LendPro APIs for embedded financing

LendPro APIs let platforms and retailers embed multi-lender financing, drawing on a network of 18+ lenders and 25+ lending programs, through three APIs: Launch, POS Sync and Settlement. Instead of building a separate integration for every lender, a developer integrates with LendPro, and the lender lineup and routing setting that LendPro configures for each location handle the rest.

On this page
  1. What are the three LendPro APIs?
  2. How does a typical integration flow?
  3. Why use the hosted application?
  4. Where can you use the Launch link?
  5. What mistakes do developers make?
  6. How do you get access?
  7. Before you build
  8. Questions

Full API documentation is provided to integration partners. LendPro is not a lender. Lenders make all credit decisions and set all terms.

Key takeaways

  • LendPro offers three APIs: Launch starts a hosted application and returns a secure link, POS Sync sends results back, and Settlement covers financed sales.
  • The shopper enters personal and credit details on the hosted LendPro application, so the integrating system does not collect them.
  • Lender lineup and routing setting are configured by LendPro for each location rather than set in the integrating code.
  • Full API documentation is provided to integration partners, and other integration needs are discussed with LendPro during an integration call.

What are the three LendPro APIs?

API What it does
Launch Starts a hosted LendPro application and returns a secure link
POS Sync Sends results back to the merchant system
Settlement Settlement for financed sales, described in the partner documentation

How does a typical integration flow?

  1. Your system calls the Launch API.
  2. LendPro returns a secure link. Open it in a browser, on a kiosk or tablet, or send it by text or QR code.
  3. The shopper completes the hosted application. See If You Pre-Qualify, No Credit Needed when the store offers it, or Lookup Application. Where the provider supports pre-qualification, it uses a soft pull and won't affect credit scores. A lender may run a hard inquiry if the shopper accepts an offer.
  4. Lenders review in the routing setting configured for that location: several at once by default, or the traditional waterfall setting.
  5. The shopper selects an offer and completes that provider's application.
  6. POS Sync sends results back to your system so the associate can finish the sale.
  7. Settlement follows when the merchant finalizes the sale.

Why use the hosted application?

The shopper enters personal and credit details on the hosted LendPro application, so your code does not need to collect them. Use the returned link wherever the shopper is: a product page, a POS screen, a kiosk or a text message.

See this on your own lenders

We will walk through your lenders, tiers and entry points in a live demo.

Request a Demo

What mistakes do developers make?

  • Launching only at checkout. Shoppers decide earlier. Put the link on product pages too.
  • Skipping POS Sync. Associates end up retyping results.
  • Collecting credit data in your own forms. Let the hosted application handle it.
  • Hard-coding lender logic. Keep lender logic out of your code. LendPro uses a financing flow configured for each location based on the lenders assigned to that location and the requirements of those programs. Contact LendPro to review configuration changes.
  • Hiding disclosures. Lease-to-own is a rental-purchase agreement, not a loan. Total cost is higher than the cash price.

How do you get access?

Talk to LendPro about your platform or store system. Full API documentation is provided to integration partners. LendPro's go-live SLA is 10 business days. Timing depends on lender activation and integration scope, and custom integrations take longer. LendPro confirms the start date and prerequisites during onboarding.

Additional integration options may be available for specific needs. Discuss your workflow, required data, and implementation requirements with LendPro during an integration call.

Review your lender configuration on a live call

Bring your current lenders. We will show how LendPro would be configured for your stores.

Request a Demo

Before you build

  • Check existing integrations. STORIS retailers use the embedded LendPro 2.0 integration, and 1stMILE shops reach LendPro's multi-lender platform through 1stMILE; see all integrations.
  • Consider white label if your network wants to offer financing under its own name; see white-label financing.
  • Plan the shopper journey by putting the Launch link before checkout, as described in embedded pre-qualification.
  • Review security to see how LendPro protects data.

Frequently asked questions

Does LendPro have an API?

Yes. LendPro offers three APIs: Launch, POS Sync and Settlement.

What does the Launch API return?

A secure link to the hosted LendPro application. Full API documentation is provided to integration partners.

Do I handle shopper credit data?

No. The shopper enters data on the hosted LendPro application, and the data is encrypted in transit. Application data is shared with the lenders reviewing the application and with service providers that process it under LendPro's privacy notice.

Where is the full API documentation?

Full API documentation is provided to integration partners. Book a call to start.

How long does an integration take?

LendPro's go-live SLA is 10 business days. Timing depends on lender activation and integration scope, and LendPro confirms the start date during onboarding.

Can I control lender order through the API?

Lender order is part of the location configuration that LendPro manages. The retailer chooses its lenders and routing setting, and changes are requested through LendPro.

See LendPro with your own lenders

One application to the lenders configured for your stores, from a network of 18+ lenders and 25+ lending programs.

Request a Demo
One application, configured lendersRequest a Demo