Integrating Cybersource With Chargent In Salesforce

Before you start integrating the Cybersource gateway in Chargent with Salesforce, make sure you have completed the following steps.

Before setting up your gateway, install the latest version of Chargent and configure your user permissions. Guides for these topics are available below to help you get started.

• Installing and Updating Chargent
• License Assignment (Production Only, not required for Sandbox)
• Permission Assignment

Before installing Chargent in production, we highly recommend installing and testing in a Salesforce sandbox. The following topics provide instructions for obtaining your test gateway credentials and creating a test Gateway record in Salesforce. Remember to refresh your sandbox beforehand to ensure that your sandbox is aligned with your production configurations.

If you don’t already have Cybersource credentials for testing, sign up for a Cybersource test account.

If you plan to use tokenization, ensure the ‘Payment Tokenization Service’ has been enabled for your Cybersource Account by contacting Cybersource Customer Support.

Cybersource provides two accounts with separate login credentials: Account Admin and Merchant Admin. The Account Admin is the master account for a specific Merchant ID (MID) and is not used for this integration. After you request your Cybersource Test Account, you’ll receive a confirmation email with links. Click the links to create usernames and passwords for both accounts. 

Chargent only requires the credentials from the Merchant Admin account.

To integrate Cybersource with Salesforce using Chargent, you’ll need to find and save the following credentials, specifically from your Merchant Admin account:

• Merchant ID
• Transaction Security Key (aka SOAP Toolkit Key)

The following sections will provide instructions for finding and saving the above credentials.

The Merchant ID credential is the ‘Organization ID’ under the ‘Merchant-Level User’ section in your account creation email. This credential is also used to log into your Cybersource test account (alongside your User Name and Password).

To find your Transaction Security Key, log in to the Cybersource test business center using your new credentials to generate the key.

1. Log in to your Cybersource test business center.
2. Click Payment Configuration from the left panel.
3. Click Key Management.
4. Click Generate Key.
5. Select SOAP Toolkit.
6. Click Generate Key on the bottom.
7. Click Copy this one-time key icon to copy the key to your clipboard.
   • Please note that the one-time key cannot be retrieved again after you navigate away from this page. We recommend saving the key in a secure location.

The following Cardinal Cruise credentials are required when enabling Strong Customer Authentication (SCA) for your Cybersource integration using Chargent. If your SCA credentials are not present, please see Cybersource’s documentation, How to View Your Cardinal Cruise Credentials.

API Key

The shared secret value between your merchant account and Cybersource’s Cardinal SCA service. This value should never be exposed to the public. This can be found in the Cybersource Customer Portal by visiting Payment Configuration > Payer Authentication Configuration.

API Identifier

This ID indicates the specific API key to be used for this account. This can be found in the Cybersource Customer Portal by visiting Payment Configuration > Payer Authentication Configuration.

OrgUnit ID

This ID indicates the merchant account to be used for Strong Customer Authentication. This can be found in the Cybersource Customer Portal by visiting Payment Configuration > Payer Authentication Configuration.

Before you can create your test gateway in Chargent, you will need to gather the following credentials using the steps above:

• Merchant ID: This is your Cybersource Username.
• Transaction Security Key: Obtained via the steps in the previous section.

With your credentials in hand, it’s time to create a gateway record in Chargent and verify your Cybersource test credentials. 

1. Login to your Salesforce sandbox (partial, full, or developer sandboxes work).
2. Go to the App Launcher and click the Chargent app.
3. Click the Chargent Settings tab and choose the Setup Wizard subtab.
4. Click Yes when prompted, “Do you have a Payment Gateway account?”.
5. Select ‘Cybersource’ from the list and click Continue.

6. Enter your Cybersource sandbox credentials, leaving the Endpoint Override field blank.
7. Click Sign In.
8. Enable or disable Strong Customer Authentication (SCA) based on whether or not you want to include 2-factor authentication for customer purchases.
   • Learn more by visiting Strong Customer Authentication (SCA) in the Supported Features section of this guide.
