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

# Unzer

> Connect Unzer to Payrails as a payment provider, covering API credentials, webhooks, and the raw card data approval required.

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

  This guide is intended for merchants who:

  * Use **Payrails** as a payment orchestrator
  * Use **Unzer** for payments
  * Are approved to process **raw card data**

  *Payrails uses a server-to-server integration with Unzer. Your Unzer account must be enabled for raw card data processing. If this is not enabled, payments will fail in production. Contact your Unzer account manager or support team to activate this capability.*
</Note>

***

## Create and configure a Unzer 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 **Unzer**.
* Continue to the next step.

***

## Step 3: Configure your Unzer integration

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

  Before you begin, make sure you have access to:

  * **Public key**
  * **Private key**

  Log in to the [Unzer dashboard](https://insights.unzer.com/signin?redirect_to=/) to complete this step.
</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.

<img src="https://mintcdn.com/payrails-42074109/6ZmkK5ZUHpx1-EP_/images/docs/dlocal-basic-information.png?fit=max&auto=format&n=6ZmkK5ZUHpx1-EP_&q=85&s=b9a43582acab50b93394ecc2898d5ecf" alt="Payrails Unzer integration instance name field" className="mx-auto block rounded-lg object-cover border border-gray-200" width="100%" data-path="images/docs/dlocal-basic-information.png" />

***

### API credentials

<Tip>
  Use restricted or scoped credentials where possible to limit access and reduce
  risk.
</Tip>

**In Unzer**

1. Go to **Settings** → **Configuration** → **API Keys**.
2. Copy the following values:
   * **Public key**
   * **Private key**
     <img src="https://mintcdn.com/payrails-42074109/knNnlxc2J__TB9tW/images/docs/unzer-image-02.png?fit=max&auto=format&n=knNnlxc2J__TB9tW&q=85&s=df0a9d733dc6dce07eb5ea23080ab94a" alt="Unzer dashboard API keys page showing public and private keys" className="mx-auto block rounded-lg object-cover" width="100%" data-path="images/docs/unzer-image-02.png" />

**In Payrails**

* Paste the values into the corresponding fields.

<img src="https://mintcdn.com/payrails-42074109/knNnlxc2J__TB9tW/images/docs/unzer-image-01.png?fit=max&auto=format&n=knNnlxc2J__TB9tW&q=85&s=545f43add3898809a37b1af48c12693a" alt="Payrails Unzer API credential fields" className="mx-auto block rounded-lg object-cover border border-gray-200" width="80%" data-path="images/docs/unzer-image-01.png" />

***

### Payment methods

**In Payrails**

* Select the payment methods you want to enable (for example **Card**).

***

### Webhooks or notifications

<Tip>
  Payrails uses Unzer notifications to receive asynchronous payment status
  updates.
</Tip>

<Warning>
  Create notifications in the same environment (test or live) as your Payrails
  integration.
</Warning>

**In Payrails**

* Copy the **Notification URL** from the configuration screen.

<img src="https://mintcdn.com/payrails-42074109/6ZmkK5ZUHpx1-EP_/images/docs/dlocal-basic-information.png?fit=max&auto=format&n=6ZmkK5ZUHpx1-EP_&q=85&s=b9a43582acab50b93394ecc2898d5ecf" alt="Payrails account configuration showing Notification URL field" className="mx-auto block rounded-lg object-cover border border-gray-200" width="100%" data-path="images/docs/dlocal-basic-information.png" />

**In Unzer**

1. Go to **Settings** → **Configuration** → **Notifications**.
2. Create a new notification endpoint.
3. Paste the **Notification URL** from Payrails.
4. Enable events for:
   * **Authorization**
   * **Charge**

***

## Enable the integration

**In Payrails**

* Save the configuration.
* Confirm the integration shows as **Enabled**.

The **Enabled** status indicates that your Unzer integration is active and ready to process payments in test mode.

***

## Next steps

1. Run a test payment using an Unzer [test card](https://docs.unzer.com/reference/test-cards/).

2. Verify that:
   * The payment appears in Unzer.
   * The payment status updates correctly in Payrails.

3. Once verified in test mode, repeat the setup using **live credentials**.

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


## Related topics

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