Use Adyen's plugin for Shopware 6 to offer frictionless payments online, in-app, and in-store.
We strongly encourage you to join us in contributing to this repository so everyone can benefit from:
- New features and functionality
- Resolved bug fixes and issues
- Any general improvements
Read our contribution guidelines to find out how.
This plugin supports Shopware >= 6.3.1.1
Please note that versions >= 3.0.0 of this plugin only support Shopware versions >= 6.4. If you are on a lower Shopware version please use version 2.
For Shopware 5 support please see our Shopware 5 repository.
Please find the relevant documentation for
If you have a feature request, or spotted a bug or a technical problem, create a GitHub issue. For other questions, contact our support team.
The plugin integrates card component (Secured Fields) using Adyen Checkout for all card payments.
- Credit and debit cards (non 3D secure, 3D secure 1, 3D secure 2 native)
- Stored card payment methods (One click payment methods)
- Express checkout (with GooglePay, ApplePay, and PayPal methods)
- Affirm
- AfterPay invoice
- Alipay , Alipay HK
- Apple Pay
- Bancontact
- Blik
- Billie
- Clearpay
- Electronic Payment Service (EPS)
- Gift cards
- Google Pay
- iDeal
- Klarna Pay Later
- Klarna Pay Now
- Klarna Pay Over Time
- Klarna Debit Risk
- MB Way
- MobilePay
- Multibanco
- Oney (3x, 4x, 6x, 10x, 12x)
- PayBright
- PayPal
- PaySafeCard
- RatePay, RatePay Direct Debit
- Riverty (Pay in 14, Direct Debit)
- SEPA Direct Debit
- Swish
- Trustly
- Twint
- Vipps
- WeChat Pay
- Open Banking / Pay by Bank
- Online Banking Finland
- Online Banking Poland
For users with sales channels that have a storefront, webhooks should be configured following the standard process outlined in the Adyen documentation.
If a user has only headless sales channels (i.e., channels without a storefront),
webhook support is also available.
In this case, the webhook URL should be structured as follows:
Sales channel domain URL followed by /store-api/adyen/notification/{salesChannelId}.
The salesChannelId parameter must be a valid sales channel ID of an active sales channel.
This module is using the Adyen APIs Library for PHP for all (API) connections to Adyen. This library can be found here
The storefront serves a bundled copy of the Adyen Web SDK (adyen.js, adyen.css and their source maps) from src/Resources/public/.
The version and SHA-384 hashes of the bundled files are recorded in src/Resources/public/adyen-web-sdk.json, and CI fails if a committed file does not match.
To update the SDK, never edit or copy the files by hand. Run the script from the repository root:
.github/workflows/scripts/update-web-sdk.sh <version>Optionally pass --expect-js sha384-... and --expect-css sha384-... to fail if the downloaded files do not match known hashes.
Commit the four SDK files together with the updated manifest.
Run the build script from the repository root:
.github/workflows/scripts/prepare-release-asset.sh # release ZIP from the last commit
.github/workflows/scripts/prepare-release-asset.sh 5.3.9 # release ZIP from a tag or branch
.github/workflows/scripts/prepare-release-asset.sh --dev # dev ZIP from the working treeA release build creates AdyenPaymentShopware6.zip from committed files only, so uncommitted changes and IDE folders are never included.
A dev build creates AdyenPaymentShopware6-dev.zip with uncommitted changes and new files under src/, for local testing only.
Both builds install vendor/ from the committed composer.lock and fail if the shipped Adyen packages differ from it.
MIT license. For more information, see the LICENSE file.