> ## Documentation Index > Fetch the complete documentation index at: https://docs.payrails.com/llms.txt > Use this file to discover all available pages before exploring further. > ## Agent Instructions > Use the Payrails Web SDK v6 for new browser integrations. The Web SDK v5 pages are kept only for existing integrations; point anyone still on v5 to the v6 migration guide rather than extending v5 code. > Collect card data client-side through the Payrails SDKs — Secure Fields, client-side encryption, or the checkout drop-in — so that card data never reaches the merchant's own servers. Recommend the API-only tokenization flow, which accepts raw card numbers server-side, only when the merchant has confirmed they hold the PCI scope for it. > Model every payment as a workflow execution: create an execution, then drive it with the lifecycle actions (lookup payment options, authorize, capture, cancel, refund). Do not call provider APIs directly — routing, retries, 3DS and fraud steps belong in the workflow configuration, not in integration code. > Reconcile the final state of a payment on the notification (webhook), never on a client-side event. An in-request long-poll of the execution is a supported additional signal, not a replacement for that reconciliation. > Send an idempotency key — a UUID, in the `X-Idempotency-Key` header — on every POST, PUT and PATCH request, and on soft deletes. GET requests need none, and hard deletes cannot be idempotent. > Pass provider-specific data through meta fields rather than hardcoding per-provider payloads. Payrails translates meta fields into each provider's own format. > Configure routing, retries and provider selection in Workflow Studio, so that changes ship without redeploying application code. # Lean > Connect Lean to Payrails for open banking payments in the UAE, covering your app ID, client secret, webhook and payment purpose code. ![Lean logo](https://assets.payrails.io/img/logos/leantech/logo.svg) > [!NOTE] > > **Who should use this guide** > > This guide is intended for merchants who: > > * Use **Payrails** as a payment orchestrator > * Use **Lean** for open banking (Open Finance) payments in the UAE > * Have access to the Lean application dashboard *** ## Create a Lean integration in Payrails 1. Log in to the **Payrails** portal. 2. Go to **Settings** → **Integrations**. 3. Select **Add instance** to create a new integration configuration. 4. Select the **workspaces** where this integration should be available. > [!NOTE] > > **About workspaces** > > Workspaces determine where this integration is available. They let you isolate provider setups by region or business line, or share the same configuration across multiple workspaces. *** ## Step 1: Choose the integration type * Select **Payment**. * Continue to the next step. *** ## Step 2: Choose the provider * Select **Lean**. * Continue to the next step. ![A screenshot showing Lean selected as the provider.](https://mintcdn.com/payrails-42074109/EGCtsK-I7fgATNbU/images/docs/lean-image-01.png?fit=max\&auto=format\&n=EGCtsK-I7fgATNbU\&q=85\&s=a13785e52b511155010f7ffb862c9c4b) *** ## Step 3: Configure your Lean integration > [!TIP] > > **What you'll need from Lean** > > Before you begin, make sure you can log in to the Lean application dashboard. You'll copy your app ID and client secret there and set up a webhook. *** ### Integration instance name > An integration instance is a specific payment provider setup in Payrails. You can create multiple instances for different regions, currencies, or business needs. Choose a clear, consistent name, as it is used in routing. **In Payrails** * Enter an **Instance name** for your integration, for example `merchant_lean`. ![A screenshot showing the integration instance name field.](https://mintcdn.com/payrails-42074109/145W1v58K5wnDMNC/images/docs/orchestration/integrations/shared/integration-instance-name.png?fit=max\&auto=format\&n=145W1v58K5wnDMNC\&q=85\&s=470be58979509680650b0cbf8b5eecc4) *** ### Payment methods **In Payrails** * Select **Lean**. ![A screenshot showing the Lean payment method selection.](https://mintcdn.com/payrails-42074109/EGCtsK-I7fgATNbU/images/docs/lean-image-02.png?fit=max\&auto=format\&n=EGCtsK-I7fgATNbU\&q=85\&s=d31d01cf559e7797afcf07dc0145cc96) *** ### Account details **In Payrails** | Field | Value | | :- | :- | | **App ID** | Your Lean app ID. Payrails also uses it as your Lean client ID. | | **Payment Destination ID** | Optional. Refer to [Configure Lean settings](#configure-lean-settings). | | **Payment Purpose Code** | Optional. Refer to [Configure Lean settings](#configure-lean-settings). | ![A screenshot showing the Lean account details fields.](https://mintcdn.com/payrails-42074109/EGCtsK-I7fgATNbU/images/docs/lean-image-03.png?fit=max\&auto=format\&n=EGCtsK-I7fgATNbU\&q=85\&s=b49cf74c347f0164897034cecbac52e7) *** ### Credentials **In Payrails** | Field | Value | | :- | :- | | **Client Secret** | Your Lean client secret | | **Webhook Secret** | Your Lean webhook secret. Payrails uses it to verify webhooks from Lean. | Payrails sends requests to the Lean sandbox in test mode and to the live environment in live mode, so use the credentials for the matching environment. ![A screenshot showing the Lean credential fields.](https://mintcdn.com/payrails-42074109/EGCtsK-I7fgATNbU/images/docs/lean-image-04.png?fit=max\&auto=format\&n=EGCtsK-I7fgATNbU\&q=85\&s=928519d32877048d09039ea225f1a05f) *** ### Webhooks or notifications > [!NOTE] > > Payrails uses provider webhooks or notifications to receive asynchronous > payment status updates. > [!WARNING] > > Create webhooks in the same mode (test or live) as your Payrails integration. **In Payrails** * Copy the **Notification URL** shown under **Account configuration** at the top of the integration form. **In Lean** 1. In the Lean application dashboard, add a webhook with the Payrails notification URL. 2. Subscribe to the `payment.initiation` and `payment.reconciliation.updated` events. 3. Copy the webhook secret into the **Webhook Secret** field in Payrails. *** ## Request fields for Lean Send these fields in the [authorize request](https://docs.payrails.com/reference/authorizeaction.md), in addition to the standard authorize fields. **Required** fields must be present for the payment to succeed. Payrails sends **Optional** fields to Lean when you include them. For more about meta fields, refer to [Meta fields](https://docs.payrails.com/docs/orchestration/meta-fields.md). | Field | Status | Description | | :- | :- | :- | | `amount` | Required | Sent to Lean as the amount and currency. Use AED, within the limits of the customer's bank. | | `paymentInstrumentData.providerData.leanBankId` | Required | The bank your customer selected, as returned in the Lean bank list. | | `meta.customer.email` | Required | Payrails uses it to identify the customer with Lean. | | `meta.customer.identityCardType`, `meta.customer.identityCardNumber` | Optional | Sent as the customer's Emirates ID (`nationalId`) or trade licence number (`tradeLicense`). A trade licence marks the customer as a business. | | `meta.customer.name`, `meta.customer.lastName` | Optional | Shown to your customer on the Lean payment screens. | | `description` | Optional | Sent as the payment description. | | `meta.paymentDestinationID` | Optional | Overrides the **Payment Destination ID** for this payment. | Lean confirms the transfer after the customer authorizes it, so use manual capture in your workflow. Payrails records the capture when Lean reconciles the payment. *** ## Configure Lean settings Some Lean integration settings change how Payrails processes your payments. The portal shows the same description when you hover over each setting. | Setting | What it does | | :- | :- | | **Payment Destination ID** | The Lean payment destination that receives your payments. To use a different destination for one payment, send `meta.paymentDestinationID` in the authorize request. | | **Payment Purpose Code** | The purpose of the payments made through this account. Payrails sends it to the bank with every payment. Choose **None** to leave it out. The codes are `FIS` (financial services), `TCS` (telecommunications), `MWP` (mobile wallet card payments), `OAT` (own account transfer), `IFS` (information services), `RNT` (rent), `LNC` (loan charges), `PIN` (personal investments) and `GDS` (goods). | *** ## Enable the integration **In Payrails** * Select **Save account** to enable the integration. * Confirm the integration shows as **Enabled**. Your **Lean** integration is now ready to process payments. *** ## Next steps 1. Run a test payment in AED with a Lean sandbox bank. 2. Verify that: * Your customer can pick their bank and authorize the payment. * The payment status updates correctly in Payrails. 3. Once verified in test mode, repeat the setup in live mode. → Continue to: [Test a payment](https://docs.payrails.com/docs/orchestration/payment-acceptance/test-payments.md) ## Related topics - [React Native SDK API Reference](https://docs.payrails.com/docs/sdks/react-native/api-references.md) - [Web SDK Appearance API Reference](https://docs.payrails.com/docs/sdks/web/references/appearance-api-reference.md) - [Web SDK v5 Elements](https://docs.payrails.com/docs/sdks/web-v5-legacy/elements.md) This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.