Visa Direct

For clients using the Mobile Push Payment Receive Side APIs, it is important to understand that some of the sensitive information (e.g. PAN, consumer name) are encrypted by Visa in the outgoing message from Visa to the client. This encryption is done using a key ID and shared secret assigned to the client during onboarding. All the data elements in the payload that have the prefix "enc" are encyrpted, for e.g. 'encMerchantPan'.

Clients need to follow these steps in order to decrypt these fields:

• Get the necessary software library that supports AES GCM mode encryption in client preferred programming languages (e.g. Java, PHP, C#, etc.) for software development. E.g. download and install Java Cryptography Extension (JCE) unlimited strength jurisdiction policy files.
  
• When the request payload data from Visa is received,
  • Identify the data field that requires decryption, i.e field name starts with prefix "enc"
  • Parse the encrypted value using the software library and extract “Key ID”
  • Use “Key ID” to fetch the corresponding shared secret required for decryption. Note: client may have more than one “Key ID” and “shared secret” from Visa stored in their system due to key management
  • Decrypt the encrypted data field using the shared secret to get the field value.
    

There is no need to perform encryption of the response payload data as there is no sensitive data field in the response payload.