When activating cards on behalf of your customers, ensure that the PIN chosen by the customer is encrypted before sending via API.🔐 Encryption Standard
- Algorithm: RSA
- Key: Contact the admin to obtain the RSA public key for production use
- Padding: PKCS#1 v1.5
- Encoding: UTF-8 for input, Base64 for output
- Always use the latest RSA public key shared by the platform.
- Do not attempt to decrypt the PIN — only the platform (with its private key) can do so.
- Use PKCS#1 v1.5 padding, not OAEP.
This is the account number mapped to a customer’s embedly wallet. Example:
`12345678901
This is the card number issued to the customer and mapped to the account
number above. Example:
123456789012
This is the random pin choosen by the customer. Example:
encrypted string