Intro to Lean

Lean provides payments and financial data infrastructure for the Middle East.

With Lean, businesses can move money and understand their customers without having to build and maintain integrations with individual financial institutions and payment providers.

Lean's platform is built around two core capabilities:

Payments — collect payments, send payouts and manage refunds.

Data — use permissioned financial insights and account verification to support onboarding, financial decision-making and customer experiences.

These guides cover Lean's UAE integration.


What can you build with Lean?

Payments

Accept bank payments from your customers and manage outgoing payments from your business.

Use Lean to build:

  • One-time payments — collect a payment when a customer makes a purchase, deposits funds or completes another transaction.
  • Account on File payments — establish a customer's consent to initiate future payments within agreed limits.
  • Payouts — send money from your connected business bank account to a beneficiary.
  • Refunds — return all or part of a reconciled payment to the customer's original account.
  • Payment reconciliation — track incoming funds and match them to payments initiated through Lean.

Refunds use Lean's Payouts capability and require Reconciliation to identify the original payment.

Data and verification

Use financial insights and account verification to better understand and verify your customers.

For Insights, customers connect their bank accounts and provide permission for Lean to retrieve and analyse the financial information needed for your use case.

Use Lean to support experiences such as:

  • Account verification — verify a customer's ownership of a bank account.
  • Income insights — understand income, salary and income reliability.
  • Financial insights — understand spending, financial commitments and cash flow.
  • Onboarding and verification — use account ownership checks to support customer onboarding.
  • Lending and risk — use financial insights to inform affordability, underwriting and credit decisions.

The capabilities available depend on the product, supported financial institution and permissions provided by the customer.


How Lean works

Lean sits between your application and the financial infrastructure required to deliver the experience. Your application interacts with Lean in three main ways.

1. APIs

Your backend communicates with Lean's APIs to create and manage resources.

For Payments, your server can create a Payment Intent for a one-time payment or an Account on File consent for future payments.

For Data, APIs allow your application to retrieve financial insights from a customer's connected accounts. Account Verification uses a separate API to check the account details you provide.

2. Customer authentication

Some actions require the customer to authenticate with their bank or provide permission.

Lean's Link SDK connects your application to this journey. Use it to let customers connect a bank, authorise a payment or establish consent for future payments.

Your integration also provides the relevant consent-management experience so customers can review and manage their permissions.

3. Webhooks

Many interactions with financial institutions happen asynchronously. Lean uses webhooks to notify your backend when a connection, consent, payment or other resource changes.

Use API responses and webhooks to track the outcome. A customer's return from their bank does not, by itself, confirm that a payment succeeded or that insights are ready.


Understand the core concepts

Customers

A Customer represents the person using your application.

Create a Customer in Lean and associate it with your own user reference, app_user_id. Lean returns a customer_id that you use in subsequent requests and customer journeys.

Payment Intents and payments

A Payment Intent describes a one-time payment you want a customer to make, including its amount, currency and destination.

A Payment represents the payment initiated through Lean. Track its status separately from the customer's authentication journey.

Account on File consents

An Account on File consent records a customer's permission for future payments from a selected bank account, subject to agreed limits and an expiry.

Creating a consent does not itself move money. Once authorised, it can be used to initiate payments within its terms.

Connections and Entities

For Insights, a customer connects their bank and grants the required permissions.

Lean represents the connection as an Entity. Use its entity_id to request supported insights and manage the connection.

Establishing the connection and preparing the information for insights are separate steps. Your integration needs to handle both.

Payment and payout destinations

A Payment Destination identifies the account that receives a customer's payment to you.

A Payout Destination identifies a beneficiary you want to pay from your connected business bank account.

These resources serve different payment flows.


Build your first integration

Lean provides a Sandbox environment where you can build and test your integration before going live.

A typical integration follows four steps:

1. Set up your application

Configure your application in the Lean Dashboard and obtain the credentials required for your integration.

2. Make your first API request

Authenticate your backend and create the resources required for your use case.

3. Complete the customer journey

Where authentication or permission is required, use the Link SDK to guide the customer through the relevant bank journey.

4. Handle the outcome

Use API responses and webhooks to keep your application synchronised with Lean. Test successful journeys, failures and delayed outcomes before moving to production.


Did this page help you?