API Overview

Creating and Using Security Keys User Guide
- Recent Revisions to This Document
- VISA Platform Connect: Specifications and Conditions for Resellers/Partners

Introduction to Creating and Using Security Keys

Create a Security Key
- PGP Keys
  - Creating PGP Keys
  - Adding PGP Keys to Your Account
  - Granting User Permissions
- REST API Keys
  - Create a P12 Certificate
  - Submit a Certificate Signing Request
  - Transacting Merchant User: Create a Shared Secret Key Pair
- REST—API Response MLE Key
  - Create or Submit a REST—API Response MLE Key
  - Test Your API Response MLE Key
- Secure Acceptance Keys
- Simple Order API Keys
- SOAP Toolkit Keys
- Message-Level Encryption Keys

Manage a Security Key
- Deactivate a Key
- Delete a Key
- Search for Keys Using Filters

Meta Key Creation and Management
- Create a Meta Key as a Portfolio User
- Create a Meta Key as a Merchant Account User
- Assign a Meta Key to All Merchants
- Assign a Meta Key to Select Merchants
- Remove a Meta Key from all Merchants
- Remove a Meta Key from Select Merchants
- Convert a Meta Key or Non-Meta Key
- Delete a Meta Key
- Regenerate a Meta Key

Meta Keys in API Requests
- REST API Payment Request with a Meta Key
- Simple Order API Payment Request Using a Meta Key
- SOAP Payment Request Using a Meta Key
- SCMP API Payment Request using a Meta Key

On This Page

REST—API Response MLE Key

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)

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 section in the Getting Started with REST
Developer Guide.

Back to top