Go-live checklist

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

• Account
• Finance
• Risk and compliance
• API communication
• Webhooks

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

Account

Set up your live account structure

• Create additional merchant accounts if needed for your business.

Give team members access to the live environment

• Create a separate user for each team member who needs to access your live Customer Area.
• Give each user the roles and account access required to perform their tasks.
• Set up Customer Area notifications to be notified of important events such as chargebacks.
• Consider setting up two-factor authentication for increased security.

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.

• Make sure that the capture flow is configured correctly in your live Customer Area, and in the SAP back office.

Finance

Receive payouts from Adyen

• Add information about the bank accounts where you want to receive the payouts from Adyen, if you haven't done so as part of your application.

• Review and change how you get paid, if required.

Use reports for reconciliation

• Set up automatic generation of reports.
• Use the Settlement details report to reconcile your accounts on a transaction level.
• Consider automating your reconciliation process.

(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

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

• Review and customize your risk profile.
• Set up Customer Area notifications about Fraudulent Payments (NOF) and Chargebacks (NOC).
• Make sure that you know how risk rules are triggered, for example by making a payment where the billing address is different from the delivery address, or using different email addresses with the same IP address.

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.

Compliance

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 that your live API credentials have the following permissions:
  • Merchant PAL webservice role
  • Merchant Recurring role
  • Checkout webservice role
  • Checkout encrypted cardholder data

Webhooks

• Configure server webhook settings in your live Customer Area, and in the SAP back office.

• Check that you are receiving all webhook event types needed for your integration.

• To prevent webhook events being queued, make sure that you accept all webhook events.

• The add-on has a scheduled job that handles the webhook event. To test that this is working correctly:

  1. In your Customer Area, go to Developers > Webhooks.
  2. Next to Standard Webhook, select the edit webhook icon .
  3. Select Test Configuration.
  4. If you are on a company account, select a Merchant account from the dropdown list.
  5. In the Event dropdown list, select the event code.

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.

• 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.

Capture

• If using manual capture, capture a payment.
• If using manual capture or a capture delay of 1-7 days, cancel a payment before it has been captured.
• If using multiple partial captures, capture part of the authorised amount, and make sure that the remaining amount is not automatically cancelled.

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 have completed the above checklist, you are ready to accept live payments!