The setup from your test environment is not copied over to your live environment, so you need to configure live settings for:<\/p>\n
After you have configured your live Customer Area<\/a> and the Adobe Commerce admin panel, test your integration by making real payments<\/a>.<\/p>\n If you have a feature request, or spotted a bug or a technical problem, create a GitHub issue<\/a>. For other questions, contact our Support Team<\/a>.<\/p>\n<\/div>\n The plugin renders the payment methods based on what is enabled in your Customer Area<\/a>.<\/p>\n Add information about the bank accounts<\/a> where you want to receive the payouts from Adyen, if you haven't done so as part of your application<\/a>.<\/p>\n<\/li>\n Review and change how you get paid<\/a>, if required.<\/p>\n<\/li>\n<\/ul>\n To learn more about risk management with Adyen, sign up for an upcoming webinar<\/a>.<\/p><\/div><\/div>\n\n By default, your Adyen account has a risk profile based on industry standards.<\/p>\n We strongly recommend to implement CAPTCHA to prevent card testing attacks<\/a>, also known as BIN<\/a> attacks.<\/p>\n Note that for Visa and Mastercard, the enrollment for 3D Secure<\/a> can take up to seven days. This means that you might not be able to offer 3D Secure<\/a> to your shoppers immediately after your live Customer Area<\/a> has been activated.<\/p>\n When using our Adobe Commerce plugin, you need to assess your PCI DSS compliance according to the Self-Assessment Questionnaire A (SAQ A)<\/a>. To meet SAQ-A requirements, we recommend to use the default card component of the plugin.<\/p>\n Adobe Commerce enforces strict Content Security Policy (CSP) rules under PCI DSS 4.0.1, that requires you to authorize and assure the integrity of scripts<\/a> regardless of your SAQ-A status. To meet the Adobe Commerce requirements, use plugin v9.17.0<\/a> or later.<\/p>\n If you customized the plugin front end, or use a headless integration, you must review the applicable compliance requirements<\/a>, and make sure you comply with script security requirements for PCI DSS v4.0.1<\/a>.<\/p>\n You are responsible for ensuring compliance with WCAG and EAA accessibility standards.<\/p>\n The Adyen Adobe Commerce plugin uses technologies that do not enforce additional accessibility requirements by default. The Adyen Plugins team does not implement additional accessibility measures beyond what the Adobe Commerce platform<\/a> and Adyen Web Components<\/a> provide.<\/p>\n Set up webhooks<\/a> in your live Customer Area<\/a>.<\/p>\n<\/li>\n In your Adobe Commerce admin panel<\/a>, enter the webhook credentials and the HMAC key from your live Customer Area<\/a>.<\/p>\n<\/li>\n Follow the instructions to for non-default event codes<\/a> to enable the OFFER_CLOSED<\/a> webhook. This is needed to close abandoned orders.<\/p>\n<\/li>\n Check that you are receiving all webhook event types<\/a> needed for your integration.<\/p>\n<\/li>\n To prevent webhook events being queued<\/a>, make sure that you accept all webhook events<\/a>.<\/p>\n<\/li>\n The plugin has a cronjob that handles the webhook event. To test that this is working correctly:<\/p>\n If the webhook is working correctly, you will see a successful HTTP response status code<\/a>, for example To make sure your integration can handle the entire payment lifecycle<\/a> with real payment details, you need to test possible scenarios with real payment details.<\/p>\n Payments with real details incur fees. To have enough funds available for refunds, consider setting up a Reserve<\/a>.<\/p>\n<\/div>\n Once you have completed the above checklist, you are ready to accept live payments!<\/p>\nAccount<\/h2>\n
Set up your live account structure<\/h3>\n
\n
Give team members access to the live environment<\/h3>\n
\n
Set up payment methods<\/h3>\n
\n
Finance<\/h2>\n
Receive payouts from Adyen<\/h3>\n
\n
Use reports for reconciliation<\/h3>\n
\n
(Optional) Set up a Reserve<\/h3>\n
\n
Risk and compliance<\/h2>\n
Risk webinar<\/h5>
\n
3D Secure<\/h3>\n
\n
Compliance<\/h3>\n
Accessibility (WCAG\/EAA) Compliance<\/h3>\n
API communication<\/h2>\n
\n
\n
Webhooks<\/h2>\n
\n
\n
ResponseCode<\/code>: 200<\/strong>.<\/p>\nEnd-to-end testing<\/h2>\n
\n
resultCode<\/code>: Refused<\/strong>, for example by entering incorrect card details.<\/li>\nrefusalReason<\/code>: FRAUD<\/strong>, by triggering multiple risk checks to achieve a risk score above 100<\/strong>.\n<\/li>\n<\/ul>\nCapture<\/h3>\n
\n
3D Secure<\/h3>\n
\n
Next steps<\/h2>\n