--- title: "Best practices to increase the Conversion Rate" description: "Merchant operational guide with the copy, UX and integration levers to reduce drop-off in the AIS flow (AISaaS and AIS One Shot)." url: "https://docs.fabrick.com/en/payment-institution/open-banking-and-psd2/pass/products/ais-common/pass-ais-best-practice/" language: "en" --- # Best practices to increase the Conversion Rate **Merchant operational guide** · `AISaaS · ongoing access` · `AIS One Shot · occasional access` > **How to use this guide** > > This guide collects the levers — copy, UX and integration — that **the merchant controls directly** to reduce user (PSU) drop-off along the aggregation flow through the Account Aggregation services. > > Start with the interventions that are easiest to implement and that bring the most direct benefit to the PSU. > > Every friction point in the AIS flow increases the risk of drop-off. Small copy, UX and integration interventions can significantly improve the completion rate without changing the core of the product. ## 1. The levers under your control Along the user journey, these are the points where you can act directly: - **The connection CTA** — where and when you show it. - **The pre-redirect screen** — the last thing the user sees before moving on to Fabrick. - **The parameters you pass during the API call** — e.g. the pre-selected bank. - **Return handling** — what you show the user when they re-enter your flow, in case of success or error. - **The moment of consent renewal** — you can anticipate it: the dedicated API exposes the consent expiration date in advance, so you can prompt the user before the data stops being updated. - **First-level support** — integrate a support channel (chat, help center) into your flow, so that a user with a doubt doesn't drop off but immediately finds an answer. ### Difference: One Shot vs Ongoing | AIS One Shot | AISaaS ongoing | | ------------------------------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Emphasizes the *single and temporary* nature of the access: *"one single access, only for this check"*. It reduces the perception of commitment. | The value is recurring and more widespread. Ask for the connection **after** the user has already perceived value, and communicate **right from the start** the duration of the consent and the ease of renewal, so that the expiration doesn't come as a surprise. | ## 2. The pre-redirect screen The pre-redirect screen is the point of the flow where you can most influence the user's decision to proceed. It prepares the user for what is about to happen and reduces drop-off at the moment of the handover to Fabrick. ### Recommended anatomy ![MockupSchermata](https://docs.fabrick.com/en/img/payment-institution/open-banking-and-psd2/pass/account-information/standard/schermata-pre-reindirizzamento-mockup.png) ### What to write in each block | Block | What to write | | --------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **\[1] Title** | Focus on the outcome, not on the mechanism. *"See your account data in a few minutes"*, not *"AIS connection via Open Banking"*. | | **\[2] Expected benefit** | Spell out the concrete benefit and, if possible, the time/effort saved compared to the alternative (e.g. uploading bank statements). | | **\[3] What you will need** | Anxiety arises when the redirect is unexpected. Clearly say how long it takes and what to have at hand — **bank credentials and smartphone.** | | **\[4] Brand lockup** | Place your logo next to Fabrick's ("Your brand → Fabrick"): it shows the continuity between your service and the partner you are about to redirect the user to. | | **\[5] Trust signals** | Read-only access, credentials that are not stored, Fabrick as a secure partner supervised by the Bank of Italy, consent revocation at any time. | | **\[6] Timeline** | The expected steps in 3 stages: choose your bank, log in securely, return to the app. It makes the expectation of what will happen concrete. | | **\[7] CTA** | Action verb oriented to the benefit (*"Connect and verify"*), with a secondary link to the FAQ for those who want to learn more without leaving the flow. | > **The mistakes that increase drop-off** > > - Asking to connect the account without first explaining the benefit for the user. > - Redirecting the user to Fabrick without notice and without presenting Fabrick as a partner of the service, creating an unexpected change of context. > - Using technical terms that only industry insiders understand, without explaining their meaning (AIS, PIS, PSU...). > - Omitting elements that increase trust, such as how data is accessed, the fact that credentials are not stored and the possibility of revoking consent. ## 3. The moment of the request (CTA timing) *When* you ask for the connection often matters more than *how* you ask for it. - Place the CTA at a **high-intent** point, where the benefit has just been made evident (e.g. right after showing the user what they will get). - Avoid asking for the connection too early, before the user has understood the value: it converts worse regardless of any other factor. - If the flow allows it, first show a "taste" of value and then ask for the connection. ## 4. Interventions that increase the CR They require development but are often the real multiplier of the CR, more than copy alone. ### Return handling, whatever the outcome `AISaaS` `AIS One Shot` When the user re-enters your flow, always communicate something: a confirmation message if it went well, or a message in plain language and a clear **retry** point in case of cancellation or error, instead of a dead end. A good part of the recoverable leakage is here. ### Skip the thank-you page `AIS One Shot only` If you handle the completion confirmation in your own flow, you can skip Fabrick's thank-you page and immediately show your own success message: one step less between the user and the value you promised them. ### Skip the bank search `AIS One Shot only` If you pass the bank identifier as a parameter in the call, you can skip Fabrick's bank search step altogether: you build that search yourself, branded and consistent with your UI, and you arrive at Fabrick with the bank already selected. ### Your logo in the Fabrick flow `AISaaS` `AIS One Shot` You can insert your company's logo along the connection journey. The user keeps seeing a context consistent with the one they started from, instead of perceiving a jump to an unknown domain: less confusion, less drop-off. ### Your company name highlighted `AISaaS` `AIS One Shot` Show your company name: it reinforces the perception that the user is still interacting with you, even if technically they are on a Fabrick domain. ### Pre-fill personal data `AISaaS` If you already pass the PSU's data (first name, last name, address, residence, email, etc.) in the API call, the user doesn't have to re-enter it during registration: fewer fields to fill in, less friction, less drop-off before reaching the real value of the service. ### Only for use cases where more than one account needs to be aggregated **Request the connection of the main account only, when it is sufficient:** asking the user to aggregate all accounts in the same flow increases friction and the risk of drop-off. If necessary, you can always invite them to add other accounts at a later time, by calling the API again. **Sequence the connections and make progress visible:** if multiple accounts are needed, ask for them one at a time and show where the user is (e.g. "1 of 3 accounts connected"). **Deliver value already from the first connected account:** the user must perceive a concrete benefit before being invited to add other accounts. ## 5. Consent renewal (AISaaS ongoing only) Prompting consent renewal is a retention lever. An expired consent means frozen data and value that silently degrades, often without the user noticing until it is too late. - **Always communicate the duration of the consent:** you already have this information via API. Show it in your app from the first connection, in the pre-redirect screen and in the FAQ, without waiting for the moment of renewal. - **Notify proactively** before expiration (in-app, email). - **Make renewal low-friction:** create a dedicated CTA, we have a dedicated API for consent renewal. ## 6. Fabrick brand and media kit Showing the Fabrick logo next to yours, in your flow, communicates that the collaboration is real and verified: it reassures the PSU that they are not leaving your perimeter for an unknown service, but continuing a journey in which we are an active part. > **Fabrick media kit** > > Logo in all variants (blue, midnight, white), usage guide and other official brand assets. > > 👉 [Open the media kit](https://www.fabrick.com/it-it/media-hub/media-kit/) ### Where to place the logo - **Pre-redirect screen:** place your logo next to Fabrick's ("Your brand → Fabrick" lockup) at the top of the screen, it is the point where the user most needs visual continuity, right before leaving your domain. - **Return page and FAQ:** repeat the same lockup in the return screen (success or error) and in the extended FAQ page, it keeps the story consistent along the whole journey, not just at the beginning. - **Use the correct variants:** blue logo on a light background, white on a dark or brand background, choose the variant from the media kit based on contrast, do not redraw it or alter its colors. ## 7. Self-assessment checklist ### Copy & UX - [ ] Benefit-oriented title, without jargon - [ ] Explicit value exchange in one sentence - [ ] Expectations managed: redirect to the bank, no. of steps, time - [ ] Visible trust signals (read-only, no credentials, Bank of Italy, revocation) - [ ] Key FAQ inline near the CTA - [ ] CTA at a high-intent moment ### Integration - [ ] Bank pre-selection where possible - [ ] Return with negative outcome handled (human message + retry) - [ ] Sequenced connections + visible progress - [ ] Value already from the first connected account ### Ongoing (retention) - [ ] Consent duration communicated up front - [ ] Proactive renewal notification, before expiration - [ ] Low-friction renewal prompt ## 8. FAQ to show to the PSU Distinguish two levels: 1. **Insert an informational link below the main CTA ("Connect and verify"):** place below the CTA a secondary link or a "How it works" micro-trigger, which on click opens a small pop-up (or bottom sheet on mobile) with the 2–3 pieces of information that help the user overcome the main doubts before proceeding, not a link to an external page. The content must remain short and focused on the objections that block conversion: "Is it safe?" (access takes place through a formal authorization, with data processed according to the applicable rules), "What data is shared?" (which information is needed and why), "What happens next?" (bank selection, authorization, return to the app), "Can I revoke consent?" (yes, at any time). The goal is not to add information to the main flow, but to make immediately available the answers that can create hesitation, right at the moment the user decides whether to continue. 2. **Extended FAQ on a dedicated page**, for those who want to go deeper than the 2–3 key objections. Below are the ready-to-use texts, with common questions grouped together and only the specific ones split by family. Adapt them to your tone of voice. ### 7a · Common FAQ #### Who is Fabrick and what is the Account Information Service (AIS)? Fabrick is an Italian fintech of the Banca Sella group, specialized in Open Banking and Embedded Finance. The AIS service allows you to access the data of one or more bank accounts to take advantage of value-added services such as creditworthiness assessment, accounting reconciliation or expense analysis. Depending on the service, access can be single (One Shot) or ongoing. #### What are the advantages of AIS? - **Value-added services** based on account data, offered by third-party companies (e.g. expense analysis, accounting and bank reconciliation, creditworthiness assessment). - **Simplicity:** few steps, without having to manually log in to your home banking. - **Security:** access takes place under the supervision of the Bank of Italy and without storing your bank credentials. #### What data is shared and how is it used? We collect and process the following data from your account: - Balance - IBAN and name of the account holder - Transaction information #### Who is the Third Party Company? It is the company that provides you with the additional services based on your account data, accessible through AIS: expense analysis, accounting reconciliation, creditworthiness assessment or other services you have chosen to subscribe to. #### What is Strong Customer Authentication (SCA)? SCA is a mandatory security system exposed by banks, provided for by the regulations supervised by the Bank of Italy, which verifies the identity of the person authorizing access to the account data. It ensures that only the holder, the joint holder or a delegate can authorize the sharing, through two-factor authentication: 1. **Bank login** → enter your credentials in your bank's interfaces (Fabrick never sees or stores them). 2. **Authentication** → the bank requires a second factor, such as a code via SMS, fingerprint or confirmation through the app. Only after this verification is access to the data authorized. #### What are the costs? Fabrick does not apply direct costs for the use of AIS services. The Third Party Company offering the value-added services may apply a fee: contact them for any information on this. #### I can't find my bank in the list. What do I do? If your bank is not in the list, it has not yet been integrated into the service — we are constantly adding new ones. Check that you have spelled the name correctly; if it is missing, report it to us through the service provider and we will do our best to integrate it as soon as possible. #### What do I do in case of errors or problems? - Contact the Third Party Company that manages the value-added service. - Check that your bank credentials are correct. - Contact your bank's support to check for any service disruptions. ### 7b · AISaaS only #### How long does the consent last and can I revoke it? Consent to data access lasts **6 months**, for all services. When it expires you will be asked to renew it with a simple step. You can revoke consent at any time from the Fabrick dashboard or by contacting the Third Party Company. #### Why do I need to create credentials? The credentials created at first access are needed to log in to the Fabrick dashboard, where you manage your accounts in one place while maintaining full control and security of the information. #### How do I access the dashboard? With the credentials created during registration. Once logged in you can view balances and transactions, manage consents, aggregate other accounts and take advantage of the other value-added services. ### 7c · One Shot only #### What does it mean to grant a Third Party Company temporary access to my bank data? By authorizing access, Fabrick guarantees that the Third Party Company can consult your data only for the time strictly necessary to provide you with the requested service — in compliance with your privacy and security. In AIS One Shot this is a **single access**.