Common Setup Questions

 

How does the API reference page work?

This 5-minute tutorial video explains the features of the API reference.

 

Which features are not available in the sandbox environment?

You can test your integration in the sandbox before you go live. Sandbox transactions are for testing purposes only. The following features are not available in the sandbox: 

Performance and stress testing

Simulated gateways or processors

 

What is a shared secret key?

A shared secret key is a base64-encoded transaction key string. You authenticate to the API using this key that is unique to your account. We use it to connect your website or API integration to the CyberSource Payment Gateway for transaction processing. It is different from your login credentials for the Merchant Portal.

 

How do I obtain a shared secret key for my sandbox account?

If you do not have a Merchant Portal account, sign-up.

Use your Merchant Portal account to create a shared secret key

 

What is a Certificate or P12 Key?

A certificate is one way to authenticate to APIs. The certificate includes public and private keys unique to your account. CyberSource generates the public key. You generate the private key from a JNLP file provided by CyberSource.

Note: Certificate authentication uses a PKCS12 key file with the .p12 extension to digitally sign your API request message before transmitting the message to CyberSource.

 

How do I obtain a .p12 keys for my sandbox account?

If you do not have a Merchant Portal account, sign-up.

Use your Merchant Portal account to create a shared secret key

 

Can I perform load or stress testing in the sandbox? 

The sandbox is for integration tests only and is not provisioned for load or stress tests. We may suspend your sandbox account if we observe unusually high transaction volumes.