---
title: "Customizations"
description: "During the setup phase of its product, FPP will be able to customize some aspects relating to the UX. These have to be agreed with Fabrick who will proceed with the appropriate configurations."
url: "https://docs.fabrick.com/en/payment-institution/open-banking-and-psd2/pass/products/ais-common/service-customization/"
language: "en"
---

# Customizations

## Introduction

During the setup phase of its product, FPP will be able to customize some aspects relating to the UX. These have to be agreed with Fabrick who will proceed with the appropriate configurations.

For all products it is possible to customize the logo and name of the company, both will be showed to final customers. As far as the logo is concerned, it has to be in png format with a transparent background.

Below are all the others possible customizations divided by product.

### Transactions History

For the Pass Aisp product it is possible to configure the *historical* parameter. In particular it is possible to set the following properties:

- *IsEnabled*: boolean which se set to *true* identifies the enabling of the movement history (recover more than 90 days of depth)
- *NumberOfMonths*: integer that identifies the months of depth of the history \* *availableFirstConsent*: boolean. If set to *true*, it enables the history mode only for banks that allow the history to be recovered with a single SCA (e.g. CBI will be excluded as of today)

#### Transaction history retrieval considerations

Below are some considerations on enabling the history and thus to recover the list of movements even beyond 90 days.

1. Fabrick requests and retrieves the maximum time interval allowed by that specific bank (e.g. 6 months, 1 year, 2 years,..) in case *NumberOfMonths* parameter is bigger than the allowed period allowed by the bank.

2. In the case of Pass Aisp standard, to date, the historical request will only be valid at the time of the first creation of the consent (therefore not for renewal). This means that se the PSU renews the consent beyond 90 days from the expiry date, a gap will be created in the transaction list.

   For example:

   - consent deadline 27/09/23
   - renewal of consent 30/12/23

   In this case, there will be a gap of *94 (date difference) - 90 (time frame retrieved from Fabrick) = 4 days*

3. The CBI gateway requires a double consensus to obtain the history, which means that the PSU will have to perform the SCA phase twice

4. If an FPP enables history, it will enable it for all its customers. If a particular PSU is also a customer of another FPP linked to Fabrick Pass then the latter FPP will inherit the history functionality for that particular PSU given that the PSU dashboard is related to the end customer and transversal from the point of view of the different FPPs.