On This Page

{#jumplink-list}  
[Markdown](/docs/vas/en-us/platform/developer/all/rest/rest-getting-started/restgs-jwt-shared-secret-intro/restgs-jwt-shared-secret-test.md)  
Filter  
FILTER BY TAG

Test Your Setup {#restgs-jwt-shared-secret-test}
================================================

You can send a test API request to validate that your account, API key, JWT messages, and MLE security are working as intended.  
`Visa Acceptance Solutions``Visa Acceptance Platform` recommends that you test and verify that your payment system can securely send and receive REST API messages before transitioning to a production account.

Postman Testing
---------------

You can use Postman to verify your HTTP signature message. To download a Postman collection of basic payment API requests, see the [REST API](https://documenter.getpostman.com/view/2960117/S17m1riA?version=latest "") collection on the Postman website.  
When testing an API outside of the Developer Center's API Reference sandbox, send your test API requests to the test server: `https://apitest.visaacceptance.com`  
For example, to test an authorization request, you can send the request to this endpoint: `https://apitest.visaacceptance.com``/pts/v2/payments`

Test Your REST--API Response Key {#restgs-jwt-shared-secret-mle-dev-center}
===========================================================================

Follow these steps to verify that your API response MLE key is working. If you have not already created or submitted an API response MLE certificate, see the Create or Submit a REST---API Response MLE Key section in [Enable Message-Level Encryption](/docs/vas/en-us/platform/developer/all/rest/rest-getting-started/restgs-jwt-message-intro/restgs-mle-intro.md "").

1. Go to the REST API Reference page in the `Visa Acceptance Solutions` Developer Center:  
   [`https://developer.visaacceptance.com/api-reference-assets/index.html#static-home-section`](https://developer.visaacceptance.com/api-reference-assets/index.md#static-home-section "") {#restgs-jwt-shared-secret-mle-dev-center_d75e22}
   {#restgs-jwt-shared-secret-mle-dev-center_d75e22}

2. On the left navigation panel, choose an API that supports MLE. For testing purposes, you can choose **Intelligent Commerce \&gt; Intelligent Commerce Product \&gt; Enroll a Card** .  
   MLE support is indicated by **Request MLE** and **Response MLE** at the top of the screen.  
   ![](/content/dam/documentation/cybs/en-us/topics/platform/rest/getting-started/images/restgs-mle-tags.png/jcr:content/renditions/original) {#restgs-jwt-shared-secret-mle-dev-center_d75e32}
   {#restgs-jwt-shared-secret-mle-dev-center_d75e32}

3. Choose the **MLE Configuration** tab.{#restgs-jwt-shared-secret-mle-dev-center_d75e50}
   {#restgs-jwt-shared-secret-mle-dev-center_d75e50}

4. In the Message Level Encryption Credentials section, enter your API response MLE key credentials:

   * **Response encryption:** Enter the key ID of your API response MLE key.  
     You saved this key ID in Step 10 in the Create or Submit an API Response MLE Key section in [Enable Message-Level Encryption](/docs/vas/en-us/platform/developer/all/rest/rest-getting-started/restgs-jwt-message-intro/restgs-mle-intro.md "").
   * **Response decryption:** Click **Browse** to submit your own private decryption key from your local system. Only *.p12* files are supported.

   ![](/content/dam/documentation/cybs/en-us/topics/platform/rest/getting-started/images/restgs-mle-dev-center-upload.png/jcr:content/renditions/original) {#restgs-jwt-shared-secret-mle-dev-center_d75e56}
   {#restgs-jwt-shared-secret-mle-dev-center_d75e56}

5. Click **Update Credentials**.{#restgs-jwt-shared-secret-mle-dev-center_d75e85}
   {#restgs-jwt-shared-secret-mle-dev-center_d75e85}

6. From the **Send** drop-down menu, choose **Send Request with Message Level Encryption**.{#restgs-jwt-shared-secret-mle-dev-center_d75e92}
   {#restgs-jwt-shared-secret-mle-dev-center_d75e92}

7. Click **Send** .  
   ![](/content/dam/documentation/cybs/en-us/topics/platform/rest/getting-started/images/restgs-mle-dev-center-send.png/jcr:content/renditions/original) {#restgs-jwt-shared-secret-mle-dev-center_d75e101}
   {#restgs-jwt-shared-secret-mle-dev-center_d75e101}

8. When a *Success: HTTP Status Code: 201* message displays in the Response section, your API response key is properly configured.  
   ![](/content/dam/documentation/cybs/en-us/topics/platform/rest/getting-started/images/restgs-mle-ebc-success.png/jcr:content/renditions/original) {#restgs-jwt-shared-secret-mle-dev-center_d75e111}
   {#restgs-jwt-shared-secret-mle-dev-center_d75e111}  
   RELATED TO THIS PAGE

* <>
* [Getting Started with REST](https://developer.visaacceptance.com/docs/vas/en-us/platform/developer/all/rest/rest-getting-started/restgs-intro.md)
* [Response Codes](https://developer.visaacceptance.com/api/reference/response-codes.md)
* [API Reference Sandbox](https://developer.visaacceptance.com/api-reference-assets/index.md#static-home-section)
* [Business Center Test](https://businesscentertest.visaacceptance.com/ebc2/)
* [Business Center Production](https://businesscenter.visaacceptance.com/ebc2/)
* [Customer Support](https://developer.visaacceptance.com/support/contact-us.md)

