> For the complete documentation index, see [llms.txt](https://docs.saferpay.com/home/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.saferpay.com/home/master/web-shop-plug-ins/shopware-6.md).

# Shopware 6

PCI and SCA compliant Shopware 6 Extension for Saferpay

## Supported Features <a href="#supported-features" id="supported-features"></a>

### Supported Versions <a href="#supported-versions" id="supported-versions"></a>

* Shopware 6.4.8.x - 6.7.x.x

### Payment methods <a href="#payment-methods" id="payment-methods"></a>

|                             |           |
| --------------------------- | --------- |
| Payment method              | Supported |
| Account-to-Account Payments | Yes       |
| Alipay                      | Yes       |
| American Express            | Yes       |
| Apple Pay                   | Yes       |
| Bancontact                  | Yes       |
| blik                        | Yes       |
| Click to Pay                | Yes       |
| Diners Club International   | Yes       |
| Discover Card               | Yes       |
| e-przelewy                  | No        |
| eps                         | Yes       |
| Google Pay                  | Yes       |
| iDEAL                       | Yes       |
| JCB                         | Yes       |
| Klarna Payments             | Yes       |
| Maestro Intl.               | Yes       |
| Mastercard                  | Yes       |
| paydirekt (Giropay)         | Yes       |
| PayPal                      | Yes       |
| Postfinance Pay             | Yes       |
| SEPA Direct Debit           | Yes       |
| Sofort by Klarna            | Yes       |
| TWINT                       | Yes       |
| UnionPay                    | Yes       |
| Visa                        | Yes       |
| V PAY                       | Yes       |
| WeChat Pay                  | Yes       |
| Wero                        | Yes       |
| WL Crypto Payments          | Yes       |

### Supported functionality <a href="#supported-functionality" id="supported-functionality"></a>

| Feature                                        | Supported                            |
| ---------------------------------------------- | ------------------------------------ |
| Multi-part captures                            | Yes (plugin version 6.0.0+)          |
| Recurring                                      | No                                   |
| Refunds                                        | Yes (plugin version 1.2.0+)          |
| Pre-Authorization                              | No                                   |
| Saferpay Fields                                | Yes (plugin version 1.3.1+)          |
| Saferpay Payment Page                          | Yes                                  |
| Saferpay Transaction Interface - Business Flow | No                                   |
| Secure Card Data (Tokenization)                | Yes (plugin version 1.4.2+)          |
| Dynamic Currency Conversion (DCC)              | Yes                                  |
| Multi Currency                                 | Yes<mark style="color:red;">​</mark> |

## Plugin Downloads​ <a href="#plugin-downloads" id="plugin-downloads"></a>

### Shopware 6.7.x.x <a href="#shopware-6.7.x.x" id="shopware-6.7.x.x"></a>

Release Date: 01.09.2026

{% file src="/files/Zz0yjBDKbAGYe2amzXn2" %}

Changelog Version 7.0.0

#### **Changed**

\- New version semantic (plugin's major version now matches Shopware 6 major version)

\- New interface for managing Saferpay payments in Shopware administration

\- Refactored refund process

\- Refactored capture process

#### **Added**

\- Added support for multipart capturing

\- Added support for multiple refunds

#### **Fixed**

\- In payment handler, a transaction will now only be set to canceled if the order transaction has not already failed

\- Fixed php.ini check for "allow\_url\_fopen"

### Shopware 6.6.x.x <a href="#shopware-6.6.x.x" id="shopware-6.6.x.x"></a>

Release Date: 01.09.2026

{% file src="/files/uV62bNbKZXpPcP5Q5Wc0" %}

Changelog Version 6.0.1

#### Changed

* New version semantic (plugin's major version now matches Shopware 6 major version)
* New interface for managing Saferpay payments in Shopware administration
* Refactored refund process
* Refactored capture process

#### Added

* Added support for multipart capturing
* Added support for multiple refunds

#### Fixed

* In payment handler, a transaction will now only be set to canceled if the order transaction has not already failed
* Fixed php.ini check for "allow\_url\_fopen"

### Shopware 6.5.x.x <a href="#shopware-6.5.x.x" id="shopware-6.5.x.x"></a>

Release Date: 11.02.2026

{% file src="/files/ZVUMdZRKukrLPdzB9Awn" %}

Changelog Version 1.9.0

\### Changed

* Removed payment methods “Paydirekt”, "Sofort" & “WL Crypto Payments”.
* Saferpay JSON API upgraded to Spec 1.50.

\### Added

* Added payment method “Wero”.

### Archive <a href="#plugin-downloads" id="plugin-downloads"></a>

#### Shopware 6.4.8.x

Release Date: 16.02.2024

{% file src="/files/UQlE2EuogjgtJHHzpcAV" %}
16.02.2024
{% endfile %}

## User Guide <a href="#user-guide" id="user-guide"></a>

User Guide - German: <https://docs.saferpay.com/home/interfaces/web-shop-plug-ins/shopware-6/shopware-6-user-guide-german>

User Guide - English: <https://docs.saferpay.com/home/interfaces/web-shop-plug-ins/shopware-6/shopware-6-user-guide-english>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.saferpay.com/home/master/web-shop-plug-ins/shopware-6.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.