Configure your application
Configure your application
Set up your Lean application before making API requests or starting customer journeys.
This guide covers the UAE Dashboard, environments, credentials and the configuration required for Open Finance.
1. Open the Lean Dashboard
Log in to the Lean Dashboard, select your application and choose the environment you want to configure.
Open Development → Integration settings to access your app token, client secret, webhook secret and registered redirect URLs.
Your access depends on your Dashboard role:
| Role | Integration settings access |
|---|---|
| Owner or Admin | Can view the app token, client secret and webhook secret, and manage redirect URLs by default. |
| Developer | Can view the app token by default. Managing redirect URLs is enabled by default in Sandbox and requires additional permission in Production. Viewing the client secret and webhook secret requires additional permissions in either environment. |
If you are integrating with a Developer role, ask your organisation's Owner or Admin to grant the additional permissions you need.
2. Start in Sandbox
Use Sandbox to build and test your integration with test customers and supported mock banks.
| Environment | Use it to |
|---|---|
| Sandbox | Develop your integration and test customer journeys using synthetic data. |
| Production | Connect to supported financial institutions and process live customer activity. |
For Sandbox:
- Send API requests to
https://sandbox.leantech.me. - Generate OAuth tokens through
https://auth.sandbox.leantech.me/oauth2/token. - Set
sandbox: truein your Link SDK configuration. - Use test data only.
Keep your Sandbox and Production configuration separate, including credentials, resource IDs, redirect URLs and webhook settings.
3. Retrieve your application credentials
In the Lean Dashboard, open Development → Integration settings.
Retrieve your Application ID and client secret.
| Value | How you use it |
|---|---|
| Application ID | Pass it as client_id when requesting an OAuth token and as app_token when configuring the Link SDK. |
| Client secret | Use it on your backend to request OAuth tokens. |
Your Application ID and app token are the same value. Access tokens are generated through the authentication flow.
Store the client secret securely on your backend. Do not include it in frontend code or mobile application bundles.
Authenticate your integration →
4. Configure consent statements
Configure the purpose and benefit statements customers see when providing consent.
You can provide both statements in English and Arabic, using wording that reflects your product and how you will use the customer's permission.
| Statement | What it should explain |
|---|---|
| Purpose | Why you are requesting permission and what you will use it for. |
| Benefit | How granting permission helps the customer complete their task or use your service. |
Configure the statements for each consent journey you support:
- Payment consents — explain why you are requesting permission to initiate payments.
- Data consents — explain why you need access to financial information to provide the relevant insights or service.
For example, a lending application might explain that financial information will be used to assess affordability, with the benefit of reducing the information the customer needs to provide manually.
5. Register your redirect URLs
After a customer authenticates with their bank or authorises a consent or payment they should be returned to your application.
Register the return URLs for your application before using them in the Link SDK.
| SDK parameter | Purpose |
|---|---|
successRedirectUrl | Returns the customer after a successful authorisation journey. |
failRedirectUrl | Returns the customer after an unsuccessful or cancelled authorisation journey. |
Use registered URLs for the environment you are testing. Before going live, register and test your Production URLs.
Your return pages must handle the redirect using the Link SDK's captureRedirect method, as described in the relevant integration guide.
Returning to a success URL does not, by itself, confirm that a payment completed or that financial insights are ready. Use API responses and webhooks to determine the business outcome.
6. Prepare your webhook configuration
Configure a webhook endpoint and subscribe to the events required by your integration.
Your endpoint should be ready before you test customer journeys so your backend can receive connection, consent and payment updates.
A redirect URL returns the customer to your application. A webhook URL receives notifications on your backend. Configure each for its own purpose.
Set up webhooks →
7. Prepare your Production configuration
Once Sandbox testing is complete, review your Production setup with Lean before serving live customers.
| Configuration | What to check |
|---|---|
| Product access | Confirm Production access for each product and the supported banks required by your integration. |
| Credentials | Configure the credentials for your Production application in your backend's secrets manager. |
| API and authentication endpoints | Use the Production API endpoint specified for your integration and https://auth.leantech.me/oauth2/token for token generation. |
| Link SDK | Use your Production app token and set sandbox: false. |
| Consent statements | Review the English and Arabic statements used in your live journeys. |
| Redirect URLs | Register and test the URLs used by your live application. |
| Webhooks | Configure your live endpoint, required subscriptions and signature verification. |
| Product resources | Create or configure the Customers, destinations and connected business accounts required for your Production flows. |
Do not reuse Sandbox resource IDs in Production requests.
Next steps
Updated 41 minutes ago
