RELATED TO THIS PAGE

ON THIS PAGE

Product overview

SAP Commerce Cloud is a powerful eCommerce solution. It brings together marketing, sales, service and billing. The Cybersource payment integration gives you a modular architecture that’s easy to extend so you can decrease development time and costs. And it’s flexible enough to build solutions that are just right for your industry and marketplaces.
 


Smartpay Fuse is a Barclaycard Payments product that has been developed in collaboration with Visa and Cybersource. Plugin integrations may be branded as Visa or Cybersource rather than Barclaycard Payments, and form part of the Smartpay Fuse ecosystem. The features outlined on this page reflect those commercially available for use with Smartpay Fuse. Plugin downloads may include additional functionality that is not part of the Smartpay Fuse commercial offering.

 

 

  • The SAP Commerce plugin provides an integration layer between SAP Commerce platform and the payment provider API.
  • The plugin consists of a set of SAP Commerce platforms extensions that cover backend and frontend integration aspects.
  • Frontend extensions are built on top of Spring MVC (Model View Controller) framework as part of SAP Commerce Platform. It uses standard SAP Commerce B2C and B2B Accelerators which are part of SAP commerce deployed on premise or in the SAP Cloud.
  • More details on SAP Commerce accelerators can be found here.  

  • Integration Features:
    • REST API
    • SOAP API
    • Secure Acceptance
    • Microform
    • 3DSecure  
  • Channels:
    • eComm (CNP)
    • In-App
  • Payment Methods:
    • Visa
    • MasterCard
    • Maestro
    • American Express
    • Apple Pay
    • Google Pay*
    • Discover
    • Diners
    • Visa Click-to-Pay
    • PayPal
      • Express Checkout
      • Credit
    • Klarna
    • Alipay
    • iDEAL
    • Sofort
    • Bancontact
    • EPS
    • WeChat
  • Payment Functions:
    • Authorisation
    • Capture
    • Sale
    • Void
    • Full Refund
    • Partial Refund
    • Full Reversal
    • Follow on Credit
    • Standalone Credit
    • Token Management Services (CIT & MIT)
    • Level II/Level III Data
  • Fraud Management:
    • Decision Manager
    • Advanced Screening
    • Device Fingerprint ID

*Google Pay transactions via a non-Android device may not invoke the Payer Authentication journey for your customer. If you choose to proceed with an individual non-secure transaction, please be aware that you may lose any liability shift protection that would usually be provided by Payer Authentication.

Getting started

SAP Prerequisites

Before beginning installation of the SAP Commerce Plugin the following components are required:

  • An instance of the SAP Commerce platform v2011
  • The SAP Commerce plugin available in the Cybersource Gihub
  • Java 11
  • Required Dependencies installed in maven repository
     

Smartpay Fuse Prerequisites 

You will be able to configure this integration to either Test or Production. If you do not yet have a live Smartpay Fuse  account, or you wish to first test the integration, then creating a sandbox account will not only allow you to start programmatic integration but also provides access to the Smartpay Fuse Portal.

  1. Visit our sandbox creation page here.
  2. Complete the registration form.
  3. Click submit to create your sandbox account.

Note: on submitting your application, you will receive an automated email from our partner, Cybersource, with first time login and password reset instructions. Be sure to check your junk mailbox if this doesn’t arrive within 2 minutes of clicking Submit.

Generate SOAP Keys

Before configurating this integration, you are required to generate your SOAP .p12 keys within your Smartpay Fuse Portal for both (Live) and (Test).

  • Sign into your Smartpay Fuse Portal account (Live) or (Test).
  • Access Payment Configuration -> Key Management
  • Select the 'Generate Key' button in the top right hand corner
  • Select your key type as 'Simple Order API' and Generate Key
  • Select Download Key, and save a password.
  • Complete the download, and save your key securely.

 



  1. There are two types of installation: using step by step approach or by using a custom recipe that will manage most of the work.
  • For using a custom recipe follow this flow (see Step 3)
  • For Step By Step (manual approach) follow this flow (see Step 4)

Custom Recipe Installation steps:


SAP Commerce payment extension installation process is based on OOTB build approach. The approach is based on copying files in appropriate locations by adding minimal required configuration properties through local.properties file.

