Go-live checklist

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

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

After you have configured your live Customer Area, 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 account security.

Set up payment methods

• Add all the payment methods that you want to offer to your shoppers.
• Make sure that payments appear correctly on the shopper's bank statement. Configure the shopperStatement field when making a payment or when creating a payment session.

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 by the information that you send in your payment request. Some fields are strongly recommended to include because they are required for specific risk checks.
• Include the correct information on your receipts for online card payments and/or in-person payments, depending on your integration.

Compliance

Make sure that your integration supports 3D Secure, so that you can apply SCA for transactions in scope of PSD2 SCA and other local regulations.

3D Secure

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

• Configure your own rules for Dynamic 3D Secure, to have more control over which transactions are processed with 3D Secure.
• Make sure that you know how the 3D Secure flow is triggered by the information that you send in your payment request. For more information, refer to our 3D Secure integration guides.

API communication

Before you can make live API requests to Adyen, you need to:

• Generate an API key in your live Customer Area, and copy this to your live integration.
• Make sure that your live API credentials have the required API permissions.
• Update the Adyen endpoints to your live endpoints.

Webhooks

• Set up webhooks in your live Customer Area.
• Make sure that you acknowledge webhook events with a successful HTTP response status code, for example 202, to prevent events being queued.
• Make sure that you are receiving all webhook event types needed for your integration.

End-to-end testing

To make sure your integration can handle the entire payment lifecycle, 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, and 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 a part of the authorised amount, and make sure that the remaining amount is not automatically cancelled.

Redirect payment methods

Redirect payment methods require the shopper to be redirected to another website or app to complete the payment. This is the payment flow for most wallets, online banking. We also support a redirect 3D Secure flow.

If you implemented any redirect payment methods, test the following scenarios:

• After being redirected, wait for more than five minutes to complete the payment.
• Select the Cancel/Back button on the redirected page, to cancel the payment.
• Close the browser when on the redirected page, to simulate the shopper abandoning the session.

3D Secure

• Make a successful payment with 3D Secure authentication, and verify that the flow that you chose to implement (either redirect or native 3D Secure 2) is triggered correctly.
• Make a 3D Secure payment where the shopper fails to complete the challenge.
• Make sure that 3D Secure is triggered correctly according to your risk settings (Dynamic 3D Secure and your risk profile).

Tokenization

If you implemented tokenization, follow the checklist below:

• Make sure that you receive the recurringProcessingModel in your payment response.
• If you want to receive the recurringDetailReference in a webhook event, enable receiving the RECURRING_CONTRACT event code.
• Create a token when making a payment.
• Use the token to make a payment.
• If you want to validate card details before processing payments, make a zero-auth transaction. If you implemented 3D Secure, also make a zero-auth transaction with 3D Secure.

Next steps

Once you have completed the above checklist, you are ready to accept live payments!