SAP Commerce Cloud
Last updated: March 1, 2023
SAP Commerce Cloud Connector integrates seamlessly with the SAP B2C Accelerator. The Connector for SAP Commerce Cloud (formerly Hybris) enables customers to implement a global payment strategy through a single integration in a secure, compliant and unified approach.
We currently support:
- SAP CC 1905, 2005, 2011, and 2105, including B2C Accelerator
- SAP Spartacus 3.2 frontend with server-side rendering (SSR) support, which is compatible with SAP CC 1905, 2005, and 2011
- SAP Spartacus 4.2 frontend with SSR support, which is compatible with SAP CC 2011 and above
This guide explains how to get started with our plugin.
- SAP Commerce Fulfilment process: With Checkout.com's APIs for authorization, capture, refund and void. The same functionality has been brought onto our Spartacus v3.2 storefront connector.
- SAP Commerce Backoffice: The connector provides specific customizations for the back office to ease the administration, configuration and management of all the operations related to the integration with the Checkout.com's payment solution.
- 3DS 2.0 (PSD2): In case of a non-frictionless interaction, the user must enter additional information related to the Strong Customer Authentication (SCA).
- SAP WCMS (Web Content Management System): The connector enables business users to add cards and APMs using CMS components.
- Express checkout: One-click payments with Apple Pay and Google Pay from the Product details page and Cart page.
| Payment method | Countries |
|---|---|
American Express | Global |
Diners | Global |
Discover | Global |
JCB | Global |
Maestro | Global |
Mastercard | Global |
Visa | Global |
If you haven't already, create a test Checkout.com account.
To set up the SAP Commerce Cloud Connector, you'll need three API keys: a secret one, a public one, and a private shared one. The first two are generated automatically when you create your account. The last one is generated when you create a webhook for your business.
- Log in to your test account on the Hub sandbox.
- In the left menu, go to Settings > Channels, and make a note of your secret and public API keys.
- Scroll down to the Webhooks section of the page and select New webhook.
- Enter the following URL, replacing
example.comwith the URL of your shop:example.com/checkout_com/webhook/callback. (A webhook URL specific to your installation is available in the Account Settings section of the plugin configuration panel.)
Note
Correctly configuring your webhooks is important; if they're incorrectly formatted, the plugin will not work.
- Select API - v2.0.
- Tick Select all, then select webhook.
- Click on the webhook you just created, and make a note of the private shared API key.
As summarised by the table below, the visibility (availability) of the payment methods in SAP Commerce Cloud is defined by three attributes:
| Attribute | Description |
|---|---|
CMS Component | For a payment method to be visible, the CMS component related to the payment needs to be added to the CheckoutComPaymentButtonsSlot content slot. If you have multiple sites, the payment should be added for each site. Any payment methods that are not globally accepted by the merchant (irrespective of the customer’s shipping/billing country) should not be added to the CMS component. |
Billing Country | Apart from card payments (which are available for all countries), other payment methods can be configured to have country restrictions applied. If the list is empty, there is no restriction at all. Otherwise, the payment method will be available for customers whose billing country is included in the list. |
Currency | Apart from card payments (available for all countries), other payment methods can be configured to have currency restrictions applied. If the list is empty, there is no restriction at all. Otherwise, the payment method will be available for customers whose shopping cart currency is included in the list. |
- Download the latest Checkout.com SAP Commerce Cloud Connector. This contains the installer recipes and connector extensions.
- Unzip the Connector .zip file.
- Copy the extracted folders to the
HYBRIS_ROOTof your Hybris installation. - Remove the SAP Commerce fulfilment extension
yacceleratorfulfilmentprocessfromlocalextensions.xml, as the connector will handle the fulfilment using thecheckoutfulfilmentprocessextension. - Run the
ant cleancommand from within your Hybrisbin/platformdirectory. - Edit your
localextensions.xmland add the following:
Information
The extensions do not rely on any absolute paths, so you can place the extensions in a different location (such as ${HYBRIS_BIN_DIR}/custom).
- Run the following commands to install the add-ons to the yaccelatorstorefront (you can replace yaccelatorstorefront with your custom storefront).
The Checkout sample data add-on is optional and allows you to add fields to the checkout page, which can be used to gather information from your customers, upsell services and products, and much more. To install:
- Run the following code:
- Run the
ant clean allcommand from within your Hybris bin/platform directory. - Run the
hybrisserver.shcommand to start up the Hybris server. - Update your running system using
ant updatesystem.
After setting up the hosts file, the connector will work initially without any external setup needed, because the Checkout sample data add-on will provide all the required data for the accelerator’s electronics and apparel stores.
Information
The add-ons are independent and can be installed on separate server instances.
The add-on comes with one Gradle recipe to be used with the Hybris installer. The recipe is b2c_acc_plus_checkout_com with b2c and Checkout.com functionality, and is based on the b2b_acc_plus recipes provided by Hybris.
The recipe generates the local.properties file with the properties defined in the recipe. You can choose to add this file to the customconfig folder.
In order to install the add-on using one of the recipes detailed in that folder, run the following commands:
Information
Our SAP Commerce Cloud Connector supports multiple Checkout.com channels, where a different website is connected to each channel. So, if you have multiple websites running on SAP Commerce Cloud, you can have a different configuration for each one and keep the payment transaction separate.
- In the Secret keys tab, enter your public key, secret key, and private shared key.
- In the Global Settings tab, set the environment to Test, so you can start testing payments. (You will need to change this to Production when you're ready to go live.)
- Still in the Global Settings tab, select the payment action you want.
- Authorize will only authorize the charge; you have to manually capture the payment yourself.
- Authorize and Capture means that the charge is authorized and captured (i.e., the money due from the customer's account is moved into your account) at the same time. If you're unsure, Authorize and Capture is probably the right choice.
- In the same tab, there are three more fields you can fill in:
- Review transactions at risk: If true, payment events coming from Checkout.com that have risk flag set to true will be created with transaction status REVIEW. Otherwise, the payment status will be ACCEPTED.
- Authorization amount validation threshold: This is used to determine whether the authorization amount reflects the value of the order. This is the allowed difference of the amounts that may exist due to the way the amounts are calculated. Increase it if you observe false positives in your integration.
- Billing descriptor: If set to true, the payment requests made will contain the billing descriptor name and city you have specified. If false, no billing descriptor will be sent.
That's it! You're ready to start testing card payments.
We will send payment events for all the webhooks configured in the Hub. There should be at least one webhook created (per environment) pointing to the webhook event receiver. Read our webhook documentation for more information.
The connector requires the following events to be sent:
payment_approvedpayment_pendingpayment_declinedpayment_expiredpayment_canceledpayment_voidedpayment_void_declinedpayment_capturedpayment_capture_declinedpayment_refundedpayment_refund_declined
This is reflecting your checkoutComPaymentEventTypes configuration property. If the webhook in the Hub sends more events, they will be ignored by the event receiver.
You can extend your configuration to add more payment methods, accept 3D Secure payments, and more.