mTLS Inbound and Outbound

In order for you to access and use the CLOWD9 Production API, Dynamic Data Stream services and 3D Secure web hooks, a Mutual Transport Layer Security (mTLS) connection must be in place. The connection can be with third parties of your choosing.

With mTLS in place, a secure connection is established and as result only parties which have the private keys and associated certificates in place are able to use the services. Any unauthorised access and security risks are mitigated protecting you, your Customers and CLOWD9.

Our Non-Production environment does not require the use of mTLS as this is test data; however this can be configured if required.

During the Implementation project, your Implementation Manager will provide the mTLS forms required to be completed. This will require support from you; however the activities are not complex and can be undertaken in parallel to other integration activities.

CLOWD9 support two types of communication flows:

• Inbound : API Management, whereby CLOWD9 will generate and share the signed certificate upon receiving a Certificate Signing Request (CSR).
• Outbound : Dynamic Data Stream and 3DS webhooks whereby CLOWD9 require you to generate and share the signed certificate.