Salesforce Commerce Cloud | Visa Acceptance Developer Portal

Product overview

The Visa Acceptance LINK Cartridge for Salesforce Commerce Cloud makes the technical side of things far less complicated. This means you can help keep deployment time and disruption to a minimum and you can get up and running quickly.

Card Payments
3D Secure (SCA Compliant)
Tokenisation
Visa Checkout
Google Pay
Apple Pay
eCheck/ACH
PayPal
Klarna
Online Bank Transfers
Fraud Prevention Tools
Utilises Microform to support SAQ-A PCI compliance
Global Tax Calculation
Delivery Address Verification Services

Product editions

Available in Professional, Enterprise, Unlimited and Developer Editions running SFRA 6.3 and below

Getting started

Prerequisites - Salesforce– In order to use the Visa Acceptance Storefront Reference Architecture cartridge please make sure you have an active instance of Salesforce and you have install and configure the SFRA app_storefront_base cartridge.
Requirements:

Salesforce Commerce Cloud subscription
Store Front Reference Architecture (SFRA) app_storefront_base cartridge

For general information about Commerce Cloud and SFRA, see the Salesforce B2C Commerce Infocentre (salesforce.com).

Prerequisites - Visa Acceptance

Create REST Keys (required for Microform)

a. Sign into your Visa Acceptance 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

Create SOAP Keys (required for all integrations)

a. Sign into your Visa Acceptance 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 'SOAP Toolkit' and Generate Key

e. Copy the Secret Key value and save them securely

Setup Workspace

Create a 'Visa Acceptance' folder in your workspace and place the cartridge int_Visa Acceptance_sfra (int_Visa Acceptance for controller version) that was downloaded from the marketplace in Step 2

Note if you have a different project setup you will need to open the file /package.json and modify the paths.base value to point to your app_storefront_base cartridge. This path is used by the JS and SCSS build scripts.

If using VSCode, install the extension Phrophet Debugger link or any other SFCC extension and include the following in dw.json().

                {
  "hostname": "your-sandbox-hostname.demandware.net",
  "username": "yourlogin",
  "password": "yourpwd",
  "version": "version_to_upload_to",
  "cartridge": [
              "int_cybersource_sfra",
              "app_storefront_base",
              "modules"
  ]
}

Note if you are using a different IDE please refer to the respective developer guide to setup the workspace.

Build and Upload Code

Prerequisite: Install node under Visa Acceptance folder

Install sgmf-scripts and copy-webpack-plugin with the following command

                npm install sgmf-scripts && npm install copy-webpack-plugin

Compile the JS and SCSS code with the following command

                npm run compile:js && npm run compile:scss

Upload the code to your Salesforce Commerce Cloud instance

                npm run uploadCartridge

Configure the Cartridge

Setup the Cartridge path

Go to settings within Business Manager (Administration > Sites > Manage Sites > [your site] > Settings
For Cartridges enter int_Visa Acceptance_sfra:app_storefront_base then select apply

Upload metadata

Go to folder Visa Acceptance/metadata/sfra_meta/sites/
Rename yourSiteID folder name to your site ID - this can be looked up in Administration > Sites > Manage Sites
Zip the sfra_metadata folder
Upload sfra_meta.zip using Site Import & Export - Administration > Site Development > Site Import & Export
Import the uploaded zip file

Upon successful import the following metadata is created:

Site Preferences (Visa Acceptance, Visa Acceptance_SecureAcceptance, Visa Acceptance_Paypal, Visa Acceptance_GooglePay, Visa Acceptance_Klarna, Visa Acceptance_VisaCheckout, Visa Acceptance_BankTransfer, Visa Acceptance_PayerAuthentication, Visa Acceptance_WeChat, Visa Acceptance_Tokenization, Visa Acceptance_TaxConfiguration, Visa Acceptance_DeliveryAddressVerification, Visa Acceptance_DeviceFingerprint, Visa Acceptance_Alipay)
Service (Visa Acceptance.conversiondetailreport, Visa Acceptance.soap.transactionprocessor.generic, Visa Acceptance.http.flextoken)
Payment Processor (KLARNA_CREDIT, Visa Acceptance_ALIPAY, BANK_TRANSFER, Visa Acceptance_WECHAT)
Payment Method
Job (Visa Acceptance: Decision Manager Order Update)

Add Keys and Enable Cartridge

Navigate to Merchant Tools > Custom Preferences > Visa Acceptance Core to add your Visa Acceptance Merchant ID and keys, set the desired endpoint (test/production), and to enable the cartridge.

Additional custom preferences can be configured in Merchant Tools > Custom Preferences

Configure Payment Methods

Navigate to Merchant Tools > Ordering > Payment Methods and select CREDIT_CARD to select the card capture method. Confirm that Payment Processor = Visa Acceptance_CREDIT before proceeding.

To set Microform as thecard capture mechanism, navigate to Merchant Tools > Site Preferences > Custom Preferences > Visa Acceptance_SecureAcceptance, and set Secure Acceptance Type as SA_FLEX. Add your REST keys to Secure Acceptance Flex Shared Secret and Secure Acceptance Flex KeyId, then select the CS Transaction Type according to your preference.

Although we have added flexible integration options, we recommend utilising our Microform solution for capturing card details, this provides a full PCI-A Solution whilst offering flexibility around your chosen UI.

Please refer to the user guide available with the downloaded cartridge for full guidance on configuring all payment methods and additional features.

Ready to Go Live

When you are ready to go live configure the cartridge using your production Visa Acceptance account details. Please refer to step 5 for a reminder on where to do this.