Search

Are you looking for test card numbers?

Would you like to contact support?

Online-payment icon

Go-live checklist

Follow this checklist before you start accepting live payments.

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

After you have configured your live Customer Area, test your integration by making real payments.

Account

Set up your live account structure

Give team members access to the live environment

Set up payment methods

The most commonly used payment methods are: Visa, Mastercard, American Express, Alipay, iDEAL, Apple Pay, Union Pay, Boleto, Google Pay, Klarna, SEPA

Discover popular ways to pay with our payment methods explorer.

  • Make sure that you've added all the payment methods that you want to offer to your shoppers.
  • Check that the countries and currencies are configured correctly for each payment method. To change these settings, contact our Support Team.
  • Make sure that payments appear correctly on the shopper's bank statement. To make any adjustments to the shopper statement, contact our Support Team.

Finance

Receive payouts from Adyen

  • If you haven't done so yet, add information about the bank accounts where you want to receive the payouts from Adyen. If you're accepting payments in multiple currencies, you can add a separate bank account for each currency.

  • By default, we pay out funds on a daily basis (from Monday to Friday), with transactions processed on a single day paid out in one batch (Sales day payout). You can review and change your payout schedule in your Customer Area > Finance > Payout model.

Use reports for reconciliation

Set up a refund reserve

  • Consider setting up a refund reserve: this is used to perform refunds to your shoppers in case of insufficient in-process funds in your Adyen account.
  • To make sure there's always enough balance available on your account for refunds, you can also set up AutoFunding.

Risk

Risk webinar

To learn more about risk management with Adyen, sign up for one of our upcoming webinars.

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.

  • 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.
  • If you have merchant accounts in the United States, contact our Support Team to enable 3D Secure on US acquirer accounts.
  • If you are doing zero-auth transactions, contact our Support Team to enable 3D Secure for zero-auth transactions.

API communication

Your API requests to Adyen are authenticated with an API key linked to your web service (ws) user. Before you can make live payments, you need to:

  • Generate an API key in your live Customer Area, and copy this to your live integration.
  • Make sure that your live ws user has the same roles as your test ws user.
  • Update the Adyen endpoints to your live endpoints.

Notification webhooks

End-to-end testing

To make sure your integration can handle the entire payment lifecycle, do end-to-end testing with real payment details:

Payments with real details incur fees. To have enough funds available for refunds, consider setting up a refund 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, 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, as well as for 3D Secure 1.

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

If you implemented 3D Secure, test the following scenarios:

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

Next steps

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