Wero is a European digital wallet developed by the European Payments Initiative (EPI), aiming to provide a unified, instant, and secure payment solution across Europe. Launched in 2024, Wero enables users to send and receive money between bank accounts in under 10 seconds, 24/7, using just a phone number. The Wero wallet will initially be available in Germany, Belgium, France followed by the Netherlands and Luxembourg. Learn more about Wero.

Payment method properties


Markets (consumer)	`BE` `DE` `FR`
Processing currencies	`EUR`
Consumer currencies	`EUR`
Authentication methods	`REDIRECT`
Authentication timeout
Minimum payment amount	0.01 EUR
Maximum payment amount	Varies by consumer bank
Payment instrument	`PASSTHROUGH_WALLET`
Recurring payments	No
Separate captures	No
Refund	Full - Partial - Multiple
Refund validity	2 years
Disputes	Yes
Settlement risk	No

Make a Wero payment

Wero payments follow our standardized REDIRECT payment flow. We recommend including all relevant settings for any authentication methods you support.

To create a Wero payment, you'll need to provide the following data at minimum when calling our payment charges endpoint:

Field	Description
`paymentMethod`	`WERO`
`amount.value`	The amount to be paid in the smallest units of the currency used.
`amount.currency`	`EUR`
`consumer.country`	The country of residence of the consumer.
authenticationSettings: REDIRECT `settings.returnUrl`	Specify the URL to which the consumer should be redirected after completing the payment. This is required for the `REDIRECT` payment flow.

Request

POST /v1/payment-charges

{
  "paymentMethod": "WERO",
  "amount": {
    "value": 1000,
    "currency": "EUR"
  },
  "consumer": {
    "country": "DE"
  },
  "authenticationSettings": [
    {
      "type": "REDIRECT",
      "settings": {
        "returnUrl": "https://www.webshop.com/order-results-page"
      }
    }
  ]
}

Response

You'll receive our standard payment charge response with the available authentication methods:

{
  "id": "charge_Y3JVzvEaJpvG53xd2R2Zt",
  "paymentMethod": "WERO",
  "paymentMedium": "ECOMMERCE",
  "scheduleType": "UNSCHEDULED",
  "instrumentId": "instr_Asu0ig2PXXZSiNrhY44A5",
  "currency": "EUR",
  "country": "DE",
  "status": "AUTHENTICATION_PENDING",
  "consumer": {
    "country": "DE"
  },
  "authenticationMethods": [
    {
      "details": {
        "requestUrl": "https://redirection-target.ppro.com",
        "requestMethod": "GET"
      },
      "type": "REDIRECT"
    }
  ],
  "authorizations": [
    {
      "id": "authz_aPobet0FNZNU1bYqfexFd",
      "amount": 1000,
      "status": "AUTHENTICATION_PENDING",
      "createdAt": "2025-06-21T08:34:20.766Z",
      "updatedAt": "2025-06-21T08:34:20.766Z"
    }
  ],
  "captures": [],
  "refunds": [],
  "discards": [],
  "voids": [],
  "createdAt": "2025-06-21T08:34:20.114Z",
  "updatedAt": "2025-06-21T08:34:20.766Z",
  "_links": {
    "authorizations": {
      "href": "/v1/payment-charges/charge_Y3JVzvEaJpvG53xd2R2Zt/authorizations"
    },
    "captures": {
      "href": "/v1/payment-charges/charge_Y3JVzvEaJpvG53xd2R2Zt/captures"
    },
    "refunds": {
      "href": "/v1/payment-charges/charge_Y3JVzvEaJpvG53xd2R2Zt/refunds"
    },
    "discards": {
      "href": "/v1/payment-charges/charge_Y3JVzvEaJpvG53xd2R2Zt/discards"
    },
    "voids": {
      "href": "/v1/payment-charges/charge_Y3JVzvEaJpvG53xd2R2Zt/voids"
    }
  }
}

Pick the desired authentication method

REDIRECT

