API security

In ensuring robust security for our APIs, Banking.Live prioritizes SSL encryption, with HTTPS connections being the default protocol.

This security measure provides protection and authentication through SSL PKI, where Banking.Live verifies API calls against client certificates.

Default HTTPS connections

Banking.Live operates with HTTPS connections as the default protocol for all APIs.

SSL encryption

SSL encryption is employed to safeguard data transmitted between clients and the Banking.Live server.

Protection and authentication

SSL PKI is utilized to ensure both the protection and authentication of data during API calls.

Client certificate verification

API calls made to Banking.Live are verified against client certificates, enhancing the security and integrity of the communication.

Data and PIN security

Sensitive information such as PAN, CVV2, and PIN is not stored nor used during processing. Internal tokens related to them are used instead, providing a secure method that protects card numbers from being stolen or misused.

Encryption during transmission

Sensitive data, including PAN, CVV2, and PIN, is encrypted during transmission between clients and the Banking.Live server, ensuring an additional layer of security provided by PaySecure API.

You can learn more about PaySecure API and its role in ensuring the confidentiality and integrity of sensitive information here.

Static API headers

A static personalized API key issued during client onboarding for use in API headers for authentication purposes.

You can learn more about Static API headers and how to use them here.