Fabrick Pay by Bank

Bank transfer description

The bank transfer description is always generated by Fabrick Payment Orchestra in the following format:

YYMMDDn [custom value or shopTransactionId bankId]

Static Prefix: generated by Orchestra with date and unique number (YYMMDDn, e.g., 2504171), where:

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

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

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

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

Variable part:

• If the merchant provides a custom value via API in payment requests, it is added to the static prefix. The value must be alphanumeric, with a maximum length of 120 characters

• If the merchant does not provide a custom value, the static prefix is added with the Shop Transaction ID and Bank ID

Example of bank transfer description:

• If a custom value is provided by the merchant: 2504171 test, where:

  • 2504171 - static prefix

  • test - custom value provided by the merchant in the payment request

• If no custom value is provided by the merchant: 2504171 123456423 123, where:

  • 2504171 - static prefix

  • 123456423 - Shop Transaction ID

  • 123 - Bank ID

In the variable part of the bank transfer description (whether for the custom value or the Shop Transaction ID), no special characters must be used: the use of non-alphanumeric characters may cause errors in generating the description or issues within the receiving bank systems.

Payment statuses

On accounts other that Banca Sella’s, Captured ≠ Credited: manual verification is required for reconciliation.

Note: Some statuses (AUTHORIZATION_EXPIRED or AUTHORIZATION_REFUSED) are not visible in the Fabrick Dashboard in order to simplify operational management.

Reconciliation and credit visibility

Merchants with a Banca Sella Account

• Fabrick has direct visibility into the merchant’s account.

• The credit is detected automatically and linked to the transaction.

• The “Captured” status is assigned only upon the verification of the actual credit of the transfer to the merchant’s account.

Merchants with an account at another institution

• Fabrick has no access to the merchant’s account, so reconciliation must be done manually.

• The “Captured” status is assigned when the transfer has been successfully executed by the payer’s bank, but it does not imply verification of the actual credit.

Reporting on Fabrick Dashboard

Every Fabrick Pay by Bank payment is visible on the Dashboard with the following data:

Benefits and Limitations

Benefits for the customer

• No external registration required

• Security through bank authentication (SCA)

• No frauds

• Traceability and irrevocability of payments

Benefits for the Merchant

• Lower costs compared to cards and wallets

• No frauds

• Non reversible payments, PSD2 compliant

• Automatic reconciliation (Banca Sella only)

• Modern, integrated payment experience

 Limitations

• No automatic reconciliation for accounts of Banks other than Banca Sella’s

• Captured ≠ actual credit on external accounts

Technical integration

Activating the test environment

To test the Fabrick Pay by Bank solution, a test environment is required. If you don’t already have one, it can be created by following the instructions available in the following page:  Requesting a test account | Fabrick.

Once registration is completed, a Shop Login will be generated in the format:
GESPAYXXXXX.

Requesting activation of the payment method

Once obtained the Shop Login for the test environment, it is necessary to request the activation of Fabrick Pay by Bank method.

The request can be sent:

• To your Fabrick sales contact, or

• Through the dedicated  Support area, by selecting:

• Product: “Fabrick Payment Orchestra”

• Item: “Other” from the drop-down menu.

It is essential to include the Shop Login of the test environment in the request.

Onboarding and configuration

Following the request, you will receive an email containing the onboarding link.
By following the link, it will be possible to complete the account activation by entering the required information.

Payment Initialization

Once the test environment is active, it is possible to start simulating payments using one of the two available modes:

• SOAP API

• REST API

The domains and endpoints to be used are described in the dedicated First minimal payment page.

Fields to include in the call for Fabrick Pay by Bank

Regardless of the chosen method (SOAP or REST), it is essential to correctly include certain mandatory fields in the request payload.

Below are examples of the calls to be made depending on the selected method.

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}

Additional Information for integration

Shop Transaction ID

The shopTransactionID field is a free-form string that uniquely identifies the transaction.
It can be filled according to the merchant’s needs, in compliance with the constraints outlined in the  Axerve technical documentation (e.g., disallowed characters).

Transfer Type and “Method” Field

For more details, refer to the dedicated section.

Setting the Bank transfer description

For more details, refer to the dedicated section.

CustomerDetail and Checkout Simplification

Providing complete data in CustomerDetail:

• CustomerDetail.FirstName

• CustomerDetail.LastName

• CustomerDetail.PrimaryEmail

allows the buyer to skip the step of manually entering their personal details during the Fabrick Pay by Bank payment flow. This optimization streamlines the user experience and reduces friction during checkout.

The buyerEmail field represents the email address of the user making the payment.

The PrimaryEmail field represents the account holder and can be left empty in the API request (it will be requested on the payment page if not provided).

Localization

• The languageId field allows to define the language of the email sent by the Fabrick Payment Orchestra gateway to the buyer.

• The language of Fabrick Pay by Bank page automatically adapts to the user’s browser language.

• Fabrick Pay by Bank emails are multilingual: the first language corresponds to the merchant’s country, the second is English (e.g., Italian/English).

How to verify the payment outcome

The transaction outcome can be checked via:

• API call getPaymentDetails

• Test environment dashboard ➤ Set up the merchant profile | Fabrick

For merchants with Banca Sella accounts, the “Captured” status corresponds to the actual credit.
For merchants with accounts at other banks, the “Captured” status only indicates that execution has been confirmed by the buyer’s bank.

Testing Fabrick Pay by Bank payments on Fabrick Payment Orchestra

Introduction

This section describes how to perform controlled tests for payments made via Fabrick Pay by Bank integrated with Fabrick Payment Orchestra, simulating various scenarios and observing the expected outcomes.
A structured table provides the parameters and configurations needed to simulate different payment scenarios, ensuring accurate analysis of the system’s responses.

Tests are divided into two main categories:

• Tests for merchants with a Banca Sella account: the full payment cycle can be verified up to the credit (including reconciliation).

• Tests for merchants with accounts at other banks: the test ends with the confirmation of execution from the buyer’s bank, but without verification of the actual credit.

Parameters configuration

For each test, you must correctly set certain parameters in the request:

If the transaction is not completed within 5 minutes, the system will return a KO outcome due to timeout.

Test example

Goal: Verify an instant transfer executed successfully to a Banca Sella bank account.

Steps:

1. Select the relevant test case from the table (see technical documentation).

2. Use the banking credentials provided for the test.

3. Set the amount field to 1.00.

4. After approximately 45 seconds, the payment will be marked as successfully executed (OK).

Test for merchants with a Banca Sella account

Test for Merchants with an account at another Bank

Sandbox Credentials –Test accounts

FAQ for Fabrick Pay by Bank

Is it possible to offer only instant transfers (or only standard transfers)?

Yes, the merchant can request Fabrick to configure only one of the two modes (standard SEPA credit transfer or instant SEPA credit transfer). In this case, the buyer will not see any choice option, and the payment will be executed using the configured transfer type only.

Can the customer choose the type of transfer (standard or instant)?

Yes, but only if both modes (standard and instant) are enabled for the store.
In this scenario, by setting the “Method” field in the request (sepa-credit-transfers or instant-sepa-credit-transfers), the merchant can pre-select the transfer type suggested to the buyer.
However, the user will still be able to manually change it on the payment screen.

Does the “Captured” status always guarantee the credit?

Only for Banca Sella accounts, as Fabrick can directly read the credit on the merchant’s account.
For merchants without a Banca Sella account, the “Captured” status indicates that the payment has been executed, but manual reconciliation by the merchant is required.

Can I use special characters in the custom value of the payment description?

No, only simple alphanumeric characters should be used.
Entering special characters may compromise the correct processing of the transfer.