RELATED TO THIS PAGE

ON THIS PAGE

Product overview

Cybersource Payment Management for clients using Salesforce Order Management. The integration for Salesforce Order Management is written in REST and supports capture and credit calls for Credit/Debit Card Payments, PayPal, Apple Pay and Google Pay.

  • Capture and credit calls for
    • Credit Card Payments
    • PayPal
    • Apple Pay
    • Google Pay.

Product editions

Available in Professional, Enterprise, Unlimited and Developer Salesforce Editions

  •  

 

For organistations using Salesforce Lightning Ready

Getting started

Prerequisites - Salesforce– In order to use the Cybersource for Lightning Order Management please make sure you have an active instance of Salesforce with an Order Managment subscription. 
 

a.       Make sure that Lightning Experience is enabled

b.       Purchase and activate an Order Management license. A license is included with a developer org or when you’re using a partner-approved Order Management template ID to create a trial org

c.       For general information about Order Management concepts, objects, and records, see Salesforce Order Management Help (salesforce.com).

Prerequisites - Cybersource

Create REST Keys

a.       Sign into your Cybersource Business Center account (Live) or (Test)

b.       Access Payment Configuration -> Key Management

c.       Select the 'Generate Key' button in the top right hand corner

d.       Select your key type as 'REST - Shared Secret Key' and Generate Key

e.       Copy your KeyID and Shared Secret Key values and save them securely

 

Install the managed package

Install the managed package from the Salesforce App Exchange (https://appexchange.salesforce.com) and search for 'Cybersource for Lightning Order Management'.

Create a Payment Gateway Provider

Creating a Payment Gateway Provider is not supported fromt the UI and needs to be done through workbench by conntecting to your organisation.

1.     Endpoint to be used - (MD/ToolingAPI):

        /services/data/v48.0/tooling/sobjects/PaymentGatewayProvider

2. Payload :   

                {

            "ApexAdapterId":< ID of PTS_PaymentAdapter.cls apex class>,

            "DeveloperName":"Cybersource_Provider",

            "MasterLabel":" Cybersource_Provider ",

            "IdempotencySupported":"Yes",

            "Comments":"Comments"

 }

Create a Named Credentials Record

The package comes with a default names credential Payment which points to Cybersource's test endpoint https://apitest.cybersource.com.

To create your own Named Credential

  1. Click Setup
  2. In the quick find box enter Named Credentials
  3. Click New
  4. Complete the fields presented noting the following:

   5.   Click Save

 

Create a Payment Gateway Record

  1. Click on App Launcher  > Payment Gateways
  2. Click New
  3. Enter the following details
  • Payment Gateway Name - name the payment gateway
  • Payment Gateway Provider - Name of the payment gateway provider created in Step 2
  • Merchant Credential - The Named Credential created in Step 3
  • Status - Set to Active to activate the payment gateway
  • External Reference - This value will be the Processor ID from your Salesforce Commerce Cloud instance

   4.  Click Save

Create a Payment Configuration Record

If you support multi-site configuration for different Merchant ID then create separate records for each Merchant ID and each sales channel

  1. Go to Setup
  2. In the quick find box, enter “Custom Metadata Types”
  3. Click on “Payment Configuration (Managed)”
  4. Click on “Manage Payment Configurations”
  5. Click on “New”
  6. Enter the required details
  • Label - should match the Salesforce Commerce Cloud site ID.  See Administration->Sites->Manage Sites for the value
  • Payment Configuration Name - Preferably the same value as Label
  • Merchant ID
  • End Point - TEST or PRODUCTION
  • REST Key ID
  • REST Shared Key

   7.   Click Save

Note Payment_Confg__c custom object has been deprecated from “Cybersource for Lightning Order Management” so don’t create any record in this object.

 

Test and Go Live

Before you start accepting payments, test your integration in Test sandbox:

The sandbox simulates the live payment gateway. The sandbox never processes an actual payment. We do not submit sandbox transactions to financial institutions for processing. The sandbox environment is completely separate from the live production environment, and it requires separate credentials. If you use your production credentials in the sandbox or vice versa, you get a 401 HTTP error.

Test your integration, and configure your live account, so you can start processing live transactions.

Ready to Go Live

  1. Install the managed packaged in Production Org.
  2. Create a new Payment Gateway Provider record in your Production Org by following steps in Step 2.
  3. Create a new named credential – “Payment_LIVE” in your Production Org by following steps in Step 3.
  4. Create a new Payment Gateway record in your Production Org by following steps in Step 4.
  5. Create a new Payment Configuration custom metadata record in your Production org by following steps in Step 5. If you support multi-site configuration for different Merchant ID then create separate records for each Merchant ID and sales channel.  Make sure the Endpoint field has Production selected.