On This Page
FILTER BY TAG
Test Your Setup
You can send a test API request to validate that your account, API key, JWT messages, and
MLE security are working as intended.
Cybersource
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 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.cybersource.com
For example, to test an authorization request, you can send the request to this
endpoint:
https://apitest.cybersource.com
/pts/v2/paymentsTest Your REST–API Response Key
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.
- Go to the REST API Reference page in theCybersourceDeveloper Center:
- On the left navigation panel, choose an API that supports MLE. For testing purposes, you can chooseIntelligent Commerce > Intelligent Commerce Product > Enroll a Card.MLE support is indicated byRequest MLEandResponse MLEat the top of the screen.

- Choose theMLE Configurationtab.
- 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.
- Response decryption:ClickBrowseto submit your own private decryption key from your local system. Only.p12files are supported.

- ClickUpdate Credentials.
- From theSenddrop-down menu, chooseSend Request with Message Level Encryption.
- ClickSend.

- When aSuccess: HTTP Status Code: 201message displays in the Response section, your API response key is properly configured.