1. Obtain SAP Commerce Suite 2011 release package and unzip it into the appropriate location.

    $unzip sap-commerce-suite-2011.zip -d sap-commerce-suite-2011
 

2. Copy the payment extensions to SAP Commerce release, following the default folder structure.

    $unzip sap-commerce-payment-plugin.zip -d sap-commerce-suite-2011


3. Configure the merchant data.

Update the configuration files by providing your payment merchant configuration. To do this please find the configuration template files having extension ".tpl", rename them to "*.impex" and edit them by adding merchant details for each Payment Method.

    $cd sap-commerce-suite-2011/hybris/bin/isvpaymentsampledata/

    $cd /resources/isvpaymentsampledata/import

For each payment method:

    $mv merchant_payment_configuration.impex.tpl merchant_payment_configuration.impex

    $mv cronjobs.impex.tpl cronjobs.impex

Note: not all payment methods provide cronjobs.impex.tpl — if absent, skip the step above.

Considering REST APIs are being used by Reporting functionality the following merchant specific configuration should be provided.

    # For TEST environment use "Cybersource.Environment.SANDBOX"

    # For PROD environment use "Cybersource.Environment.PRODUCTION"
isv.payment.api.rest.runEnvironment=Cybersource.Environment.SANDBOX

   # HTTP_Signature = http_signature and JWT = jwt
    isv.payment.api.rest.authenticationType = http_signature

   # HTTP Parameters
   # The credentials below MUST be provided in case "isv.payment.api.rest.authenticationType=http_signature"

isv.payment.api.rest.<merchant_id>.merchantKeyId = <merchantKeyId>
isv.payment.api.rest.<merchant_id>.merchantsecretKey = <merchantsecretKey>

    # JWT Parameters
    # The credentials below MUST be provided in case "isv.payment.api.rest.authenticationType=jwt"
    isv.payment.api.rest.<merchant_id>.keyAlias = <merchant_id>
    isv.payment.api.rest.<merchant_id>.keyPass = <merchant_id>
    isv.payment.api.rest.<merchant_id>.keyFileName = <merchant_id>
    # P12 key path. Enter the folder path where the .p12 file is located.
    isv.payment.api.rest.<merchant_id>.keysDirectory = isvpayment/keys

 

4. The payment extension package provides two recipes for installation in B2C or B2B storefronts. Execute recipes with install.sh (Unix/Mac) or install.bat (Windows).

    Installation for b2c storefront:

    $cd sap-commerce-suite-2011/installer
    $./install.sh -r b2c_acc_isv
    $./install.sh -r b2c_acc_isv initialize

    Installation for b2b storefront:

    $cd sap-commerce-suite-2011/installer
    $./install.sh -r b2b_acc_isv
    $./install.sh -r b2b_acc_isv initialize

OOTB SAP Commerce configured apparel storefronts (this is b2c storefront) to respond to dns names, which should be added into hosts file, this is more reliable than using IP addresses.

Open hosts file for editing and add the following line:
    127.0.0.1 apparel-de.local apparel-uk.local   

For b2b storefront (powertools) add following entry:
    127.0.0.1 powertools.local


5. Start the platform.

For b2c:

    $./install.sh -r b2c_acc_isv start

For b2b:

    $./install.sh -r b2b_acc_isv start

Verify the installation by opening the relevant URL — the storefront home page should load.

    For b2c:

    https://apparel-uk.local:9002/yb2cacceleratorstorefront

    For b2b:

    https://powertools.local:9002/yb2bacceleratorstorefront

Step by Step Installation - Manual Approach

 

1. Obtain SAP Commerce suite 2011 release package and unzip it into appropriate location.

    $unzip sap-commerce-suite-2011.zip -d sap-commerce-suite-2011

2. Install B2C components with accelerator storefront, that includes apparel store as sample data.

    $cd sap-commerce-suite-2011/installer
    $./install.sh -r b2c_acc
    $cd ..

    Note: If you need b2b functionality use b2b_acc recipe.

3. Generate a separate storefront extension from yacceleratorstorefront template, using OOTB extgen tool.

    For B2C:

    $cd hybris/bin/platform
    $. ./setantenv.sh
    $ant extgen -Dinput.template=yacceleratorstorefront -Dinput.name=yb2cacceleratorstorefront -Dinput.package=de.hybris.platform.yb2cacceleratorstorefront

    For B2B:

    $cd hybris/bin/platform
    $. ./setantenv.sh
    $ant extgen -Dinput.template=yacceleratorstorefront -Dinput.name=yb2bacceleratorstorefront -Dinput.package=de.hybris.platform.yb2bacceleratorstorefront

