Gestpay becomes Axerve Ecommerce Solutions

# Setup the merchant profile

Each merchant can configure his/her profile by accessing the Axerve Back Office environment at:

## Authentication

REST api introduces ApiKey authentication, a random token generated via Axerve Backoffice to be used in every call. This approch has been introduced to cope with the rise of cloud hostings, where it’s difficult to always have the same public IP.

The first step is to create and activate your ApiKey in your backoffice.

Choosing REST API, you can only use ApiKey authentication, which means the APIKEY must be checked like in the image above.

Please understand that if the apiKey is stolen, anyone can pretend to be you from Axerve Ecommerce Solutions’ standpoint. Keep the apiKey safe and never share with anyone.

The token must be attached as header to every call to Axerve Ecommerce Solutions.

Authorization:apikey R0VTUEFZNjU5ODcjI0VzZXJjZW50ZSBUZX....


For more information on how to generate and manage the apikey, please refer to the online help available on each page.

Alternately, once you have created a payment, you can use the payment token

paymentToken:Asjdlfad5543AA33a....


## Configuration of response URLs and e-mail

Axerve Ecommerce Solutions communicates the transaction result with a server-to-server call to a page specifically prepared by the merchant and by directing the buyer’s browser to the pages configured by the merchant (different pages for positive or negative results).

In the Configuration > Responses section in the Back Office environment, it is possible to specify the URLs used by the system to communicate the transaction result.

In this section it is also possible to specify the addresses that will be used for e-mail notifications.

The required urls are:

• URL for positive response: when the payment is successfully completed.
• URL for negative response: when the payment fails.
• URL Server to Server: server to server call, returned in both cases (success and failed)

In all cases, Axerve Ecommerce Solutions adds these parameters to the url:

• a: Shop login
• status: OK (success) or KO (fail)
• paymentID
• paymentToken

It’s also possible to overwrite these URLs during the payment/submit call, in responseURLs object (check the documentation for more details).

The status of the transactions can be:

• UNSUBMITTED The transaction is created but not yet submitted.
• WAITING The payment has been subimtted and Axerve Ecommerce Solutions is waiting for something to happen in order to perform the authorization request (eg. user 3DS authetication or 3rd party payment redirect)
• PENDING (XX) The authorization request has been performed and Axerve Ecommerce Solutions awaiting the 3rd patry’s response
• APPROVED (OK)
• DECLINED (KO)

## M.O.T.O. : what happens after a transaction

M.O.T.O. stands for Mail Order - Telephone Order. Long before internet, the only way to pay without having to show the credit card was by telephone, or by mail.

In Axerve Ecommerce Solutions, M.O.T.O. means that a transaction is carried out without physically handling the credit card.

M.O.T.O. is intended as the way the system should behave when receiving transactions. There are two options:

• Unify authorization and transaction. When a buyer completes a payment, the money is automatically transferred to the merchant account.
• Separation of the authorization and the transaction process. In this case, when the buyer completes a payment, Axerve Ecommerce Solutions only asks for the payment authorization of his credit card company (e.g. verify that the money is available, and make a pre-authorization); subsequently the merchant must carry out the transaction.
• In this case it is possible to customize the operation. It’s possible to choose the operation between delete and move, and the number of days before its execution (14 days for Klarna, 25 for each other method)

If the transaction is not carried out within 25 days (configurable), Axerve Ecommerce Solutions will automatically cancel the transaction and the money will be returned to the buyer. 25 days is the maximum number of days that a transaction can be authorized before being cancelled.

M.O.T.O. settings are valid for all credit card transactions, including ApplePay, Hype, or token transactions.

M.O.T.O. settings are valid for every Axerve Ecommerce Solutions plan. Your settings will be used to determine the transaction next state, whether you’re using Axerve Ecommerce Solutions payment page, or the iFrame solution, or server-to-server calls.

## Fields & Parameters configuration

Mechants may want to display or hide some fields in the payment page, or in the email response, depending on their needs; think of the buyer’s email or name. In Configuration > Fields & Parameters you can decide which parameters to show, and when.

## Sending Custom Parameters to Axerve Ecommerce Solutions

During the payment/create call you can also pass user-defined parameters. This is completely optional and can be useful for attaching some additional data (a sessionId, a variable, etc.) that you want to receive back when the payment is completed (or failed).

From the page Payment Page -> Fields & Parametrs, you can create custom parameter by clicking on Add parameter in the Merchant Back-Office:

Then fillout the box with your parameter’s name:

A description of the fields:

• Field Name: the parameter name that will show up in the Mechant Back-Office, under Payment Page -> Fields & Parametrs.
• Parameter: the parameter name that will be used via code in payment/details and other methods.
• Response: the name that the parameter should have in response.
• Visible: if the parameter should be shown to the buyer on the payment page, click this button. You can choose a name for the parameter in all Axerve Ecommerce Solutions supported languages.
• Email Response: if the parameter should be sent to the buyer via mail, here you can specify the name of the parameter in all Axerve Ecommerce Solutions supported languages.

Once you have set up a new parameter (in the examples the parameter is called MYPARAM) you can send it via payment/create method.

You can code your custom parameters inside the field customInfo, in a key/value syntax.

"customInfo":{
"{myCustomInfo1}":"{myCustomInfoValue1}",
"{myCustomInfo2}":"{myCustomInfoValue2}"
}


You can retrive those parameters calling payment/details. They are also included in the payment/submit result.

For more informations about customInfo check out the API documentation.