On This Page

{#jumplink-list}  
[Markdown](/docs/cybs/en-us/security-keys/user/all/ada/security-keys/keys-manage/keys-rest-mle-intro.md)  
Filter  
FILTER BY TAG

REST---API Response MLE Key {#keys-rest-mle-intro}
==================================================

This section describes how to create, submit, and test a REST---API response MLE key.  
Message-Level Encryption (MLE) enables you to store information or communicate with other parties while helping to prevent uninvolved parties from understanding the stored information. MLE is required only for certain payments services. Enabling MLE requires you to create a *REST -- API Response MLE* key. If your organization is using a meta key, the portfolio account or merchant account that created the meta key must also create the REST -- API Response MLE key.  
MLE is required for APIs that primarily deal with sensitive transaction data, both financial and non-financial. These are the types of sensitive transaction data:

* Personal identification information (PII)
* Personal account number (PAN)
* Personal account information (PAI)
  {#keys-rest-mle-intro_d22e40}  
  MLE is supported when using JSON web tokens.

Additional Information
----------------------

For information about how to implement MLE in your system, see the [Enable Message-Level Encryption](https://developer.cybersource.com/docs/cybs/en-us/platform/developer/all/rest/rest-getting-started/restgs-jwt-message-intro/restgs-mle-intro.md "") section in the *Getting Started with REST* Developer Guide.  
RELATED TO THIS PAGE

* [Customer Support](https://support.visaacceptance.com/)
* [REST API Field Reference Guide](https://developer.cybersource.com/docs/cybs/en-us/api-fields/reference/all/rest/api-fields/rest-api-fields-intro.md)