FabrickPass

Documentation for the activation of the FabrickPass alternative payment method via Fabrick

FabrickPass is the alternative payment method which, with the offer of a single solution, enables Ecommerce to receive credit transfers without the need for PSD2 regulation certification. How can the service be used? This page contains the necessary instructions for the integration and activation of the PISP service through the use of Fabrick as payment gateway.

Pre-requisites

To start the activation process, you must meet the following requirements:

• A signed Ecommerce contract with Fabrick

• It is advisable to activate the product with a Banca Sella account.

• FabrickPass can be used with an account with a bank other than Banca Sella, but as the status of the transfer will not be received, manual reconciliation will be required.

In the case of an account other than Banca Sella, the status of the credit transfer in the Fabrick dashboard will remain ‘Pending’ (XX). It is necessary to manage the ‘Pending’ status of the payment, because SEPA credit transfers have a pending status that respects the timing of the network.

Accounts Other Than Banca Sella

Standard and/or Instant Bank Transfer:

• XX: Transfer pending

• OK: Transfer completed

• KO: Transfer failed

Banca Sella Accounts

Standard and/or Instant Bank Transfer:

• XX: Transfer pending

• OK: Transfer completed, amount credited to the account

• KO: Transfer failed

FabrickPass is available exclusively for companies with registered offices in Italy, France and Spain.

Activation process

1. Integration with Fabrick

• If you don’t already have one, you will need to create a test environment to test the solution by following the instructions at this link. Upon registration, you will receive a shopLogin, a string formatted as: “gespayxxxxx”.

• Send an email requesting the activation of the FabrickPass payment method to your contact person or submit a request through the dedicated area at this link, selecting "Other" from the dropdown menu. You will need to provide the shopLogin of the test environment for which activation is requested.

• Wait for the email containing the onboarding link provided by Fabrick and enter the required information to activate the account.

2. To initialize a payment in the test environment, you can use one of the two supported methods: SOAP or REST. The domains to be used in API requests are listed here.

3. Fields to include in the FabrickPass call                               

Before making the call to FabrickPass, you must ensure that the following mandatory fields are correctly included in the payload.

The following fields are required to ensure the correct processing of the transaction:

API SOAP

Encrypt

1<soapenv:Envelope xmlns:soapenv="<http://schemas.xmlsoap.org/soap/envelope/>" xmlns:ecom="<https://ecomm.sella.it/>">
2   <soapenv:Header/>
3   <soapenv:Body>
4      <ecom:Encrypt>
5         <ecom:shopLogin>{{shopLogin}}</ecom:shopLogin>
6         <ecom:apikey>{{Apikey}}</ecom:apikey>
7         <ecom:uicCode>242</ecom:uicCode>
8         <ecom:amount>0.03</ecom:amount>
9         <ecom:shopTransactionId>{{shopTransactionId}}</ecom:shopTransactionId>
10         <ecom:paymentTypes>
11            <ecom:paymentType>FABRICKPASS</ecom:paymentType>
12         </ecom:paymentTypes>
13         <ecom:OrderDetails>
14            <ecom:BankTransferDescription>{{BankTransferDescription}}</ecom:BankTransferDescription>
15            <ecom:ProviderPaymentDetails>
16               <ecom:Method>instant-sepa-credit-transfers</ecom:Method>
17            </ecom:ProviderPaymentDetails>
18            <ecom:CustomerDetail>
19               <ecom:FirstName>Mario</ecom:FirstName>
20               <ecom:Lastname>Rossi</ecom:Lastname>
21               <ecom:PrimaryEmail>mario.rossi@fabrick.com</ecom:PrimaryEmail>
22            </ecom:CustomerDetail>
23         </ecom:OrderDetails>
24      </ecom:Encrypt>
25   </soapenv:Body>
26</soapenv:Envelope>

Decrypt

1<soapenv:Envelope xmlns:soapenv="<http://schemas.xmlsoap.org/soap/envelope/>" xmlns:ecom="<https://ecomm.sella.it/>">
2   <soapenv:Header/>
3   <soapenv:Body>
4      <ecom:Decrypt>
5         <ecom:shopLogin>{{shopLogin}}</ecom:shopLogin>
6         <ecom:CryptedString>{{CryptedString}}</ecom:CryptedString>
7         <ecom:apikey>{{Apikey}}</ecom:apikey>
8      </ecom:Decrypt>
9   </soapenv:Body>
10</soapenv:Envelope>

S2S - callReadTrxS2S

1<soapenv:Envelope xmlns:soapenv="<http://schemas.xmlsoap.org/soap/envelope/>" xmlns:ecom="<https://ecomms2s.sella.it/>">
2   <soapenv:Header/>
3   <soapenv:Body>
4      <ecom:callReadTrxS2S>
5         <ecom:shopLogin>{{shopLogin}}</ecom:shopLogin>
6         <ecom:shopTransactionId>{{shopTransactionId}}</ecom:shopTransactionId>
7         <ecom:bankTransactionId>{{bankTransactionID}}</ecom:bankTransactionId>
8         <ecom:apikey>{{Apikey}}</ecom:apikey>
9         <ecom:paymentDeviceDetails>
10            <ecom:TerminalId></ecom:TerminalId>
11         </ecom:paymentDeviceDetails>
12      </ecom:callReadTrxS2S>
13   </soapenv:Body>
14</soapenv:Envelope>

