Message Level Encryption Developer Docs Updated

Community Manager

Getting started with Message Level Encryption (MLE) just got a little easier with an enhanced MLE Encryption Guide

 

As many of you know, API products hosted through Visa Developer leverage either Mutual SSL or X-Pay Token to authenticate/authorize clients. Now, Visa also sends and receives sensitive information for which, an additional level of security in the form of Message Level Encryption is required as per TSR Guidelines.  

 

MLE on Visa Developer provides an enhanced security for message payload by using asymmetric encryption technique (public-key cryptography). 

 

Why this matters?

 

While MLE is optional or not applicable for most Visa APIs, there are some APIs which support MLE in enforced/mandatory condition only. This means, users will need MLE implemented on top of Mututal SSL Authentication. The encryption requires separate key-pairs for the Request or Response payloads of the transaction. 

 

Users who must implement MLE will see changes in the Go-Live process which includes new important key steps like uploading additional files - so it's important to get caught up on what is required here and we've laid it out for you in our Developer API Documentation - MLE Encryption Guide page

 

Get all the details in the guide, including encryption requests and decryption response payloads in Java, Python, Node.JS and C#.

 

Like what you see in the guide? Want to see more? Let us know your feedback by commenting below, we'd love to hear from you. 

Comments
Dabbler

This is great to provide even more options for your consumers!

blogs

Recent Blogs