Certificate change for *.adyen.com and *.adyenpayments.com

Adyen will roll the wildcard certificates *.adyen.com and *.adyenpayments.com on the live platform on 22nd January 2020 between 09.00 and 12.00 AM CET. Adyen will send out a system message once the certificate has been replaced successfully.

1) Will I be affected by this certificate change?

Likely this change does not affect your integration. Only merchants that do (custom) certificate pinning may need to check if the correct certificates are in their certificate trust store.

2) How can I verify if I am doing certificate pinning?

Certificate pinning is done on the merchant’s side of the integration. Therefore, merchants' certificate pinning strategies are not visible to Adyen. In case you are unsure, please check with your technical team, service administrator, or system integrator.

Merchants who do not perform certificate pinning, do not require to take action.

3) What is Adyen's recommendation on certificate validation?

By default, Adyen does not recommend to perform certificate pinning on Adyen's wildcard certificate because this may impact connectivity to Adyen's systems at the moment the certificate is rolled. In practice, for various reasons Adyen may decide to roll the certificate at different moments in time (with or without prior communication).

In case you use a custom Certificate TrustStore, merchants will have to trust the public Root Certificate Authority (CA): DigiCert Global Root G2. You can find the latest Root CA using the following links:

Similarly for the Root CA, Adyen may decide at any moment in time (with our without prior communication) to change the Root CA. In case the Root CA is not trusted, this may impact merchant connectivity to Adyen's systems. 

4) How can I check which certificate(s) is/are relevant for my integration?

You can verify the domains used for API requests to Adyen. Each certificate corresponds to the API calls performed under the domains with the same name: adyen.com or adyenpayments.com  respectively. These endpoints are used for sending API requests to Adyen's systems, for example for:

  • Payment authorisations
  • Checkout
  • Modifications (such as refunds and captures)
  • Recurring / token management
  • MarketPay
  • Automatic report downloads

Usually, the endpoints can be found from your configuration. Your technical team or system integrator will be able to determine which endpoint(s) are being used in your integration.

5) Can I verify my connection in the test environment with Adyen?

The certificate for *.adyen.com is already available in the test environment as of January 9th 2020. Your technical team or integrator can already start verifying your payments integration that fall under this domain and certificate by checking if there are no connection errors.

The certificate for *.adyenpayments.com is used for merchant-specific endpoints. As merchant-specific endpoints are only available on Adyen's live system, the certificate has not been made available within our testing environment. For more information about endpoints, please refer to this page: Live Endpoint Structure.

For further questions regarding these certificates, please contact support (support@adyen.com).

Have more questions? Submit a request

Articles in this section