Setup the merchant profile

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

Some settings regard the procedure and the information that must be sent to or will be returned by GestPay.

Authentication configuration

GestPay identifies the merchant requesting the encryption service through the WSCryptDecrypt web service by comparing the calling server IP address to the IP addresses configured in the profile associated with the Shop Login used for the call. If the calling server is not recognised, the transaction process ends and a specific error is returned.

In the Configuration - IP Addresses section of the Back Office environment, the merchant can enter the IP addresses of its servers (if calls to GestPay originate from a server farm). There is no limit in the number of insertable IPs.

Configuration of response url and e-mail

GestPay communicates the transaction result with a server-to-server call to the 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 notifications via e-mail.

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 a good without exhibiting the credit card was by telephone, or by mail.

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

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

If the transaction is not carried out in 25 days (configurable), Gestpay 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.

Configuration of Fields & Parameters

if you want to send more than the mandatory fields, for example if you want to customize the payment process, you must declare what fields you are going to send. This section describes how and what.

Merchants can define the transaction structure (specifying what information beside the required information will have to be sent to GestPay) by configuring in the Back Office environment what information is to be sent in phase I and what information must be returned when the transaction result is communicated.

This system allows the merchant to customise the transaction structure with proprietary information that will be stored in the GestPay archives and will allow each transaction to be identified using customised search keys. Moreover, customised information can be returned with the transaction result communication, thus allowing the merchant’s information system to manage this information appropriately.

Tokenization: set Fields & Parameters

In order to be able to request, obtain and use a Token, merchants need to appropriately set their “Fields and Parameters” in the dedicated section of GestPay Merchant Back Office.

Then the merchant has to create a new page in the Back Office Interface to see the Tokenization features in the list of the parameters.

Following settings must be applied (for changes to take effect, the page must be published):

Field Settings Notes
Token Request PARAMETER = TRUE This allows merchants to request a new token.

Payment Options Visibility: set Fields & Parameters

In order to configure Payment Options Visibility for the payment page of a transaction, merchants need to appropriately set their “Fields and Parameters” in the dedicated section of GestPay Merchant Back Office.

Following settings must be applied (for changes to take effect, the page must be published):

Field Settings Notes
Payment Types PARAMETER = TRUE This allows merchants to insert a tag <paymentType>?</paymentType> for each payment method they want to show on the payment page.

Payment Type Detail: set Fields & Parameters

In order to configure Payment Type Detail for the payment page of a transaction, merchants need to appropriately set their “Fields and Parameters” in the dedicated section of GestPay Merchant Back Office.

Following settings must be applied (for changes to take effect, the page must be published):

Field Settings Notes
PaymentTypeDetail PARAMETER = TRUE This allows merchants to insert tag <paymentTypeDetail.MyBankBankCode> or <paymentTypeDetail.IdealBankCode> to specify the Bank Code to use in the payment page

Consel “Rate in Rete”: set Fields & Parameters

In order to configure Consel “Rate in Rete” for the payment page of a transaction, merchants need to appropriately set their “Fields and Parameters” in the dedicated section of GestPay Merchant Back Office.

Following settings must be applied (for changes to take effect, the page must be published):

Field Settings Notes
ConselMerchantPro PARAMETER = TRUE Merchant Pro code to pass in the encrypt to show Consel “Rate in Rete” in the payment page (tag Consel_MerchantPro)
ConselCustomerInfo PARAMETER = TRUE Customer Info data tag enabled into XML (tag Consel_CustomerInfo)

PayPal Reference Transaction: set Fields & Parameters

In order to configure PayPal Reference Transaction for the payment page of a transaction, merchants need to appropriately set their “Fields and Parameters” in the dedicated section of GestPay Merchant Back Office.

Following settings must be applied (for changes to take effect, the page must be published):

Field Settings Notes
PayPallBillingAgreement PARAMETER = TRUE a description of the goods, terms and conditions of the billing agreement