open menu
axerve docs
Payments/Alternative payments/FabrickPass

FabrickPass FabrickPass

WEB

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

  • An open and eligible account with Banca Sella

  • 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.

default

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

Instant transfers:

  • Pending -> OK: Transfer in process and then successful.

  • Pending -> KO: Transfer in process and then failed.

  • OK: Transfer successful.

  • KO: Transfer failed.

Ordinary transfers:

  • Pending -> OK: transfer in process and then successful.

  • Pending -> KO: transfer in process and then failed.

  • OK: Transfer successful.

  • KO: Transfer failed.

Unusual instances on Instant/Ordinary Transfers:

  • OK -> KO: Transaction cancelled (possible fraud or cancellation, not allowed by regulation).

Sella Bank accounts

Instant Transfers:

  • Pending -> OK: Transfer in process and then successful, amount credited to account.

  • Pending -> KO: Transfer in process and then failed.

  • OK: Transfer successful, amount credited to account.

  • KO: Transfer failed.

Ordinary transfers:

  • Pending -> OK: Transfer in process and then successful, amount credited to account.

  • Pending -> KO: Transfer in process and then failed.

  • OK: Transfer successful, amount credited to account.

  • KO: Transfer failed.

default

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

Activation process

1. Testing and certification

  1. Use the test environment provided by Fabrick to verify integration

  2. Carry out trial payments to ensure the lack of any anomalies

2. Fabrick integration

  1. Send an email requesting activation of the FabrickPass payment method to the address provided in the dedicated area.

  2. If more than one shopLogin is available, enter which one you wish to activate the functionality for.

  3. Wait for the email containing the onboarding link provided by Fabrick with a redirect to Fabrick, in which you will be asked to enter information about the Ecommerce and proceed with the account activation.

  4. Enter the required configuration information and start using FabrickPass.

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

copy
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

copy
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

copy
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

copy
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

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

In the Method field, you can specify the preferred transfer type as follows:

  • Instant Credit Transfer: fill in the Method field with ‘instant-sepa-credit-transfers’.

  • Ordinary Credit Transfer: enter ‘sepa-credit-transfers’ in the Method field.

  • No preference: if there is no preference between instant or ordinary credit transfer, leave the Method field empty.

The maximum length of BankTransferDescription is 120 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 documentationexternal link or contact technical supportexternal link.

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 Referenceapi link.

  • 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

Previous
prevEPS
Next
Giropaynext