API REST

Create

1{  
2   "shopLogin":"{{shopLogin}}",
3   "amount":"0.01",
4   "currency":"EUR",
5   "shopTransactionID":"{{ShopTransactionID}}",
6   "buyerEmail":"mario.rossi@fabrick.com",
7   "responseURLs": {
8       "buyerOK": "https://{{ThankYouPage_Url}}",
9       "buyerKO": "https://{{ThankYouPage_Url}}",
10       "serverNotificationURL": ""
11   },
12   "paymentType":["FABRICKPASS"],
13   "paymentChannel": {
14       "channelType":["LINK"]
15   },
16   "OrderDetails": {
17       "BankTransferDescription": "{{BankTransferDescription}}",
18       "ProviderPaymentDetails": {
19           "Method": ""
20       },
21       "CustomerDetail": {
22           "FirstName": "Mario",
23           "Lastname": "Rossi",
24           "PrimaryEmail": "mario.rossi@fabrick.com"
25       }
26   }
27}

Detail

1{
2  "shopLogin" : "{{shopLogin}}",
3  "bankTransactionID": "",
4  "shopTransactionID" : "",
5  "paymentID":"{{paymentID}}",
6  "terminalID": ""
7}

The shopTransactionID parameter is a free string that can be set as desired. Refer to the API documentation for more details, including which characters are not allowed, available here.

In the Method field, you can specify the desired type of bank transfer as follows:

• Instant Bank Transfer: Set the Method field to "instant-sepa-credit-transfers".

• Standard Bank Transfer: Set the Methodfield to "sepa-credit-transfers".

This field will only set the preferred method; the final choice will always be up to the paying user, who can change the method on the Fabrick page.

The maximum length of BankTransferDescription is 120 characters, and only alphanumeric characters can be used.

By entering the CustomerDetail fields (FirstName, LastName, PrimaryEmail), the Buyer data entry step in FabrickPass will be automatically bypassed.

For further information or technical support, you can contact technical support.

Populating the Bank Transfer Description for FabrickPass

When using FabrickPass, the Orchestra system will automatically add a prefix to the bank transfer description in the following format:

YYMMDDN

• YY = Last two digits of the year (e.g., 25 for 2025)

• MM = Month in two-digit numeric format (e.g., 02 for February)

• DD = Day in two-digit numeric format (e.g., 24 for the 24th)

• N = Incremental daily counter (e.g., 1, 2, 3...)

Example of a generated description:

12502241

2502241

Notes:

• To ensure acceptance by banks, avoid using special characters in the description.

• The maximum allowed length for the description is 50 characters.

Entering the CustomerDetail fields (FirstName, LastName, PrimaryEmail) will automatically skip the Buyer data entry step in FabrickPass.

For further information or technical support, please consult the complete Fabrick API documentation or contact technical support.

Further info

Below is some useful information for managing the integration:

• The language specified in the languageId defines the language of the e-mail that is sent from Fabrick (Gateway) to the Fabrick buyer API Reference.

• The language of the FabrickPass page changes according to the language set on the browser.

• The e-mail sent by FabrickPass to the buyer is in two languages. For example, if the location is in Italy, the first language will be Italian and the second English.

The information listed in CustomerDetail, and below, is needed to skip the page that requires it on FabrickPass:

• FirstName

• LastName

• PrimaryEmail

How to check the outcome?

It is possible to check the outcome either through a new API request (getPaymentDetails) or via the dashboard provided. For the test environment, here is an explanation of how to access the dashboard: link.

As mentioned earlier, we highlight the difference in the outcome of an OK result depending on whether the account is a Banca Sella account or a different account.

FabrickPass (PISP) Test in Orchestra

Introduction

This section describes the testing process for payments with FabrickPass (PISP) in Orchestra, outlining the various cases and outcomes of transactions. A structured table provides the necessary parameters and configurations to simulate different payment scenarios, ensuring an accurate analysis of the system's responses.

If the credit account is a Banca Sella account, it is possible to directly verify the reconciled payment. This test is not available for accounts with other banks.

The section is divided into two parts:

• Test with Banca Sella Accounts

• Test with Accounts from Other Banks

Configuring Parameters in Orchestra

To perform tests, the request parameters must be properly configured.

Main Parameters

• bankId: The identifier of the bank to use

• bankName: The name of the bank

• product: The type of payment (SEPA Credit Transfer or Instant SEPA Credit Transfer)

• amount: The transfer amount

• status: The expected final status for the test

• threshold: Time (in seconds) required to reach the final status

If the payment is not completed within 5 minutes, the status returned will be KO.

Test Example

Objective: Verify an instant bank transfer with a successful outcome on Banca Sella.

1. Select the corresponding row in the test cases table.

2. Use the credentials of the corresponding bank.

3. Set the amount to €1.

4. After 45 seconds, the payment status will change to OK.

The following section provides a structured reference for performing reliable tests, facilitating the identification of any anomalies, and ensuring the correct functioning of the payment system

Test Cases

Test Cases with Banca Sella Accounts

Test with Accounts from Other Banks

Sandbox Account Credentials Table