Gestpay becomes Axerve Ecommerce Solutions


Merchants who want to use Axerve Ecommerce Solutions within their products must first register and create an account with Axerve Ecommerce Solutions.

The integration of Axerve Ecommerce Solutions on Salesforce Commerce Cloud is offered as a generic cartridge and allows you to use different payment methods, which are described in the next section.

Available payment methods

The cartridge provides a new Payment Processor and enables different payment methods:


Below is a list of the features available to merchants using Axerve Ecommerce Solutions on Salesforce Commerce Cloud:

Web services

The Axerve Ecommerce Solutions cartridge interacts with two web services:

Axerve Ecommerce Solutions Backoffice merchant configuration

The documentation for creating a merchant account can be found here.


Under Configuration > Security you can create the API to enable communication between the Salesforce Commerce Cloud sandbox and the Axerve Ecommerce Solutions Backoffice.

It is not necessary to activate the IP security level, since by activating the API Key it is possible to use this connection mode in the different applications (sandbox SFCC test, development, staging).

In the Configuration > Environment section, fields are available to specify the URLs to which the customer should be redirected depending on the payment outcome:

After completing the previous steps, it is necessary to go to Payment Page > Fields and Parameters section and enter your custom parameter PAYMENT_INSTRUMENT_UUID.

This parameter is needed to identify the payment method used and associate it with the relevant order, since a single Salesforce order could be paid for using several payment methods (credit card, PayPal, discounts, etc.).

Click on Add parameter:

You will see the following screen:

It will then be necessary to enable three parameters: TOKEN, Token ExpiryMonth and Token ExpiryYear.

Another custom parameter that must be added is the SITE parameter, as below.

A parameter that must be added is LOCAL:

Cartridge Installation Guide

Installation from Zip file and update

Extract the contents of the file and copy the link_gestpay_5.1.8 folder (renamed link_gestpay in the following sections) into the project root.

Note: if you update the cartridge version, you must import all services and payment methods and repeat the compilation steps.

Front-end compilation

In order to use the Axerve Ecommerce Solutions cartridge, it is necessary to install NodeJS 8+ on your device. The cartridge works independently and does not require anything else.

After copying the link_gestpay folder into the project root, open the terminal in the link_gestpay folder and run the npm install command. Once the above is complete, build the cartridge using the npm run compile:js command. The Axerve Ecommerce Solutions cartridge does not contain any CSS files, so JS compilation is sufficient.

The front-end compilation has been corrected and optimised in the transition from version 5.1.6 to 5.1.7 in order to provide system integrators with a complete cartridge that runs in stand-alone mode. The previous version, on the other hand, required the inclusion of custom logic to carry out the compilation (adding custom files to the Axerve Ecommerce Solutions cartridge or using other cartridges in the project in order to set points to the underlying cartridges and carry out the JS compilation steps).

Once installation has been completed via the next steps, the expected result on the front end should be as follows:

Cartridge path configuration

In Business Manager, go to Administration > Sites > Manage sites > siteID > Settings and add the following cartridges to the beginning of the cartridge path: int_gestpay_mfra:int_gestpay:int_gestpay_core

Cartridges must be uploaded using the standard procedures provided by Salesforce Commerce Cloud: via the Commerce Cloud UX-Studio plugin on Eclipse or via the dw.json configuration file and Prophet Debugger extension on Visual Studio Code.

Import Metadata

In the link_gestpay/metadata folder there is a folder called meta-mfra that contains two .xml files (custom-objecttype-definitions.xml, system-objecttype-extensions.xml) that need to be imported under Administration > Site Development > Import & Export.

All .xml import procedures described in the document need to be carried out in MERGE mode.

Important: before importing .xml files, we advise exporting the metadata already on your Business Manager application (Meta Data > Export, export custom object type and system object type separately) and merge them with the .xml files in the link_gestpay cartridge, then upload the updated files.

Configuring and activating payment methods

In the link_gestpay/metadata folder, there is an .xml file called payment-methods.xml which must be imported under Merchant Tools > Ordering > Import & Export > Payment Methods.

Payment Processors can be configured manually by adding the new GESTPAY_CREDIT and GESTPAY_PAYMENT_GATEWAY components in the Merchant Tools > Ordering > Payment Processors section or by importing the payment-processors.xml file via the Administration > Site Development > Site Import & Export section. For manual creation, you must enter GESTPAY_CREDIT and GESTPAY_PAYMENT_GATEWAY in the ID field, while the description field can be left empty.

Credit card

To enable credit card payments, go to Merchant Tools > Ordering > Payment Methods and select CREDIT_CARD. Set up the Payment Processor on GESTPAY_CREDIT and verify that the Enabled field is set to “Yes”.


To enable PayPal payments, go to Merchant Tools > Ordering > Payment Methods and select PayPal. Rename the ID using PAYPAL instead of PayPal; then set the Payment Processor to GESTPAY_PAYMENT_GATEWAY and check that the Enabled field is set to “Yes”.

Other payment methods

The other payment methods available, in addition to those mentioned above, are:

To enable each of these methods, it is necessary to set the Payment Processor to GESTPAY_PAYMENT_GATEWAY and check that the Enabled field is set to “Yes”.

Below is an example for Alipay:

The list of enabled payment methods must be consistent with the configurations made in Axerve Ecommerce Solutions Backoffice.

Site preferences configuration

In the link_gestpay/metadata folder, there is an .xml file called preferences.xml which needs to be imported in the Administration > Site Development > Site Import & Export section.

After importing the file, it is possible to set the Site Preferences for Axerve Ecommerce Solutions in the Merchant Tools > Site Preferences > Custom Site Preference Groups > GestPay Configurations section.

Here are some instructions on how to set up the required Site Preferences:

Configuring Services

In the link_gestpay/metadata folder, there is an .xml file called services.xml which needs to be imported in the Administration > Operations > Site Import & Export section.

Configuring Jobs

In the link_gestpay/metadata folder, there is an .xml file called jobs.xml that needs to be imported under Administration > Operations > Import & Export.

Attention: Only one job is imported via this .xml, gestpay-s2s-job, which refers to the file int_gestpay/cartridge/scripts/jobs/notification.js, but this file is not in the official version 5.1.6 of the cartridge or in the previous versions (5.1.5, 5.1.3). The file has been restored to version 5.1.7 using a customised version of the 5.1.6 cartridge, adapted for a specific merchant.

LOG Analysis

Logs are defined at the int_gestpay_mfra level and are contained in the file that handles service calls. The keyword to look for in the logs is gestpayService, which can be found in the SFCC logs. To access the log view on SFCC, go to Administration > Development Setup > Log Files.

Job Installation Guide


It is necessary to use the job if you are using Klarna as a payment method or if Riskified has been enabled on your merchant account.

We recommend that you set up the CheckOrders job step in your order update job, which we will call UpdateOrders for example, in order to avoid possible competition problems on resources (orders), thus having a single writer on orders.

To install the step in your UpdateOrders you must follow the instructions in paragraph 5.2.2.

In the absence of pre-existing jobs, we recommend starting from paragraph 5.2.1.

Job Step Installation From BM

5.2.1 - Go to the BM, select Administration -> Operations -> Jobs. Click on New Job, on the top right-hand side of your screen, and enter ID.

5.2.1 Step Installation

Click the + button to install the step in Update Job (Image A), then click the Configure a step link .



In the search section, type GestPay and then select custom.GestPay.StatusCheck.