This section provides information about API methods designed for managing bank cards. You can use these methods to issue new cards, check balances, retrieve card information, and perform other card-related operations. The API enables seamless integration of card functionalities into your systems, ensuring convenient and secure access to card data.In addition to standard card operations, the API provides functionality for validating cardholder identity. This includes verifying that the personal details provided by a user (first name, last name, and phone number) match the information registered with the system for a given card token
Working with Encrypted Data in Payment Cards Services#
In the Payment Cards section, RSA encryption is used to protect confidential information such as PAN, CVC, card PIN, and other sensitive data.There are two supported formats for working with encrypted data:1.
From Freedom Processing to the partner
a. Freedom Processing encrypts the data using the partner's public key.
b. The partner decrypts the data using their private key.
2.
From the partner to Freedom Processing
a. The partner encrypts the data using the Freedom Processing public key.
b. Freedom Processing decrypts the data using its private key.
Key Exchange#
To establish encrypted communication, either share your public RSA key with Freedom Processing or request their public key, depending on the direction of data exchange. Please contact your account manager for the key exchange process.Encryption requirements#
Encryption Method: Asymmetric Encryption
Encryption Key: Recipient's public RSA key
Transmission format: Encrypted data is encoded in Base64
Sender-Side Encryption Process#
1.
Prepare the plaintext data (card_pan,card_cvc,pin).
2.
Use the recipient’s public RSA key to encrypt the data using:
3.
Encode the encrypted data in Base64.
Recipient-Side Decryption Process#
1.
Receive the encrypted data encoded in Base64.
2.
Decode the Base64 string to get the encrypted binary data.
3.
Use your private RSA key to decrypt the data using:
4.
Retrieve the original plaintext data.
Example: Using Encrypted Data with the Set PIN Method#
Option 1 - PIN Provided by the Partner#
The partner generates the PIN to be set.
The PIN is encrypted using the public RSA key of Freedom Processing, obtained from the account manager.
The Base64-encoded encrypted value is passed in the pin field of the request body.
Freedom Processing decrypts the received value using its private RSA key and sets the PIN for the card.
Option 2 - PIN Generated by Freedom Processing#
The partner calls the Set PIN method without specifying a PIN in the request.
In this case, the PIN is generated and set by Freedom Processing.
The generated PIN is then encrypted using the partner’s public RSA key, previously exchanged via the account manager.
The encrypted PIN is delivered to the partner through one of the agreed secure channels.
The partner decrypts the received value using their private RSA key to retrieve the original PIN.
Modified at 2025-07-24 12:00:34