9. When you receive a message stating “Your credentials have been successfully verified!”, click Sign In to complete the steps in the wizard.
   • If you receive an error message in red, see the Checking Your Remote Site Settings section below or check out our troubleshooting tips.

The remaining choices in the Gateway Setup Wizard are determined by your specific use case. For more detailed information about the steps, see Gateway Setup Wizard.

The remote sites for your gateway should automatically activate when completing the Gateway Setup Wizard. If you encounter any issues connecting to Chargent using your gateway credentials, ensure they have been correctly activated in your org.

1. Click the gear icon at the top right and choose Setup.
2. Enter “remote” in the Quick Find box and choose Remote Site Settings.
3. Locate the following Remote Site names and make sure the “Active” box is selected:

• • CyberSourceLiveA
  • CyberSourceTestA

4. If the “Active” box is not selected, click Edit, select Active, and click Save.

Setting up your direct debit network is optional but recommended. When you reach the gateway setup wizard page labeled “Select the Payment Methods you accept,” select the direct debit network for your region.

Cybersource supports the ‘ACH – US’ direct debit network. Choosing the correct Direct Debit Network will allow you to accept Bank Account payments and display the correct Direct Debit Network fields in Chargent.

For more information, see Understanding Bank Account Payments.

Once you’ve tested your gateway integration in a Salesforce sandbox, you’re ready to move to production! See Moving from Sandbox to Production to learn how to migrate your Chargent configuration changes to your production environment. After moving Chargent to production, see Testing in Production for best practices prior to going live.

To process real payments in Cybersource, contact Cybersource’s Sales Team to migrate your test Cybersource account to a production Cybersource account.

If you plan to use tokenization, ensure the ‘Payment Tokenization Service’ has been enabled for your Cybersource Account by contacting Cybersource Customer Support.

So far, you’ve used your test Cybersource credentials and created a test gateway in your Sandbox. Now, it’s time to create a new gateway record in your production environment specifically for processing live transactions.

1. Log in to your production Salesforce org.
2. Go to the App Launcher    and click the Chargent app.
3. Click the Chargent Settings tab and choose the Setup Wizard subtab.
4. Click Yes when prompted, “Do you have a Payment Gateway account?”.
5. Select ‘Cybersource’ from the list and click Continue.
6. Click Live Transactions and enter your new live gateway credentials, leaving the Endpoint Override field blank.

7. Enable or disable Strong Customer Authentication (SCA) based on whether or not you want to include 2-factor authentication for customer purchases.
   7. Learn more by visiting Strong Customer Authentication (SCA) in the Supported Features section of this guide.
8. Click Sign In.
9. When you receive a message stating “Your credentials have been successfully verified!”, click Continue to complete the steps in the wizard.
   • If you receive an error message in red, see our troubleshooting tips.

For more detailed information about these steps, see our documentation for the Gateway Setup Wizard.

With your live gateway record created, you are ready for the final phase of testing: running live transactions in a production environment. Visit Testing in Production for considerations and best practices related to testing in your production environment.

When testing with live payment information, you can prevent transactions from settling by voiding them immediately afterward. For more information, see Refunding and Voiding Transactions. As a precaution, we recommend using very low amounts to minimize any impact in the event you forget to void them.

To test gateway responses in the live environment, submit live transactions with the correct street address, zip code, and CVC information to generate successful responses. Likewise, submit incorrect street address, zip code, and card code information to generate other responses. You can void successful transactions immediately to prevent live test transactions from being processed.

Congratulations! You have successfully integrated Salesforce and Cybersource! You can now process transactions through Cybersource directly in Salesforce using Chargent!

All of Chargent’s gateway integrations support most of Chargent’s core features. Some features are reliant on support by the gateway itself. Chargent’s integration with Cybersource includes, but is not limited to, the following features:

Using Cybersource, you can validate US bank accounts on the Automated Clearing House (ACH) network via our partner, Lyons, a leading data verification provider. This feature is designed to satisfy NACHA’s mandate—Supplementing Fraud Detection Standards for Web Debits.

For more information, see ACH Validation.