4. Copy payment extensions to SAP Commerce suite, following default folder structure.

    $unzip sap-commerce-payment-plugin.zip -d sap-commerce-suite-2011

5. Add and configure payment extensions in localextensions.xml. This file contains all extensions used by the platform on startup.

    $vim ../../config/localextensions.xml

    For B2C, add the following extensions at the end of localextensions.xml:

    <extension name='isvpayment' />
    <extension name='isvpaymentaddon' />
    <extension name='isvb2cpaymentaddon' />
    <extension name='isvpaymentsampledata' />
    <extension name='isvfulfilmentprocess' />
    <extension name='yb2cacceleratorstorefront' />

    For B2B, add the following extensions at the end of localextensions.xml:

    <extension name='isvpayment' />
    <extension name='isvpaymentaddon' />
    <extension name='isvb2bpaymentaddon' />
    <extension name='isvpaymentsampledata' />
    <extension name='isvfulfilmentprocess' />
    <extension name='yb2bacceleratorstorefront' />

    Remove the following existing extensions from localextensions.xml:

    <extension name='yacceleratorfulfilmentprocess' />
    <extension name='yacceleratorstorefront' />

6. Payment extensions require Java 11. Add merchant-specific properties to local.properties to configure credentials for commands and reporting.

    $vim ../../config/local.properties

    Add the following properties at the end of the file:

    build.source=11.0
    build.target=11.0
    site.pci.strategy=FLEX

    # For TEST environment use "Cybersource.Environment.SANDBOX"
    # For PROD environment use "Cybersource.Environment.PRODUCTION"    isv.payment.api.rest.runEnvironment=Cybersource.Environment.SANDBOX

    # HTTP_Signature = http_signature and JWT = jwt
    isv.payment.api.rest.authenticationType = http_signature

    # HTTP Parameters

    # The credentials below MUST be provided in case "isv.payment.api.rest.authenticationType=http_signature"
    isv.payment.api.rest.<merchant_id>.merchantKeyId = <merchantKeyId>
    isv.payment.api.rest.<merchant_id>.merchantsecretKey = <merchantsecretKey>

    # JWT Parameters

    # The credentials below MUST be provided in case "isv.payment.api.rest.authenticationType=jwt"    isv.payment.api.rest.<merchant_id>.keyAlias = <merchant_id>
    isv.payment.api.rest.<merchant_id>.keyPass = <merchant_id>
    isv.payment.api.rest.<merchant_id>.keyFileName = <merchant_id>
    # P12 key path. Enter the folder path where the .p12 file is located.
    isv.payment.api.rest.<merchant_id>.keysDirectory = isvpayment/keys

7. Install payment add-ons to enable payment functionality without modifying the accelerator storefront directly.

    For B2C:

    ant addoninstall -Daddonnames="isvpaymentaddon,isvb2cpaymentaddon" -DaddonStorefront.yacceleratorstorefront="yb2cacceleratorstorefront"

    For B2B:

    ant addoninstall -Daddonnames="b2bacceleratoraddon,isvpaymentaddon,isvb2bpaymentaddon" -DaddonStorefront.yacceleratorstorefront="yb2bacceleratorstorefront"

    Note: b2bacceleratoraddon is the OOTB SAP Commerce addon for B2B functionality. If you have already installed this addon, omit it from the command above.

8. OOTB apparel storefront is configured to respond to DNS names, which should be added to your hosts file.

    For B2C:

    127.0.0.1 apparel-de.local apparel-uk.local

    For B2B:

    127.0.0.1 powertools.local

9. Initialize and start the platform.

    $ant initialize
    $./hybrisserver.sh

    Verify the installation by opening the relevant URL — the storefront home page should load.

    For B2C:

    https://apparel-uk.local:9002/yb2cacceleratorstorefront

    For B2B:

    https://powertools.local:9002/yb2bacceleratorstorefront

 

Further Information

Testing Guide landing page can be found here
Generic test card numbers (no 3DS) can be found here
3DS testing use cases can be found here
Information on PCI-DSS for each of the integration options can be found here