Certificate Management for mutual TLS client certificate to API endpoints - Arcot
search cancel

Certificate Management for mutual TLS client certificate to API endpoints - Arcot

book

Article ID: 250093

calendar_today

Updated On:

Products

CA Payment Security

Issue/Introduction

This article looks to outline and track the certificates used in the interaction(s) listed below so they can be trusted by entities allowing Arcot to connect using mutual TLS. 
Arcot utilizes certificates that are valid for one year to ensure the highest level of security for transaction and other flow interactions. The most current certificates used by the Arcot service will be available and update as required.

The interactions will include the following:

  • Outbound mTLS from Arcot to entity using the certificate <silo>ssl.arcot.com (trusted for outbound API call) 

Resolution

Arcot’s recommendation is to trust the Root and Intermediate certificates only. If you are required to also trust the Leaf certificate, please ensure that all three certificates are loaded into your Trust Store. To avoid impact to service, the existing certificates must not be removed until they have expired.

Attachments

secure5a_arcot_com_682787208.zip get_app
secure2ssl_arcot_com_681548667.zip get_app
secure5ssl_arcot_com_681547590.zip get_app
tsysssl_arcot_com_618284911.zip get_app
mycardsecuressl_arcot_com_618276175.zip get_app
uat_ssl_arcot_com(05 Dec 2024).zip get_app
secure7ssl.arcot.com.zip get_app