Chargent’s integration with Cybersource supports Address Verification System (AVS), a technology used to prevent fraud by validating the ownership of a credit card using the billing address of a credit card and matching it with the data on file at the credit card issuing company.

Your AVS results are stored in Salesforce using the AVS Response Code field on your transaction record. For code definitions, see Cybersource’s AVS Codes.

For more information, see Address Verification System (AVS).

Chargent’s integration with Cybersource supports multiple currencies. Visit ISO Standard Currency Codes for a list of currencies supported by Cybersource.

Additionally, this gateway integration supports Salesforce’s Multiple Currencies feature.

For more information about currencies in Chargent, see Understanding Currencies.

Data levels allow you to send more information with each transaction, ensuring the security and authenticity of the payment. Higher data levels translate to higher savings on transaction fees. The following levels of data are supported by Cybersource using Chargent:

• Level I

For more information about data levels, see Understanding Data Levels.

Below, we’ve listed the payment method types that are supported when using the Cybersource gateway integration. For more information about payment methods supported by Chargent, see Payment Methods Supported.

Credit Cards

• Visa
• Mastercard
• Discover
• American Express
• UK Maestro
• JCB Card
• Diners Club

See Cybersource’s documentation about Card Types for a list of credit card types supported by Cybersource. You can also check out Understanding Credit Card Payments to learn more about how credit card payments work in Chargent.

Bank Accounts

• ACH – US (aka echeck or electronic check)

For more information, see Understanding Bank Account Payments.

Chargent’s Cybersource integration supports Stand-Alone Credits (aka Unlinked Refunds). A Stand-Alone Credit allows you to send funds from your Cybersource account to a credit card. Unlike a Refund, an Unlinked Refund has no time limitation and can be processed when no prior transaction has occurred.

Stand-Alone Credits are not automatically enabled for your Cybersource account. See How to Apply for Permissions to Perform a Stand-Alone Credit (SAC).

Chargent refers to Stand-Alone Credits by their common name, Unlinked Refunds. For more information about enabling and processing Stand-Alone Credits, visit Sending Unlinked Refunds.

Strong Customer Authentication (SCA) is a two-factor authentication (2FA) requirement wherein, during a consumer-initiated transaction, the cardholder must provide two of the three elements: something the cardholder knows, something the cardholder owns, something the cardholder is.

With SCA enabled, a pop-up window will appear when your customers make a payment via Payment Request or Take Payment, asking them to authenticate with 2FA, adding an additional layer of security to your customer-initiated transactions.

See the following related documentation:

• Obtaining Your SCA Credentials
• Testing SCA Credit Card Transactions
• What is Strong Customer Authentication (SCA)?

Surcharging represents a growing trend in the payment industry, allowing you to pass your credit card fees on to your customers. Chargent has partnered with InterPayments, a leader in the surcharging space, to help you take control of your credit card fees and improve your Salesforce payment process.

To learn more, see Setting Up Surcharging.

Tokenization allows you to store payment information at your gateway and not in Salesforce. Tokenization helps you decrease the scope of your PCI compliance and improve security by storing your customers’ payment information on Cybersource’s servers and not in Salesforce.

Chargent’s Cybersource integration supports tokenization for the following payment method types:

• Credit Card
• Bank Account

In Cybersource, the token is stored as a Profile ID, which is returned to Salesforce and stored in the Token field on the Chargent Order and Tokenization on the Transaction records in Salesforce. Additionally, tokens are stored in a Chargent Tokens record when Payment Methods is enabled in your org.

Contact Cybersource Support to ensure that the ‘Payment Tokenization Service’ is enabled for your Cybersource account.

To learn more, visit Understanding Tokenization.

Chargent’s integration with Cybersource supports the following transaction types:

• Authorize
• Capture
• Partial Capture
• Refund
• Partial Refund
• Unlinked Refund (Stand-Alone Credit)
• Refund Authorization

For more information about Transaction Types, see Understanding Payments and Cybersource’s documentation, What are the transaction types that can be submitted?

