---
title: "PSU Guide - Onboarding"
description: "The following document describes the steps that the PSU will have to carry out to complete the OnBoarding phase for the Fabrick census."
url: "https://docs.fabrick.com/en/payment-institution/open-banking-and-psd2/pass/products/standard/media/user-ux/aisp-psu-guide/"
language: "en"
---

# PSU Guide - Onboarding

## Introduction for FPP

The following document describes the steps that the PSU will have to carry out to complete the OnBoarding phase for the Fabrick census. The following process is *only necessary for the Fabrick Pass project* and not for the Fabrick Pass One Shot for which please refer to the specific documentation.

The OnBoarding phase is initiated by the FPP, redirecting the customer to the link returned by the **POST CreateUserOnBoarding** API.

This phase is necessary for regulatory purposes as Fabrick has the role of TPP according to the PSD2 nomenclature and is therefore the entity supervised, as well as authorized, by the Bank of Italy.

The guide may be shared with the PSU as a source of support; alternatively, being a one-off operation, FPP could decide to create a support figure who can assist its client through the entire process and support him in case of any doubts.

## FPP client tutorial

The tutorial will be divided into two sections:

- OnBoarding phase
- Dashboard PSU

The OnBoarding phase records the PSU in the Fabrick registry. After registering, the PSU, using the chosen credentials, will have access to the Dashboard which will allow it to manage its consents and authorizations regarding the FPPs. In fact, a PSU can be a customer of several FPPs at the same time and can share different information with each of them.

## OnBoarding phase

The OnBoarding phase is divided into four sections:

- Registration
- Personal data
- Recognition
- Contracts acceptance
- Aggregation of accounts

Once all the steps have been completed, it will be possible to proceed with the aggregation of your accounts while remaining on the same Fabrick page.

The first three points are intended as a one-off for each PSU. For example, se the PSU was already registered on Fabrick because it is the user of another service offered by a different FPP, he will be automatically redirected to the last phase (in a transparent way on the FPP side).

This check is based on the PSU's personal information, primarily the tax ID number

### Registration

As soon as the PSU clicks on the link, he will be redirected to this homepage

