Technical Requirements

1. Transaction Log

Digital services which have integrated with Verify should track and store user transactions for potential issue management.

The following are some of the suggested minimum fields for tracking:

• State/ Transaction No. from the Verify request body

• Fields requested from Verify

• Time Stamp

In the event of user feedback or contact, these transaction logs may be requested by us to reconcile and resolve issues raised by the user.

---

2. X.509 Public Key

To implement RS256 (RSA Signature with SHA-256) Digital Signature for Verify APIs in your apps, please use a X.509 Public Key Certificate with RSA key size of 2048 bits or larger from one of the following compatible Certificate Authority (CA):

• Comodo/Sectigo

• digiCert

• GeoTrust

• GlobalSign

• Netrust*

• Thawte

• VeriSign

*Certificate must be issued by Netrust. Entrust-issued certs are not accepted.

ECC and ECDSA Public Key Certificates are currently NOT supported.

---

3. TLS & Cipher Suites

IMPORTANT: In line with contemporary industry best practices, Verify supports TLS 1.2 and above.

The list of supported strong cipher suites include:

• TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384

• TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256

• TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384

• TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256

---

4. Webhook URLs (applicable to version 1 only)

For security reasons:

• Different Webhook URLs should be used for staging and production environments

• Fully Qualified Domain Name (FQDN) of staging and production environments should be used (i.e. instead of IP address)

• Webhook URLs should not contain Hash (#) or Wildcard (*) characters