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

# Wero via Deutsche Bank

> Accept Wero wallet payments from customers in Europe through Deutsche Bank, and see the merchant reference, customer and billing fields Payrails requires.

<picture noZoom>
  ![Wero logo](https://assets.payrails.io/img/logos/wero/logo.svg)
</picture>

<picture noZoom>
  ![Deutsche Bank logo](https://assets.payrails.io/img/logos/deutschebank/logo.svg)
</picture>

Accept [Wero](https://docs.payrails.com/docs/orchestration/payment-methods/wero) payments with Deutsche Bank as the payment service provider (PSP). Payrails redirects the customer to the Wero page, where they scan a QR code and approve the payment in the Wero app or their banking app.

## Supported workflows

<table>
  <thead>
    <tr><th>Workflow</th><th>Supported</th></tr>
  </thead>

  <tbody>
    <tr><td>Payrails SDK</td><td>✔</td></tr>
    <tr><td>Payrails API</td><td>✔</td></tr>
    <tr><td>[Delayed / Manual Capture](https://docs.payrails.com/docs/orchestration/payment-acceptance/capture-and-cancel-modes.md#capture-mode)</td><td>✖</td></tr>
    <tr><td>[Instant Capture](https://docs.payrails.com/docs/orchestration/payment-acceptance/capture-and-cancel-modes.md#capture-mode)</td><td>✔</td></tr>
    <tr><td>[Cancel / Void](https://docs.payrails.com/docs/orchestration/payment-acceptance/cancel-a-payment.md)</td><td>✖</td></tr>
    <tr><td>[Refund / Reverse](https://docs.payrails.com/docs/orchestration/payment-acceptance/refund-a-payment.md)</td><td>✔</td></tr>
    <tr><td>[Save Instruments](https://docs.payrails.com/docs/resources/manage-instruments.md)</td><td>✖</td></tr>
    <tr><td>[Merchant Initiated Transaction (MIT)](https://docs.payrails.com/docs/resources/payments/authorization-flags.md)</td><td>✖</td></tr>
  </tbody>
</table>

## Before you begin

Complete these steps before you send your first Wero payment through Deutsche Bank:

1. Set up a Deutsche Bank integration in your workspace. Follow the [Deutsche Bank integration setup guide](https://docs.payrails.com/docs/orchestration/integrations/deutsche-bank.md) if you don't have one yet.
2. Ask Deutsche Bank to activate Wero on your DB Gateway Europa account.
3. In the Payrails Portal, go to **Settings → Integrations**, open your Deutsche Bank integration, select **Wero** under **Payment methods**, and save.
4. Add Wero as a [payment option](https://docs.payrails.com/docs/orchestration/payment-methods/set-up-payment-methods.md) in your workflow.

## Request fields for Deutsche Bank

Send these fields in the authorize request, in addition to the standard [authorize fields](https://docs.payrails.com/reference/authorizeaction.md). **Required** fields must be present for the payment to succeed. Payrails sends **Optional** fields to the PSP when you include them.

| Field | Status | Description |
| - | - | - |
| `merchantReference` | Required | Set when you create the execution. Sent to Deutsche Bank as the reference on the customer's bank statement. Use up to 35 characters from letters, digits, spaces and `/ - ? : ( ) . , ' +`. |
| `amount.currency` | Required | Use `EUR`. |
| `meta.customer.email` | Required | Sent to Deutsche Bank as the customer email. You can send `meta.customer.phone.number` instead. |
| `meta.order.billingAddress.city` | Required | Sent to Deutsche Bank as the billing city. |
| `meta.order.billingAddress.postalCode` | Required | Sent to Deutsche Bank as the billing postal code. |
| `meta.order.billingAddress.country.code` | Required | Sent to Deutsche Bank as the billing country, for example `DE`. |
| `meta.customer.phone.countryCode`, `meta.customer.phone.number` | Optional | Sent to Deutsche Bank as the customer phone number, with the dialing code in front. |
| `meta.customer.name`, `meta.customer.lastName` | Optional | Sent to Deutsche Bank as the customer name. |
| `meta.order.billingAddress.street`, `meta.order.billingAddress.doorNumber` | Optional | Sent to Deutsche Bank as the billing street address. |
| `meta.clientContext.ipAddress` | Optional | Sent to Deutsche Bank as the customer IP. |

## Authorize a Wero payment

Create the execution with a `merchantReference` that fits the Wero format, for example `order-4821`. Then call [authorize a payment](https://docs.payrails.com/reference/authorizeaction.md) with `wero` as the `paymentMethodCode`. The response includes the redirect to the Wero page.

```json Authorize request theme={null}
{
  "amount": {
    "value": "25.00",
    "currency": "EUR"
  },
  "paymentComposition": [
    {
      "integrationType": "api",
      "paymentMethodCode": "wero",
      "amount": {
        "value": "25.00",
        "currency": "EUR"
      }
    }
  ],
  "meta": {
    "customer": {
      "name": "Max",
      "lastName": "Mustermann",
      "email": "max.mustermann@example.com"
    },
    "order": {
      "billingAddress": {
        "street": "Teststr.",
        "doorNumber": "1",
        "city": "Berlin",
        "postalCode": "10115",
        "country": {
          "code": "DE"
        }
      }
    }
  },
  "returnInfo": {
    "success": "https://example.com/success",
    "error": "https://example.com/error"
  }
}
```

The customer scans the QR code and approves the payment in the Wero app or their banking app. Confirm the result through [webhook notifications](https://docs.payrails.com/docs/orchestration/payment-acceptance/receive-notifications.md) or the execution status before you fulfill the order.

## How Deutsche Bank handles Wero

* Payrails checks the merchant reference, the customer contact and the billing address before it calls Deutsche Bank.
* Deutsche Bank captures Wero payments as soon as the customer approves them, so the payment completes in one step.
* Wero sends the customer back to your site after they approve or decline the payment. Payrails then reads the final result from Deutsche Bank, and Deutsche Bank also sends it as a notification.
* When the customer declines the payment in the app, Payrails marks it as canceled by the customer. When the customer leaves the Wero page without approving, Deutsche Bank closes the payment after about 10 minutes, and Payrails marks it as abandoned by the customer.
* You can refund a Wero payment in full or in part, as many times as you need up to the paid amount. A refund stays pending until Deutsche Bank sends its result as a notification, usually within seconds.
* Each Wero payment is a new customer-initiated payment.


## Related topics

- [Wero](https://docs.payrails.com/docs/orchestration/payment-methods/wero.md)
- [Deutsche Bank](https://docs.payrails.com/docs/orchestration/integrations/deutsche-bank.md)
- [Bank Transfers via Flutterwave](https://docs.payrails.com/docs/orchestration/payment-methods/bank-transfers/flutterwave.md)


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