Go further with SAP Commerce Cloud
Last updated: November 4, 2022
There are a number of ways you can extend your SAP Commerce Cloud integration to suit your business needs.
In this guide, you'll learn how to:
Additional payment methods
Before you start
In order to start accepting an alternative payment method, we first need to enable it on your account. Please contact your Customer Success Manager or our Sales team to get started.
We currently support the following payment methods on SAP CC:
Check the individual payment method pages to see which ones you can support. Availability will depend on your location, as well as your customer's billing address and currency.
Enable Apple Pay
- Sign in to your SAP CC Administration Console and go to Apple Pay Payments > ApplePay Configuration.
- Enter your merchant name.
- Enter your merchant ID. You can find this in your Apple Developer account.
- Enter your two-letter country code.
- Select which payment capabilities you want to support. Read the Apple documentation for more information.
- Select the payment networks you wish to support. Read the Apple documentation for more information.
- Enter the private key from your merchant identity certificate. You can find this in the contents of the
.key
file in your Apple Developer account. - Enter the public key from your merchant identity certificate. You can find this in the contents of the
.pem
file in your Apple Developer account.
See our Apple Pay documentation for more information.
Enable Google Pay
- Sign in to your SAP CC Administration Console and go to Google Pay Payments > GooglePay Configuration.
- Select which card networks you want to support through Google Pay with the allowed card networks setting. See Google's documentation for more information.
- Select which card authorization methods you want to support through Google Pay with the allowed card authentication methods setting. See Google's documentation for more information.
- Select the environment used for processing payments – either Test or Production. This is not the same as the Checkout.com environment setting.
- The payment gateway defines which gateway Google Pay uses. This should be left as
checkoutltd
. - Enter your gateway merchant ID. You can find this in your Dashboard account.
- Enter your merchant name.
- Enter your merchant identifier. You can find this in your Google payments profile.
- Set Type to CARD. This defines the payment methods supported by Google Pay.
See our Google Pay documentation for more information.
Payment method configuration
The 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 should not be added to the CMS component, regardless of the customer’s shipping or billing country. |
Billing Country | Card payments are available for all countries. You can choose to make other payment methods available only for specific billing countries by supplying them in the list. Countries excluded from the list will not be able to use the alternative payment methods. If the list is empty, no country restrictions are applied. |
Currency | Card payments do not have any currency restrictions applied. You can choose to make other payment methods available only for specific currencies by supplying them in the list. Currencies excluded from the list will not be able to use the alternative payment methods. If the list is empty, no currency restrictions are applied. |
Enable 3D Secure payments
- Go to card payments.
- If you want to process all payments as 3D Secure (3DS) payments, set Use 3D Secure to True.
- Select whether you want to attempt non-3D Secure transactions. If you select True, any cards that do not support 3DS will go through without a 3DS check. If you select False, cards that do no support 3DS will be blocked.
This add-on is compliant with the 3DS 2.0 (PSD2) directive. In case of a non-frictionless interaction, where a customer is required to enter additional information related to Strong Customer Authentication (SCA), the customer will be sent to our hosted solution page. Read our 3DS documentation for more information.