![onb1](https://docs.fabrick.com/en/img/payment-institution/open-banking-and-psd2/pass/account-information/standard/onboarding/onb1.png)

The first step is registration, on this first page the PSU will have to decide a password that respects the rules indicated by the UI. The credentials chosen will be useful for accessing the Fabrick Dashboard once the process has been completed.

![onb2](https://docs.fabrick.com/en/img/payment-institution/open-banking-and-psd2/pass/account-information/standard/onboarding/onb2.png)

As you can see from the previous image, it will also be necessary to accept the pre-contractual documentation and the information on the processing of personal data.

As soon as confirmed, the PSU will receive an email from Fabrick ([noreply@fabrick.com](mailto:noreply@fabrick.com)) with a 4-digit OTP:

---

*Gentile Mario Rossi,*

*ti preghiamo di inserire nella procedura di registrazione di Fabrick Pass il seguente codice di sicurezza univoco (OTP):*

**1234**

*Entering this code allows us to verify the authenticity of the email address provided during registration.*

*Puoi riprendere la procedura di registrazione in ogni momento al seguente link: [https://fabrick.com/fabrick/pass/v4.0/onboarding/abcd1234-abcd-efg-bc5f-123456789012?jwtToken=1234abcd-randomToken-4321](https://fabrick.com/fabrick/pass/v4.0/onboarding/abcd1234-abcd-efg-bc5f-123456789012?jwtToken=1234abcd-randomToken-4321).*

*Grazie,* *Il Team di Fabrick Pass*

---

the code has to be entered in the next step to verify the correctness of the email indicated.

![onb3](https://docs.fabrick.com/en/img/payment-institution/open-banking-and-psd2/pass/account-information/standard/onboarding/onb3.png)

By continuing, the confirmation will be displayed:

![onb4](https://docs.fabrick.com/en/img/payment-institution/open-banking-and-psd2/pass/account-information/standard/onboarding/onb4.png)

### Personal Data

In this second phase it will be necessary to confirm your personal data. The fields will already be pre-filled as they have been passed by the FPP at the time of the OnBoarding phase. It is not possible to modify the data shown in this first part, but it will be necessary to correct them by referring to your FPP.

![onb5](https://docs.fabrick.com/en/img/payment-institution/open-banking-and-psd2/pass/account-information/standard/onboarding/onb5.png)

All data relating to one's residence and domicile may be corrected:

![onb6](https://docs.fabrick.com/en/img/payment-institution/open-banking-and-psd2/pass/account-information/standard/onboarding/onb6.png)

The fields of this second screen will be pre-filled se and only se the data has been passed by the FPP itself at the time of the onBoarding phase, otherwise the PSU will have to fill in manually.

### Recognition

At this point Fabrick will have to verify the veracity of the information provided by the PSU. To do this, 3 different methods are proposed:

- Verification via SPID
- Documentary verification
- Verification by bank account

Some of the methods presented will not be available in some countries.

![onb7](https://docs.fabrick.com/en/img/payment-institution/open-banking-and-psd2/pass/account-information/standard/onboarding/onb7-ric.png)

#### Verification via SPID

If the PSU selects the first method, he will be redirected to his provider's page, thus continuing with the flow already known to the SPID user.

#### Documentary verification

In this case, the PSU will be required to take a selfie showing the identity document in the hand. The document must be clearly visible and legible.

The PSU can take a photo via its webcam or select a previously saved file:

As a second step, the PSU will have to upload his document (front and back) entering all the data relating to him.

#### Verify via bank account

In this last case, confirmation takes place following a double check:

- authentication via SCA at PSU's bank
- comparison of the user's name and surname with the holder of a personal account

In this case, Fabrick will ask the PSU to select the bank where he has a personal account and proceed with the authentication phase as he would normally do on his internet banking.

It could happen that the PSU bank is not present in this list: this does not mean that it is not supported, but only that the bank does not expose the account holder as information via the PSD2 channel (not allowing Fabrick to carry out the necessary checks ). Fabrick is trying to reduce the number of banks with this limitation through direct reports: the percentage, already very low, is therefore constantly decreasing.

> This phase is only useful for recognition purposes, it should be noted that the aggregation and authorization phase by the PSU towards the FPP will take place in the subsequent steps. For example, se you want to aggregate the accounts of your company in the name of "MyCompany Spa", it will be done in the following steps, while in this step it will be necessary to indicate the bank where you have a personal account in the name of the natural person to allow verification of identification. FPP will not be able to read information relating to this current account used only for recognition purposes by Fabrick.

Once selected, you will pass to the second box where you will have to confirm Fabrick's authorization to retrieve the account data to proceed with the checks.

In this step there is also the "*Select environment*" drop-down menu: this component is visible only in the test UI, therefore never visible to the PSU in production environment. It is useful for the FPP to select sandbox or live accounts during its internal tests.

The next step will be the authentication phase on the selected bank.

The authentication step or sca flow can be different for each bank, to see all the possibilities please refer to "Strong Customer Authentication Flows - UI".

##### Selection of holding account

At the end of the SCA (Strong Customer Authentication) phase, the third and last box will open in which the PSU will be asked to indicate the type of holder for each account. In fact, it is possible that the PSU has more than one account at the indicated bank and, for each one, it will also have the possibility to decide whether to synchronize it (allow Fabrick to keep the information updated) or not simply by selecting or deselecting it.

If the match between the data indicated and the name and surname of the account holder is successful, the verification can be considered successful. In the event that the holder does not correspond exactly with the name and surname of the PSU, the recognition step will not be successful and the PSU will se a warning message with all the details. In this case it will be possible to use a second account having the holder consistent with the generality of the PSU, otherwise one of the other two methods of recognition can be used.

This could happen, for example, in the case of a joint account, as the control is based on the exact match of the information

#### Which method to choose?

The PSU can choose the method it prefers, Fabrick recommends verification by bank account or SPID as the first method. Compared to document verification, they are faster and less subject to the possibility of error.

### Anti-money laundering questionnaire

Once the verification has been successfully completed, as a last step, you will be asked to fill in a short anti-money laundering questionnaire:

![onb8](https://docs.fabrick.com/en/img/payment-institution/open-banking-and-psd2/pass/account-information/standard/onboarding/onb8.png)

If the answer is yes, for each question, a text box will appear so that the PSU can enter the necessary details:

### Contracts acceptance

The User Experience continues with the confirmation of the contractual conditions, the PSU will have to read them before being able to continue. You will need to download the "Fabrick Pass Agreement" document before proceeding.

![onb9](https://docs.fabrick.com/en/img/payment-institution/open-banking-and-psd2/pass/account-information/standard/onboarding/onb9.png)

The next page is dedicated to FPP, the name and logo of the company will be visible (in the example Test Company).

![onb10](https://docs.fabrick.com/en/img/payment-institution/open-banking-and-psd2/pass/account-information/standard/onboarding/onb10.png)

In this case as well, the PSU must download the “Information on the service” document, which contains all the information regarding the service offered by their FPP. This document will be prepared by the FPP and sent to Fabrick, which will upload it to this page; [here](https://docs.fabrick.com/en/files/platformAndPaymentInstitution/openBankingAndPSD2/PassAIsAllegatoServizioValoreAggiuntoSample.docx) you can find a sample template.

### Aggregation of accounts

At this point, the PSU can proceed with the aggregation of all the desired accounts. Continuing with our example, having used the "Bank Account" mode for the previous phase, the same bank is automatically re-entered having already valid consent from the PSU. Obviously it is possible to deselect it (because it is only useful for identification purposes) and connect others.

![onb11](https://docs.fabrick.com/en/img/payment-institution/open-banking-and-psd2/pass/account-information/standard/onboarding/onb11.png)

Some banks require the PSU to indicate the type of account: for example BPM distinguishes the business account from the retail one and also offers the WeBank service. The behavior is the same as for Internet Banking, so also in this case the PSU will know which one to select based on its account types.

As described above, the PSU will be redirected to the page of the selected bank and we will continue with the SCA and finally to return to the Fabrick domain again to select the accounts to be synchronized. With each new aggregation, the PSU will return to the summary page where he can connect a new account or finish the procedure.

The accounts selected at this stage will be those shared with the FPP.

By completing the process, the PSU will be automatically redirected to the application of the FPP (se any).

![onb12](https://docs.fabrick.com/en/img/payment-institution/open-banking-and-psd2/pass/account-information/standard/onboarding/onb12.png)

## Dashboard PSU

Once the OnBoarding phase has been completed, the customer will be able to access their Dashboard available at the following link:

[https://www.fabrickpass.com](https://www.fabrickpass.com/)

([https://www.uat.fabrickpass.com/web/fabrick/pass/v4.0/login](https://www.uat.fabrickpass.com/web/fabrick/pass/v4.0/login) in pre-production)

The login credentials will be the email address and password chosen during registration.

The dashboard is useful for the PSU to manage everything related to its accounts. It is independent from the FPP as the PSU could be a customer of several FPPs and therefore have multiple aggregate accounts and decide to authorize only some of them for a given FPP and others for another FPP.

The FPP may provide on its UI the possibility of redirecting the PSU on the Dashboard. The FPP can also decide to insert the link of the *Home* page (the link indicated above) or a link relating to a particular section so that the PSU lands directly on the desired page.

As an alternative to the dashboard, to allow FPPs to directly redirect users on the renewal of consents and the addition of new aggregations, it is possible to initialize the Update Aggregation workflow described in the other sections.

### Which One to Choose

It is recommended to use the **POST Update Aggregation** API instead of the full dashboard (static link) for the following reasons:

- The PSU will have a simplified and straightforward user experience for managing its accounts.
- Once the flow is complete, the PSU will be automatically redirected to the page specified by the FPP.
- All accounts will be automatically authorized for the calling FPP without the need to explicitly request it, thus avoiding an extra step for the PSU. Only in certain situations might the full dashboard be more convenient, for example, if the PSU is a client of multiple FPPs and wants to manage accounts and authorizations for each FPP from a single page.

## Onboarding result and email comunications

Once the onboarding phase has been completed, Fabrick's controls can give different results. The controls concern both the identification part, based on the method selected by the user among those exposed (SPID, bank account, document verification), and the part of AML (Anti Money Laundering) and CSSE (Control of Subjects Subjected to Embargo). CSSE is the Watchlist Screening Procedure of GBS. It is an application that is owned by Anti-Money Laundering department. In this section we will describe all the possible cases.

Fabrick will communicate the status of the process to the PSU by email. Below are the emails that the PSU may receive.

### Registration confirmed

---

*Congratulations,*

*we confirm your registration to the Fabrick Pass service. You will be able to take advantage of your account and activate the services of the third-party companies connected.*

---

In this case the process has been completed successfully and the PSU will be able to immediately use the service offered by the FPP.

### Registration confirmed: document verification in progress

---

*Congratulations,*

*we confirm your registration to the Fabrick Pass service. We will complete the verification of the documentation acquired within 3 working days and we will notify you of the result via email. In the meantime, you will be able to take advantage of your account and activate the services of the connected third-party companies.*

---

In this case, the process was successful, but the PSU used document verification as identification method: an additional check may be required up to a maximum of 3 days as indicated by the email.

### Registration confirmed: temporary suspension of the service

---

*Congratulations,*

*we confirm your registration to the Fabrick Pass service. Unfortunately, the verification activities of the acquired documentation are taking longer than expected. We are forced to temporarily suspend the service until the verification activities are completed. We apologize for the inconvenience.*

---

In this case, the checks gave a negative result relating to the identification part. An example would be where the user has used document verification as identification method, but the document is unreadable. A second e-mail will be sent to the PSU with the instructions to be performed, in the example described above a link will be sent to allow the new upload of the document.

The PSU will be able to decide whether to proceed again with the upload of the document from the link received by email or, alternatively, to restart the OnBoarding phase from the FPP page and choose a new identification method. In fact, Fabrick will recognize the user and bring him directly to the necessary step by skipping the steps already passed with a positive result.

Below is an example of the email that the customer could receive:

---

*Gentile Mario Rossi,*

*We are experiencing problems verifying the identity document you uploaded to our portal.* *Please upload it again, making sure to photograph the front and back of the original document, centered and clearly legible.* *Thank you for your cooperation.*

*Ricarica qui il documento*

*Grazie,* *Team Fabrick Platform*

---

*Dear Mario Rossi,* *we are experiencing some problems in verifying the identity document you uploaded to our portal.* *Please upload it again, making sure to photograph the document front and back, in its original version, in a centred and clearly legible position.*

*Thank you for your cooperation.*

*Update here your document*

*Kind regards,*

*Team Fabrick Platform*

---

### Registration confirmed: temporary suspension of the service

---

*Congratulations,*

*we confirm your registration to the Fabrick Pass service. We must carry out further checks on the information provided and we are forced to temporarily suspend the service. We will inform you of the result of the checks, at the end of which you can start taking advantage of the benefits of your account and activate the services of the third-party companies now connected.*

---

In this case, additional verification by Fabrick is required regarding the AML or CSSE aspects. In general, this verification will take very little time and will therefore allow the user to access the service; otherwise, the user will not be able to access the service until the verification is complete. The maximum waiting time guaranteed by Fabrick is 7 days.

### Registration rejected

---

*Dear Customer,*

*unfortunately it was not possible to accept your request to open the Fabrick Pass Account Information service based on the assessments and checks carried out by Fabrick on the requirements necessary to proceed with the activation of the same.* *We apologize for the inconvenience.* *Greetings,*

---

Following Fabrick's checks, the customer was found to have a high risk profile, for this reason it is not possible to proceed with the activation of the service
