Certificate Management for Signing and Endpoint certificates - Arcot

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 looking to connect to Arcot. 
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:

• Inbound TLS from entity to Arcot at <silo>api.arcot.com (trusted for AfDB endpoints, callback service(OOB), and also used for request signing)
• Inbound TLS from entity to Arcot at <silo>.arcot.com (trusted for Data upload services)
• Inbound TLS from entity to Arcot at secure5a.arcot.com (trusted for Asynchronous Transaction Data Feed (ATDF) and Risk Analysis Case Management API) 

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.