Redirect your consumer to the returned $.authenticationMethods[?(@.type == "REDIRECT")].details.requestUrl.
For example, with the value of https://redirection-target.ppro.com/ using the returned $.authenticationMethods[?(@.type == "REDIRECT")].details.requestMethod HTTP method.

Handling the payment result

REDIRECT

After the consumer completes the payment, they are redirected to the returnUrl specified in the payment charge creation request.
Upon redirect back to your site, retrieve the latest payment status by performing a GET /v1/payment-charges/{paymentChargeId}. Use the returned status field to determine and display the final payment outcome to the consumer.
Additionally, webhooks are triggered to notify you of the payment result. This ensures you receive the outcome even if the consumer closes their browser or fails to return to your website.

Payment instrument

A PASSTHROUGH_WALLET instrument will be created for Wero, with no additional data provided.

Request

GET /v1/payment-instruments/{instrument-id}

Response

{
    "id": "instr_5ChenWBwW8xARvJ3GccAx",
    "type": "PASSTHROUGH_WALLET"
}

Sandbox testing

Select "Pay with Wero code" and click the displayed code to copy it. Then, go to the Wero site and click the "Give consent" button. Paste the copied code into the field provided, choose the desired payment outcome (Approve or Deny).

Disputes & chargebacks management

A consumer has up to 120 days from the transaction date to initiate a pre-dispute for a Wero payment (this may extend up to 540 days in specific delivery-related cases). Wero encourages consumers to resolve issues directly with the merchant via the app's integrated communication channel before escalating to a formal dispute.

Wero dispute management is available via the PPRO global disputes platform. If you are not integrated via API, PPRO will notify you via email of any new pre-disputes or chargebacks.

Once a pre-dispute or dispute is raised, the merchant is required to provide a response (Challenge, Accept, or Offer) within 7 days. Failure to respond within this window will result in the dispute being automatically lost.

The section below contains the technical specifications and settings for Wero for an integration with the PPRO global disputes platform via API.

Wero uses the extended dispute lifecycle and requires the following support:


Dispute phases	`pre-dispute` `dispute` `pre-arbitration` `arbitration`
Chargebacks	Preemptive chargebacks with reversals
Chargeback timing	Dispute is raised → Preemptive chargeback raised Merchant challenges a dispute → Chargeback reversed Merchant loses after a challenge → Chargeback raised Arbitration won → Chargeback reversed

The following actions are allowed in each phase:

Phase	Action Type	Due By (Days)	Message Config	Files Required	Amount Required	Supported Resolutions
PRE_DISPUTE	`CHALLENGE`	7	Required (1 - 2000 chars)	No	No	N/A
	`ACCEPT`	7	Required (1 - 2000 chars)	N/A	N/A	`full-refund`, `partial-refund`, `replacement`
	`OFFER`	7	Required (1 - 2000 chars)	N/A	N/A	N/A
DISPUTE	`CHALLENGE`	7	Required (1 - 2000 chars)	No	Yes	N/A
	`ACCEPT`	7	Required (1 - 2000 chars)	N/A	N/A	N/A
PRE_ARBITRATION	`CHALLENGE`	7	Required (1 - 2000 chars)	No	No	N/A
	`ACCEPT`	7	Required (1 - 2000 chars)	N/A	N/A	N/A
ARBITRATION	N/A	N/A	N/A	N/A	N/A	N/A

The following capabilities are allowed in all phases:

Capability Type	Statuses Allowed In	Configuration Details
UPLOAD_FILE	`ACTION_REQUIRED`, `ACCEPT_PROCESSING`, `CHALLENGE_PROCESSING`, `OFFER_PROCESSING`, `UNDER_REVIEW`, `LOST`, `WON`, `OFFER_ACCEPTED`, `OFFER_REJECTED`	Types: PDF/A-1b, PNG, JPG, JPEG Max Size: 10 MB Max Files: 100
POST_MESSAGES	`ACTION_REQUIRED`, `ACCEPT_PROCESSING`, `CHALLENGE_PROCESSING`, `OFFER_PROCESSING`, `UNDER_REVIEW`, `LOST`, `WON`, `OFFER_ACCEPTED`, `OFFER_REJECTED`	N/A