> ## 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.

# Lidio

> Connect Lidio to Payrails for card payments in Türkiye, covering your merchant code, API key and API password.

<Note>
  **Who should use this guide**

  This guide is intended for merchants who:

  * Use **Payrails** as a payment orchestrator
  * Use **Lidio** for card processing in Türkiye
  * Have an active Lidio merchant account
</Note>

***

## Create a Lidio 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.
</Note>

***

## Step 1: Choose the integration type

* Select **Payment**.
* Continue to the next step.

***

## Step 2: Choose the provider

* Select **Lidio**.
* Continue to the next step.

<img src="https://mintcdn.com/payrails-42074109/DS81KC-NNGTwOcXz/images/docs/lidio-image-01.png?fit=max&auto=format&n=DS81KC-NNGTwOcXz&q=85&s=dd9e725b1cd0c333650ed9517c8e3261" alt="A screenshot showing Lidio selected as the provider." className="mx-auto block rounded-lg object-cover border border-gray-200" width="80%" data-path="images/docs/lidio-image-01.png" />

***

## Step 3: Configure your Lidio integration

<Tip>
  **What you'll need from Lidio**

  Before you begin, make sure you have your Lidio merchant code, API key and API password. Lidio provides them when it sets up your account.
</Tip>

***

### 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_lidio`.

<img src="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" alt="A screenshot showing the integration instance name field." className="mx-auto block rounded-lg object-cover border border-gray-200" width="80%" data-path="images/docs/orchestration/integrations/shared/integration-instance-name.png" />

***

### Account details

**In Payrails**

| Field | Value |
| :- | :- |
| **Merchant Code for Lidio** | Your Lidio merchant code |

<img src="https://mintcdn.com/payrails-42074109/DS81KC-NNGTwOcXz/images/docs/lidio-image-02.png?fit=max&auto=format&n=DS81KC-NNGTwOcXz&q=85&s=0d8d2aa29ced0bc403811f7d9f9af75d" alt="A screenshot showing the Lidio account details fields." className="mx-auto block rounded-lg object-cover border border-gray-200" width="80%" data-path="images/docs/lidio-image-02.png" />

***

### Credentials

**In Payrails**

| Field | Value |
| :- | :- |
| **API key** | Your Lidio API key: the value Lidio gives you for the `Authorization` header, without the `MxS2S` prefix |
| **API Password** | Your Lidio API password. Payrails uses it to verify notifications from Lidio. |

Payrails sends requests to the Lidio test environment in test mode and to the live environment in live mode, so use the credentials for the matching environment.

<img src="https://mintcdn.com/payrails-42074109/DS81KC-NNGTwOcXz/images/docs/lidio-image-03.png?fit=max&auto=format&n=DS81KC-NNGTwOcXz&q=85&s=e4a1821151267917e8ef20b7c03764c1" alt="A screenshot showing the Lidio credential fields." className="mx-auto block rounded-lg object-cover border border-gray-200" width="80%" data-path="images/docs/lidio-image-03.png" />

***

### Payment methods

**In Payrails**

* Select **Card**.

<img src="https://mintcdn.com/payrails-42074109/DS81KC-NNGTwOcXz/images/docs/lidio-image-04.png?fit=max&auto=format&n=DS81KC-NNGTwOcXz&q=85&s=a3604799a87e2e78937b9f033ac24258" alt="A screenshot showing the Lidio payment method selection." className="mx-auto block rounded-lg object-cover border border-gray-200" width="80%" data-path="images/docs/lidio-image-04.png" />

***

### Webhooks or notifications

Payrails sends its notification URL to Lidio with every payment, so you don't need to set one up in the Lidio dashboard. Payrails verifies each notification with your API password.

***

## Request fields for Lidio

Send these fields in the [authorize request](/reference/authorizeaction) for card payments, in addition to the standard authorize fields. **Required** fields must be present for the payment to succeed. Payrails sends **Optional** fields to Lidio when you include them. For more about meta fields, refer to [Meta fields](/docs/orchestration/meta-fields).

| Field | Status | Description |
| :- | :- | :- |
| `amount` | Required | Sent to Lidio as the total amount and currency. |
| `merchantReference` | Required | Sent as the order ID: letters and numbers only, up to 20 characters. |
| `meta.customer.name` | Required | Sent as the customer name. |
| `meta.customer.email` | Required | Sent as the customer email. |
| `meta.customer.reference` | Required | Sent as the customer ID. |
| `meta.customer.phone.number` | Required | Sent as the customer phone. |
| `meta.order.billingAddress` | Required | Sent as the invoice address. Include `country.name`, `city`, `area` and `postalCode`. |
| `meta.order.deliveryAddress` | Required | Sent as the delivery address. Include `country.name`, `city`, `area` and `postalCode`. |
| `meta.order.lines` | Optional | Sent as the basket items, with `name`, `quantity` and `unitPrice`. The lines must add up to `amount`. |
| `meta.risk.threeDSMode` | Optional | `Force` runs 3D Secure. |

***

## Enable the integration

**In Payrails**

* Select **Save account** to enable the integration.
* Confirm the integration shows as **Enabled**.

Your **Lidio** integration is now ready to process payments.

***

## Next steps

1. Run a test card payment in TRY in the Lidio test environment.
2. Verify that:
   * The payment appears in Lidio.
   * The payment status updates correctly in Payrails.
3. Once verified in test mode, repeat the setup in live mode.

→ Continue to: [Test a payment](/docs/orchestration/payment-acceptance/test-payments)


## Related topics

- [Integrations](/docs/orchestration/integrations.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.