Plugin icon

Go-live checklist

Follow this checklist before you start accepting live payments.

The setup from your test environment is not copied over to your live environment, so you need to configure live settings for:

After you have configured your live Customer Area and the SAP back office, test your integration by making real payments.


Set up your live account structure

Give team members access to the live environment

Set up payment methods

The add-on renders the payment methods based on what is enabled in your Customer Area.

  • Add all the payment methods that you want to offer to your shoppers.
  • Check that the payment methods are rendered in the correct order in your checkout. You can change the order of local payment methods in your Customer Area > Settings > Checkout settings.
  • Make sure that payments appear correctly on the shopper's bank statement. To make any adjustments to the shopper statement, contact our Support Team.


Receive payouts from Adyen

Use reports for reconciliation

(Optional) Set up a Reserve

  • Consider setting up a Reserve: this is used for refunds and other operational expenses in case of insufficient in-process funds.

Risk and compliance

Risk webinar

To learn more about risk management with Adyen, sign up for an upcoming webinar.

By default, your Adyen account has a risk profile based on industry standards.

3D Secure

Note that for Visa and Mastercard, the enrollment for 3D Secure can take up to seven days. This means that you might not be able to offer 3D Secure to your shoppers immediately after your live Customer Area has been activated.


When using our SAP Commerce add-on, you need to assess your PCI DSS compliance according to the Self-Assessment Questionnaire A (SAQ A).

API communication

  • Set up API credentials in your live Customer Area, and in the SAP back office.
  • Make sure your live API credentials have the following permissions:
    • Merchant PAL webservice role
    • Merchant Recurring role
    • Checkout webservice role
    • Checkout encrypted cardholder data


If the webhook is working correctly, you will see a successful HTTP response status code, for example ResponseCode: 200.

End-to-end testing

To make sure your integration can handle the entire payment lifecycle with real payment details, you need to test possible scenarios with real payment details.

Payments with real details incur fees. To have enough funds available for refunds, consider setting up a Reserve.

  • For each payment method that you offer, make a successful payment using real details.
  • Make a payment with resultCode: Refused, for example by entering incorrect card details.
  • Make a payment with refusalReason: FRAUD, by triggering multiple risk checks to achieve a risk score above 100.
  • Make a refund using our API, including a partial refund.


3D Secure

  • Make a successful payment with 3D Secure authentication.
  • Make a 3D Secure payment where the shopper fails to complete the challenge.

Next steps

Once you've completed the above checklist, you're ready to accept live payments!