--- title: "PSU Guide" description: "The following document describes the operations that the PSU must perform in the initialization phase of a payment on Fabrick." url: "https://docs.fabrick.com/en/payment-institution/open-banking-and-psd2/pass/products/pisp-in/media/pisp-in-psu-guide/" language: "en" --- # PSU Guide ## Introduction to the FPP The following document describes the operations that the PSU must perform in the initialization phase of a payment on Fabrick. This phase is initiated by the FPP by redirecting the customer to the link returned by the **POST CreatePaymentWorkflow** API. This phase is necessary for regulatory purposes as Fabrick has the role of TPP according to the PSD2 nomenclature and it is the entity supervised and authorized by the Bank of Italy. The guide may be shared with the PSU as a source of support. ## PSU tutorial ### Introduction With the API **POST CreatePaymentWorkflow** the FPP will be able to modify and/or simplify the flow that Fabrick will present to the PSU. For example, the FPP will be able to decide the type of payment (SEPA, instant or leave the PSU the possibility to make the choice). It will also be able to pre-fill an IBAN or even use a previously saved PSU account. For all the details, refer to the guide *Fabrick Pass - Payment Initiation*. ### Payment flow The FPP has the ability to make various choices that modify the UX of the PSU: based on the information passed to Fabrick via the workflow initialization API, it will be able to simplify the steps of the payment flow. This document describes the two main cases: - FPP does not know the account information of its customer (without *debtorAccountId*) - The customer chooses the bank where his account is rooted or enters his bank's IBAN - the FPP knows a priori the account information of its customer (with *debtorAccountId*) #### Workflow initialization without debtorAccountId When the FPP does not provide the customer's account information, the PSU will arrive on the following Fabrick page: ![passPis1](https://docs.fabrick.com/en/img/payment-institution/open-banking-and-psd2/pass/pay-by-bank/pis-in/pisp-psu-ui/pass-pis1.png) The first part shows some information about the FPP and the provided service. The second part instead shows a brief summary of the payment, indicating at the bottom that Fabrick will not apply any commission. Proceeding further the PSU will have to choose the personal bank and the following page will be displayed: ![passPis2](https://docs.fabrick.com/en/img/payment-institution/open-banking-and-psd2/pass/pay-by-bank/pis-in/pisp-psu-ui/pass-pis2.png) And then the PSU will see a recap of the payment: ![passPis3](https://docs.fabrick.com/en/img/payment-institution/open-banking-and-psd2/pass/pay-by-bank/pis-in/pisp-psu-ui/pass-pis3.png) It is possible to see an additional white box in case the bank manages different internal services such as a retail account and a business account. This behavior is typical of CBI gateway banks; also in this case the user must select the service from a drop-down menu. The third box indicates the type of payment, as indicated in the technical documentation, FPP will decide between the following choices: - ordinary bank transfer - instant transfer - let the PSU choose between the two modes above In the latter case, the UI will appear in the section to allow the PSU its preference. In our example, the first type was indicated by the FPP, so the PSU will not be able to modify it. In the last box, the PSU must accept the terms and conditions by reading the information on the processing of personal data. In this section there is also the checkBox that allows the PSU to save the account used for subsequent payments. This information, as shown above, will be exposed by Fabrick during the payment flow and will be shared with the FPP. The last drop-down menu of the box allows the PSU to select the environment, choosing between a real account and a test account displayed by the selected bank. In fact, all banks must expose a sandbox environment to allow testing of TPPs (or FPPs in this case). Obviously this menu is present only in the test environment and it's removed in the production environment. By confirming the initialisation of the payment, the PSU will be redirected to the page for entering your bank's credentials. Depending on the modality exposed (see technical document for details) it will be possible to continue on the Fabrick page or be redirected to the final bank page. Now the PSU will be redirected to the bank's page where he will enter his credentials. In this way the IBAN will be prevalued by the bank and the PSU will be able to proceed with the authorization of the payment. If the user has several accounts, the bank page will ask him to select the desired one from the list shown on the screen. If the bank does not support the direct payment method without IBAN, Fabrick will carry out the procedure to allow the user, with specific consent, to select the account and in any case make the payment without manually entering the Iban. In our example we have entered a Unicredit bank account. ![passPis5](https://docs.fabrick.com/en/img/payment-institution/open-banking-and-psd2/pass/pay-by-bank/pis-in/pisp-psu-ui/pass-pis5.png) Immediately after entering the credentials, the PSU will proceed with the confirmation via the second factor. The expected behavior must be exactly the same as for internet banking: receiving an SMS or a push notification on the smartphone... ![passPis6](https://docs.fabrick.com/en/img/payment-institution/open-banking-and-psd2/pass/pay-by-bank/pis-in/pisp-psu-ui/pass-pis6.png) There is also the possibility that the second factor is not requested (see PISP exemption rules) and the payment will be authorized after confirmation of the authentication credentials. Once the flow has finished, the FPP will be able to decide, based on a configuration defined with Fabrick during setup and valid for all payments, whether to show a Fabrick page with a personalized message or to redirect the PSU directly to the page of any application. The choice may depend on several factors: - se the payment flow was initiated from the FPP app or via a "payByLink" sent by email - se the FPP, once the flow is complete, prefers to manage the UI from its own app or delegate the UI to Fabrick. #### Workflow initialization with debtorAccountId When the FPP knows the PSU's account information, this information can be passed directly to Fabrick via the same **POST CreatePaymentWorkflow** API. In this way, navigation by the PSU is simplified and reduced only to the confirmation of the Terms and Conditions. In particular, the information to be shared will be the type of payment, the bank and its service (se exist). Through the ABI information, retrieved from the IBAN, Fabrick will show the customer's bank directly. It could happen that two different banks correspond to an ABI (for example Unicredit and Buddy Bank): in cases like this, the PSU will be asked to select its own bank from the 2 shown in the first box. ### Double SCA flow Some banks, particularly those belonging to the CBI gateway, require a double SCA flow. This is due to the gateway's interpretation of the PSD2 specifications: the first SCA indicates an authentication phase, while the second indicates the payment authorization phase. If you choose to implement the Fabrick-side debtor management mode, Fabrick can save certain information relating to the customer's account in order to avoid the first SCA from the second payment onwards. #### Blacklisted banks The FPP has the option of inserting one or more banks in the black-list (see technical documentation: black-list and white-list), this means that the black-listed banks will not be present in the bank list shown to the user. If the user inserts an iBAN relating to that specific bank, the following message will be shown: ![passPisIbanBlackListed](https://docs.fabrick.com/en/img/payment-institution/open-banking-and-psd2/pass/pay-by-bank/pis-in/pisp-psu-ui/pass-pis-iban-black-listed.png) The user should then proceed by selecting a different bank where possible. ### Payment flow UK case In this case the PSU will be redirected to the page of our partner Token.io. Below is an example. Bank selection: ![token_1](https://docs.fabrick.com/en/img/payment-institution/open-banking-and-psd2/pass/pay-by-bank/pis-in/pisp-psu-ui/uk-token/token-1.png) Confirm the payment details ![token_2](https://docs.fabrick.com/en/img/payment-institution/open-banking-and-psd2/pass/pay-by-bank/pis-in/pisp-psu-ui/uk-token/token-2.png) Insert the credentials ![token_3](https://docs.fabrick.com/en/img/payment-institution/open-banking-and-psd2/pass/pay-by-bank/pis-in/pisp-psu-ui/uk-token/token-3.png) Insert the OTP ![token_4](https://docs.fabrick.com/en/img/payment-institution/open-banking-and-psd2/pass/pay-by-bank/pis-in/pisp-psu-ui/uk-token/token-4.png) Select (eventually) the debtor account ![token_5](https://docs.fabrick.com/en/img/payment-institution/open-banking-and-psd2/pass/pay-by-bank/pis-in/pisp-psu-ui/uk-token/token-5.png) ### Communications to the PSU For each payment correctly authorized by the end customer, Fabrick will send an informative email to the customer with some payment details to be used in case of request for further information. As a payment institution, Fabrick is subject to specific disclosure and transparency obligations toward the PSU. Upon successful completion of the payment initiation process—that is, when the payment request is properly initiated and authorized by the PSU at their bank—Fabrick must provide evidence of the outcome of its activity. It is important to note that this communication refers exclusively to Fabrick’s activities as a PISP and does not constitute confirmation that the payment has actually been executed or posted. The subsequent execution of the payment is, in fact, the responsibility of the PSU’s bank, over which Fabrick has no control. For this reason, the email cannot be deleted or disabled at Fabrick’s discretion, as it is part of the obligations associated with the provision of the regulated service. --- *Gentile Mario Rossi,* *Hai disposto un ordine di pagamento a favore di Merchant Demo di EUR 1000.* *Codice Operazione Fabrick: 123456* *Codice Operazione ASPSP (prestatore di servizi di pagamento di radicamento del conto): 654321* *Data Operazione: 22/11/2023 09:19:48* \*Costo Operazione: EUR 0,00 \*\* *You can consult the information sheet with the terms and conditions of the Service that you accepted and signed when placing the payment order at the following link: [https://www.fabrick.com/wp-content/uploads/2021/09/F002_Fabrick-PASS_PISP-incasso_Foglio-Informativo-PSU_20210927.pdf](https://www.fabrick.com/wp-content/uploads/2021/09/F002_Fabrick-PASS_PISP-incasso_Foglio-Informativo-PSU_20210927.pdf)* *Please download and keep the document.* *Grazie,* *Il Team di Fabrick Pass* *\* Applied by Fabrick. Any costs and fees charged by the ASPSP or the beneficiary of the transaction are not included.* *---------------------------------------------------------------------------------------------------------------------------* *Dear Mario Rossi,* *You initiated a payment of EUR 1000 to Merchant Demo.* *Fabrick Transaction ID: 123456* *ASPSP (Account Servicing Payment Service Provider) Transaction ID: 654321* *Transaction Date: 22/11/2023 09:19:48* \*Transaction Fee: EUR 0,00 \*\* *You can check out the Terms and Conditions you accepted and signed in the process of payment initiation at the following link: [https://www.fabrick.com/wp-content/uploads/2021/09/F002_Fabrick-PASS_PISP-incasso_Foglio-Informativo-PSU_20210927.pdf](https://www.fabrick.com/wp-content/uploads/2021/09/F002_Fabrick-PASS_PISP-incasso_Foglio-Informativo-PSU_20210927.pdf)* *Please download and keep the document.* *Thank you,* *Fabrick Pass Team* *\* Charged by Fabrick. Any fees the ASPSP or the beneficiary may charge are not included.* --- The email is sent as soon as the PSU completes the SCA (authorizing in this ay the payment initiation). If the bank replies immediately (near real time) indicating the payment status as REJECTED, then the email will not be sent, despite the successful authorization.