-
Notifications
You must be signed in to change notification settings - Fork 16
Home
Adyen PrestaShop integration supports PrestaShop versions 1.7.5.0 and up.
Feature | Support |
Cards Integration | Checkout API (component) |
LPM Integration | Checkout API (component) |
Pay by link | No |
POS Integration | No |
Express checkout | Yes |
Adyen Giving | Yes |
Gift Cards | HPP |
Tokenization | |
Tokenize card details for one-off | Yes |
Tokenize local payment methods for one-off | No |
Subscriptions | No |
Card Installments | Yes |
Authorization | |
Sending level 2/3 data | Yes |
3D Secure 1 | No |
3D Secure 2.0 | Yes |
Order Status updated when in manual review | Yes |
Show risk score in order payment information | Yes |
Payment & order management | |
Cancel | Yes |
Full capture | Yes |
Partial capture | Yes |
Auto capture | Yes |
Manual capture | Yes |
Full Refunds | Yes |
Partial Refunds | Yes |
Refunds Available from the Customer Area only | No |
Other/Additional | |
MOTO (mail order, telephone order) | No |
Include open invoice data into request | Yes |
- BLIK
- EPS
- giropay
- iDEAL
- Klarna Pay now
- MB WAY
- MobilePay
- Online banking Finland
- Online banking India
- Online banking Poland
- Online banking Thailand
- Sofort (Online bank transfer)
- Trustly
Adyen PrestaShop integrations support configuring multiple sub shops within one PrestaShop administration panel. You can select the store context at any time during the integration configuration by using the store switcher.
Download the latest plugin release from the GitHub repository and upload it through the PrestaShop Plugin Manager.
For authenticating API requests from PrestaShop, you need to provide an API key.
To generate an API key for your test environment:
- Log in to your Customer Area.
- Go to Developers > API credentials, and select the credential username for your integration, for example ws@Company.TestCompany.
- Under Authentication, select Generate New API Key.
- Copy and securely store the API key in your system — you won't be able to retrieve it later.
- If your API key is lost or compromised, you need to generate a new one.
- Select Save at the bottom of the page.
API key should have the following roles:
- Management API - Accounts read
- Management API - Accounts read and write
- Management API - API credentials read and write
- Management API - Payout Account Settings Read
- Management API - Webhooks read
- Management API - Webhooks read and write
- Management API - Payment methods read
- Management API - Stores read
- Management API - Stores read and write
- Checkout encrypted cardholder data
- Checkout webservice role
- Data Protection API
- Merchant PAL Webservice role
- Merchant Recurring role
- API Clientside Encryption Payments role
To get an API key for your live environment, follow the same steps in your live Customer Area.
You will need to add either the test or the live API key in the integration dashboard, depending on the selected environment, as described in Step 2.
After successfully authenticating with the provided API key from step 2, the integration will automatically register the client key and allowed origins on the Adyen API, and you will be requested to select the merchant account to link to the Adyen account. This will automatically generate a HMAC key and register webhooks for that merchant account.
To enable a payment method, you need to add it in your Customer Area.
All available payment methods will be displayed on the payment methods configuration page.
You can configure their display properties, as well as define additional surcharges for each configured payment method.
The following payment methods provide some additional configuration:
- Single click payments
- Installment configuration
- Sending L2/L3 data
- Installment configuration
- Apple Pay merchant credentials
- Enable express checkout
- Amazon Pay merchant credentials
- Enable express checkout
- Google Pay merchant credentials
- Enable express checkout
- Enable express checkout
Upon installation, the integration will set default status mappings between PrestaShop order statuses and Adyen payment states. However, you can change this mapping at any time by navigating to the status mapping configuration page and changing how these statuses should map.
These mappings will be used to transition the PrestaShop order into a status mapped to the Adyen payment state in the incoming webhook request from the Adyen API. Webhooks are triggered when there is a change to the created payment in the Adyen platform.
After you've set up the plugin, use our test card numbers to make test payments.
After your test payments, look up the payment status in your Customer Area. If a transaction has been refused due to a high-risk score, consider making adjustments to your risk profile scoring.
You can configure the following properties for each activated payment method:
Configuration | Description |
Payment method name | Title displayed to customers on checkout. |
Payment method description | The description is displayed to customers at checkout. |
Payment method logo | The customizable image will be displayed to customers at checkout. |
Surcharge type | Available options:- None |
- Fixed surcharge: Fixed surcharge added to the order total
- Percent surcharge: Percentage of the total order amount added as a surcharge
- Combined surcharge: Combines fixed and percent surcharge | | Fixed surcharge amount | Available only if the surcharge type is fixed or combined. Specifies a fixed surcharge in the current order currency that will be added to the order total. | | Percent surcharge | Available only if the surcharge type is a percent or combined. Specifies a percentage of the total order amount that will be added to the order total. | | Surcharge limit | Available only if surcharge type is a percent or combined. Specifies a fixed amount in the current order currency that represents a threshold that cannot be surpassed by the total surcharge amount. In case the total calculated surcharge amount is higher than the limit, the limit amount will be set as a surcharge. |
Some payment methods offer additional configuration options (single-click payments, installments, express checkout configuration, etc.)
With our Adyen Giving feature, you can give your shoppers the option to donate to a charity as part of your payment flow. This feature is available with credit cards and iDEAL payment methods.
You can configure the following options:
Configuration | Description |
Enable Adyen Giving | Enable the Adyen Giving feature (merchants must also choose and enable a charity in their customer area) |
Charity Name | The name of the chosen charity. |
Charity Description | Description of the chosen charity. |
Charity Merchant Account | The Adyen account name of the charity. |
Donation Amounts | Comma-separated suggested donation amounts. |
Charity Logo | Logo of the chosen charity |
Background Image | The background image that appears in the Component |
Charity Website | The website URL of the charity |
The integration sends the following PrestaShop customer data to the Adyen API:
- ID
- Name
- Birthday
- Billing address
- Shipping address
- Checkout locale
- Order items
Whenever the system performs a significant action that requires the merchant's attention (or is simply informative), such notification will be forwarded to the notifications hub.
Notifications in the notifications hub are split to shop events and webhook events.
Shop events contain all integration actions that require the merchant's attention or serve to inform the merchant.
Webhook events effectively represent a transaction log of all payments made with Adyen payment methods in the shop system.
The integration extends the order details page with additional information about the payment on Adyen. You can perform one of the following actions on this page:
- Cancel a payment
- Capture a payment (partially or fully)
- Refund a payment (partially or fully)
You can capture and/or refund Adyen payments only by amounts. Additionally, on this page you can see the full transaction history of that payment, with a timeline of all status changes on that payment.
If you are using the plugin version 4.0.7 or below, you should migrate to the new version of the plugin.
If you are on an older version of the PrestaShop plugin, you might be using the Adyen API key that does not have sufficient roles to access the management API. An API key is considered invalid if it has insufficient roles or if webhook registration/HMAC registration/test fails.
If this is the case, during the migration process, the integration will detect that the current Adyen API key stored in the configuration does not have sufficient roles.
The migration process will migrate configured connection credentials, payment methods, transaction logs, and transaction details for orders placed with Adyen payment methods in the last 30 days.
All payment methods that are not supported by the new plugin will be deactivated. In the case of a multistore environment, after the migration process ends, payment methods will be available in shops where a valid API key is present. The merchant will have to manually reconnect and configure a plugin for every PrestaShop sub-store where an invalid API key was detected.
Since integration cannot keep track of which orders were captured before the migration process, the integration will enable all actions for those orders (cancel, capture, refund). It will rely on Adyen API to refuse invalid actions.
-
Installation and setup
- Step 1: Install the plugin
- Step 2: Generate an API key
- Step 3: Generate a client key
- Step 4: Set up notifications
- Step 5: Set up Capture Delay
- Step 6: Set up the plugin in PrestaShop back office
- Step 7: Set up payment methods
- Step 8: Set up a cron job
- Step 9 (optional): Validating the plugin
- Step 10: Make test payments
- Updating from a version earlier than 2.1.0
- Reinstalling the plugin
- Logs
- Go-live checklist
- Upgrade the Plugin
- Troubleshooting