On This Page

Step 2: Shared Secret Key Pair

Key pairs are used with HTTP Signature message security.

Create a Shared Secret Key Pair

Follow these steps to create a shared secret key pair.
  2. On the left navigation panel, choose
    Payment Configuration > Key Management
    .
  3. Click
    + Generate
     key.
  4. Under REST APIs, choose
    REST – Shared Secret
     and then click
    Generate key
    .
    The REST API Shared Secret Key page appears.
  5. Click
    Download key
     .
    The .pem file is downloaded to your desktop.
You can create or upload another key by clicking
Generate another key
. To view all of your created keys, use the Key Management page.
IMPORTANT
Securely store the
.p12
 file and password in your system. These credentials are required to implement certain products and you must be able to access them.

Test the Shared Secret Key Pair

After creating your key certificate, you must test and verify that your key can successfully process API requests. These tasks explain how to test and validate your key certificate using the developer center and the
Business Center
.
  2. On the left navigation panel, click .
  3. Under Authentication and Sandbox Credentials, set the Authentication Type drop-down menu to HTTP Signature.
  4. Enter your organization ID in the Organization ID field.
  5. Enter your key, also known as your private key, in the Key field.
  6. Enter your secret key, also known as your public key, in the Shared Secret Key field.
  7. Click
    Update Credentials
    .
  8. On the developer center's left navigation panel, navigate to
    Payments >
    POST
     Process a Payment
    .
  9. Under Request: Live Console, click
    Send
    .
    A message confirms that your request was successful with the status code 201.
  10. Log in to the
    Business Center
    :
  11. On the left navigation panel, navigate to
    Transaction Management > Transactions
    .
  12. Under Search Results, verify that the request ID from the test authorization response is listed in the Request ID column.
    If the test authorization was successful, a success message is present in the corresponding Applications column.