Standard payment page

The table above displays the required fields only. Other fields may be relevant if you use a specific anti-fraud system or alternative payments. Check the API for the full list.

There are two available endpoints:

• Test environment

https://sandbox.gestpay.net/gestpay/GestPayWS/WsCryptDecrypt.asmx?wsdl

• Production environment

https://ecommS2S.sella.it/gestpay/GestPayWS/WsCryptDecrypt.asmx?wsdl

You need to start with a SOAP encryption request, following which Fabrick Payment Orchestra processes a payment with this data:

1<Encrypt>
2   <shopLogin>GESPAY12345</shopLogin><!-- Assigned by Fabrick Payment Orchestra backend --> 
3   <uicCode>242</uicCode> <!-- code for Euro --> 
4   <amount>1245.6</amount> <!-- the money you want to receive -->
5   <shopTransactionId>34az85ord19</shopTransactionId> <!-- an ID generated by you -->
6</Encrypt>

Fabrick Payment Orchestra responds as follows:

1<EncryptResult>
2   <GestPayCryptDecrypt xmlns="">
3   <TransactionType>ENCRYPT</TransactionType>
4   <TransactionResult>OK</TransactionResult><!-- everything ok! -->
5   <CryptDecryptString>2C53F1B5...</CryptDecryptString><!-- crypted string with sent info -->
6   <ErrorCode>0</ErrorCode><!-- ...another way to say Ok! -->
7   <ErrorDescription/>
8   </GestPayCryptDecrypt>
9</EncryptResult> 

With the string encryption (2C53F1B5...) and the shopLogin it is possible to redirect the user to the payment page.

Step III: request to the payment page

After obtaining the encrypted data code (as described in the previous step), the buyer will be redirected to the payment page of the Fabrick Payment Orchestra server to the following address:

https://ecomm.sella.it/pagam/pagam.aspx?a=<ShopLogin>&b=<encrypted string>

in test environment:

https://sandbox.gestpay.net/pagam/pagam.aspx?a=<ShopLogin>&b=<encrypted string>

The page request will be executed by satisfying two parameters:

• a The code that identifies the merchant (Shop Login)

• b The encrypted code string that identifies the transaction

The payment page receives the parameters and verifies the identity (parameter a must correspond to the merchant) and the security of the transaction data (parameter b must correspond to the string of encrypted data communicated by the merchant during the previous step).

If the checks are passed, the buyer will see the payment page and will have to enter the required data to complete the payment process.

If the checks are not passed, the payment page will not be displayed and the process moves on to the next step of the communication of the transaction result.

Via our payment page :

• Fabrack manages transaction security

• You can choose which active payment systems will show in the list, such as PayPal, UnionPay or MyBank

• You can customize the layout by inserting your own logo

Step IV: communication of the result of the transaction

After the buyer has concluded the payment, Fabrack communicates the result of the transaction to both the merchant and the buyer.

The payment result for the merchant

Once the payment has been successfully carried out, Fabrick Payment Orchestra redirects the user to the URL set up for a positive response. Otherwise, it will be redirected to the URL created for the negative response.

Redirecting happens according to 2 parameters:

• a which is the shopLogin

• b which contains an encrypted string with the transaction result

At this stage, the merchant's server must send the request WsCryptDecrypt.Decrypt again to decrypt the gateway response and show the correct message to the buyer.

On Yourshop.com the same response has been set up for both positive and negative results, but it is still possible to set a specific response for each result. The buyer is redirected to:

http://www.yourshop.com/response.php?a=GESPAY12345&b=2C53F1B5...

response.php page needs to be able to:

• receive 2 arguments (a & b)

• decrypt b

• show the buyer the outcome (receipts, emails etc.)

Once the payment is completed, Fabrick Payment Orchestra communicates an encrypted string with the transaction result to the merchant's server via Server to Server URL (optional). If the Server to Server URL has not been set up in the back office, the communication will take place on the URL defined for a positive response.

The notification is forwarded by server-to-server request to the page specifically set up on the merchant's server (the URL of the notification page is one of the merchant's profile data, and is configurable through Fabrack Back Office). The syntax of the call is as follows:

http://<url server to server>?a=<ShopLogin>&b=<encrypted string>

The request to the page is sent after 2 parameters are satisfied:

• a the code that identifies the merchant (Shop Login)

• b the encrypted code string with the transaction result

If there are any communication errors, Fabrick Payment Orchestra will perform multiple forwarding attempts for two days following the transaction.

Once a and b are received, you can send the Decrypt request (from the WsCryptDecrypt web service) to find out the outcome of the transaction and update the database, in order to send the confirmation email to the customer, etc.

The merchant will also receive an e-mail notification regarding the result of the transaction to the address set up in their profile.

Furthermore, the processed transaction can be viewed by accessing the Fabrack Back Office in the Active Report section.

According to the MOTO settings, the transaction can be set to Authorized (the amount of the transaction is blocked but not yet transferred); or Settled (MOV – the amount is transferred from the buyer's account).

If the transaction is authorized, it must be captured in the Fabrack Back Office.

Payment result for the buyer

Fabrick Payment Orchestra immediately communicates the result of the transaction. The buyer can also download the receipt in PDF format.

The buyer will also receive an notification email with the transaction result to the address provided on the payment page, if indicated.

At the end of the payment, if the buyer does not click on the "Back to shop" button, the payment will not be finalized and the Fabrack's server will not send the Server to Server notification to the merchant.