Salesforce sends payment information to your gateway based on the field values in your Chargent Order records. The gateway stores the payment information as a transaction. Then, the gateway sends a response to Salesforce, storing it in a Transaction record. Here are a few important examples of how the data is mapped between Salesforce and Cybersource.

For customizable field mapping options, see Cybersource Custom Mapping.

The Order Source field can be set for ACH transactions and determines the SEC code sent to Cybersource. The following table provides the mapping between the Order Source field on the Chargent Order record and the corresponding SEC code in Cybersource.

Chargent also uses the Order Source field to set the CommerceIndicator for register token calls when using Cybersource. The values in the Order Source field are mapped to the CommerceIndicator value in the Cybersource SOAP API. The following table displays the mapping from Order Source to CommerceIndicator:

Chargent’s Cybersource Custom Mapping feature allows you to send values from almost any fields on the Chargent Order object to the Cybersource gateway using Cybersource’s Merchant-Defined Data fields.

The feature is not required for processing Cybersource payments but allows you to store additional information within Cybersource. Custom Mapping is designed to send up to 20 fields in a request. Any fields on the Chargent Order object can be selected – including Chargent’s packaged fields or custom fields you’ve created.

Cybersource doesn’t allow you to send Personal Identifiable Information (PII) to Merchant Defined Data fields, including name, address, credit card number, etc. See the Merchant-Defined Data Fields section in Cybersource’s Managing Merchants documentation for more information.

1. Go to the App Launcher and click the Chargent app.
2. Click the Chargent Settings tab.
3. Click the down arrow to the right of Global Settings and choose the Cybersource Custom Mapping subtab.
4. In the Select Object picklist, select ‘Chargent Orders’.
5. Select a field from the Chargent Order (presented in the left column) and a field for mapping in Cybersource (presented in the right column).
6. (Optional) Click + to the left of the Chargent Order field to add additional field mappings.
7. Click Save.

One Chargent Order field can be mapped to one or more Cybersource custom fields. The mapped fields are sent in ‘Authorize’ and ‘Charge’ requests. In Cybersource, the fields are shown on the detailed transaction description page:

If you have questions about Cybersource Custom Mapping, please feel free to contact us.

The Reason Code field on a Transaction record stores a response code provided by Cybersource. To learn more about a specific response code, see What Does this Reason Code Mean? or search Cybersource’s Transaction Response Codes.

To review gateway responses in Salesforce, go to the transaction record in Chargent and examine these field values:

The following considerations are specific to Cybersource. Please let us know if you have any questions about the following items.

Payment Request Limitation

Our Cybersource integration does not allow customers to choose their payment method (Credit Card or Bank Account) in Payment Requests out of the box. This is due to Cybersource’s SEC code requirements relating to the payment method for each transaction.

For more information, see Cybersource: Why can’t my customer choose their payment method in Payment Request pay forms?

Error 150

If you attempt to use tokenization, but tokenization is not enabled in Cybersource, you may receive an error 150. This error can also be related to setting an incorrect value in the Order Source field on the Chargent Order record.

For more information, see Cybersource: 150- Error – General system failure.

Disabling AVS

There is no way to disable AVS in Cybersource; however, Cybersource has two features that can be enabled by request.

• ‘Relaxed AVS’ allows you to change address fields that are typically required to optional.
• ‘Ignore AVS’ will ignore all AVS responses from Cybersource.

For more information, see Turning off Cybersource Address Verification System (AVS).

If you are having trouble connecting to your gateway, we recommend starting with these troubleshooting steps.

For additional troubleshooting tips or frequently asked questions about Cybersource, check out Chargent’s knowledge base articles.

For general information about Cybersource, go to http://www.cybersource.com.

For sales questions about any Cybersource service, email [email protected] or call 650-432-7350 or 888-330-2300 (toll-free in the United States).

For support information about any Cybersource service, visit the Support Center: http://www.cybersource.com/support

Contact our support team if you encounter any Chargent issues with your implementation.

Chargent Quick Start Guide
Gateway Setup Overview
Supported Gateways