TLS certificates
Last updated: June 3, 2026
All communication with Checkout.com APIs is encrypted in transit using the Transport Layer Security (TLS) protocol. During the TLS handshake, Checkout.com provides a certificate chain consisting of leaf and intermediate certificates signed by several different certificate authorities. To validate the authenticity of a certificate, a complete chain of trust must be established. The complete chain of trust ends with a trust anchor, which is within the client's trust store.
Most modern operating systems and browsers have these certificates preinstalled. If you manage your own trusted store of certificate authorities, you must include them in that trusted root store. If you do not, certificate validation fails during the TLS handshake and your client cannot establish a secure connection.
Information
Avoid pinning the leaf or intermediate certificates, as they change frequently.
When integrating with Checkout.com APIs, your trust store must include the following certificates:
| Certificate subject name | Serial | Repository location |
|---|---|---|
|
|
|
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
To ensure maximum compatibility, add all of these certificates to the trust store that your application uses. If this list of trusted certificate anchors changes, we'll send you an email from updates@checkout.com.