Adding a Cybersource Connection

Adding a Cybersource connection to your BR-DGE retail channel requires you to collect some information for us to add to your BR-DGE retail channels. This article details the information BR-DGE requires, and how you can locate it.

Cybersource Account

If you don't already have a Cybersource Account, you can create a Sandbox account with Cybersource. For a Cybersource Production account, you must contact their Sales Team.

BR-DGE requires the following information to allow you to route payments to Cybersource through our platform:

• Merchant Id
• Rest API Key
• Rest API Shared secret

Please note that some of these details are sensitive. We ask you to handle these with care.

• How to locate your Merchant Id?
• Login to the Cybersource Portal.
• On the portal main page, there is a banner at the top with configuration details.
• The value for Merchant Id is the value in this banner for Transacting ID.

• How to create your Rest API Key and Shared secret?
• Login to the Cybersource Portal. 
• Select Payment Configuration > Key Management.
• Click on Generate Key button.
• In the Create Key window, select REST - Shared Secret and click Generate key.
• In the next window copy or download the Rest API Key and Shared Secret.

Cybersource Account 3-D Secure Prerequisites

Your Cybersource Merchant ID must be configured specifically for 3-D Secure 2.x.

Your Cybersource Merchant ID must be setup with three credentials, provided by Cardinal Commerce. These will be visible in the Enterprise Business Center when set up.

These credentials must be present in your Cybersource account for 3DS Direct to work correctly. These are NOT required to be sent on to BR-DGE but must be configured;

• API Identifier - A non-secure value that should be passed within the JWT under the iss claim.
• Org Unit ID - A non-secure value that should be passed within the JWT under the OrgUnitId claim.
• API Key - A secure value that should never be rendered or displayed anywhere within a browser/mobile app. This value must only ever be stored on the merchant server. The API Key is used to sign the JWT initialize the connection to Cardinal Commerce, and to verify the JWT signature received back from Cardinal.
• Please review this Cybersource article to see how to verify if you have 3-D secure configured.

Contact the Cybersource Support team to ensure that the Merchant ID is configured for 3DS2 and the above credentials are in place correctly.