<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Mirta Rotondo on Medium]]></title>
        <description><![CDATA[Stories by Mirta Rotondo on Medium]]></description>
        <link>https://medium.com/@mirtarotondo?source=rss-85ddf429d16a------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*V67wY0c_FsEqYtIZf3na7A.jpeg</url>
            <title>Stories by Mirta Rotondo on Medium</title>
            <link>https://medium.com/@mirtarotondo?source=rss-85ddf429d16a------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 12:29:32 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@mirtarotondo/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[UX/UI guides: how to optimise your open banking user journey]]></title>
            <link>https://medium.com/@mirtarotondo/ux-ui-guides-how-to-optimise-your-open-banking-user-journey-80a11c20cd4?source=rss-85ddf429d16a------2</link>
            <guid isPermaLink="false">https://medium.com/p/80a11c20cd4</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[ux-guide]]></category>
            <category><![CDATA[ui]]></category>
            <category><![CDATA[open-banking]]></category>
            <dc:creator><![CDATA[Mirta Rotondo]]></dc:creator>
            <pubDate>Tue, 19 Jan 2021 12:16:41 GMT</pubDate>
            <atom:updated>2021-01-19T12:16:41.985Z</atom:updated>
            <content:encoded><![CDATA[<h3>UX/UI guides: How to optimise your open banking user journey</h3><h4>Give your users a better in-app experience by following these simple implementation techniques</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YZ7_3US5EY-d2740vTAP1w.png" /></figure><blockquote>At TrueLayer, we’ve been opening up finance since 2017. In the process we’ve learned a thing or two about what drives your users to connect their bank account, as part of an open banking flow. In this article, we cover some of our top tips for improving the user experience in your app — whether it’s Account Information Services (AIS), Payment Initiation Services (PIS) or both — to increase your conversion rates and make your users even happier.</blockquote><p>Before we get started, let’s clarify what we’re talking about in this article.</p><p><strong>Open banking flow. What’s that?</strong></p><pre>By <em>open banking flow</em> we are referring to a portion of your overall flow. Specifically: from the moment a user selects an open banking method to either connect their account (AIS) or make a payment (PIS), until the completion of that journey.</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YP2bbt8_Mjvko5JYQ0ghfA.png" /></figure><p><strong>Completion rate? Conversion rate?</strong></p><pre>When we talk about <em>completion rate</em> or <em>conversion rate</em>, we are referring to the percentage of users that successfully connect their bank account, make a payment, or both.</pre><p><strong>What results can you expect to see by following the suggestions in this guide?</strong></p><pre>A/B testing and client implementations have seen conversion rates increased by up to <strong>23%</strong>.</pre><p>All clear? Good! Now let’s identify the scenario that best describes your use case before we dig into the best practices to improve your flow.</p><blockquote>📥 Too much reading? <a href="https://docs.google.com/presentation/d/1wQ77gCLI63erAY2xJaNkw6O1ndkzs9Lk9L_ogkJJPJY/edit?usp=sharing">Download</a> our visual guide instead.</blockquote><h3>Scenarios and user motivation</h3><p>What does your app do? Is it a marketplace? A PFM app? An online casino? Whatever the industry, chances are it will fit into one of the following use cases:</p><ol><li><strong>PIS only:</strong> top-ups / bank-to-bank transfer / digital wallets</li><li><strong>AIS only: </strong>identity verification / account aggregation</li><li><strong>AIS + PIS:</strong> a little bit of both</li></ol><p>When it comes to new technologies, hard data shows that both demographics and use case (the actual reason why a user is doing something) play a vital role in completing a flow. We’ll refer to these as the user’s <strong>motivation</strong>. So what motivates a user to finish the flow? What’s their reward? Well, <a href="https://www.nngroup.com/videos/it-depends-ux-context/">it depends!</a></p><p>To understand what we’re talking about, let’s look at two examples.</p><p>Think about the motivation someone has to request a loan to buy their first house, compared to someone who wants to put aside some cash for a holiday. One is requesting money, the other simply thinking about saving money. The loanee is taking an action: requesting a big chunk of money for what is a life-changing decision. The saver is considering doing something, but hasn’t made any commitments yet.</p><p>These different motivations cause different user behaviours.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ft_C9MfvCQ2a7LAbcGPE3g.png" /></figure><p>When looking to optimise your user’s open banking journey, it is vital that you understand their motivation. So your first port of call should be to build user personas. Really dig deep into the reasons why a user uses your app, and try to <strong>understand their emotional and rational states</strong>. This will help you <strong>empathise with your users</strong> and discover how you can better serve them.</p><p>Next you need to ask yourself: <em>how often will my user go through this flow? </em>Is it a one-time only deal, or is it something that they might repeat multiple times every month?</p><h4><strong>First-time user vs returning users</strong></h4><p>Whether your user passes through the flow multiple times, or just once, plays a big role in how your journey should be designed. The reason, once more, comes down to your user’s motivation.</p><p>In the world of AIS, think about first-time consent vs re-consent. Or with PIS, think account top-ups. Once the user has been through the journey, they’ve already answered most of the key questions you needed to ask them. So avoid causing frustration by asking them the same questions all over again.</p><p>The <strong>design of a first-time user flow vs a returning user flow should be different</strong>. We’ll explain how in the next section.</p><h3>Best practices</h3><p>Through our research we have identified four major principles that will help you improve your conversion rate. They are:</p><ol><li>💡 avoid ambiguity</li><li>👀. be transparent</li><li>☝️ use common patterns and shortcuts</li><li>✏️. simplify complexities</li></ol><p>Now let’s translate these into what the user actually wants:</p><ol><li>to follow a journey that is familiar</li><li>to clearly understand what they are doing</li><li>to perform actions that make sense</li><li>to read only what they want to read</li></ol><p>The above points are all true whatever your scenario is (AIS, PIS, both). However, some are more relevant to first-time users (1,2,4), while others more relevant to returning users (1,3).</p><h3>1) 💡Avoid ambiguity: users like familiarity</h3><p>If you are a TrueLayer customer, you are either using our user interface (UI) or have created a custom flow for your app. Either way, it will look something like this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KoaUGM04Twq7IZGl242M4Q.png" /></figure><p>Suddenly entering a different UI and being redirected to something outside of your brand experience <em>can</em> break <a href="https://blog.truelayer.com/ux-ui-guides-how-to-increase-open-banking-adoption-71513643827e">trust</a>. But not always. If the external UI has already been optimised for conversion, or (better yet) is already known and trusted by the user, it can actually convert better.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9JjHcWeVta7KwtPH1Vmo5g.jpeg" /></figure><p>To reduce ambiguity and create a more familiar journey, there are two key points you need to focus on:</p><ol><li>branding your UI</li><li>avoiding content duplication</li></ol><h4><strong>Branding your UI</strong></h4><p>Creating a consistent brand experience across the entire user journey is less disruptive and converts better than introducing a non-branded UI. To do this you’ll need to opt for a fully white-labelled solution, and design and build your own bank selection and consent pages.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*r9vtj304NEc_BE0NBIJFfQ.jpeg" /></figure><p>Alternatively, you can use the TrueLayer flow to save time and go live with your product right away. For Data, you can easily customise the UI, its colours, upload your logo, and update the copy all in our <a href="https://console.truelayer.com/data/customisation">Console</a>. Unfortunately, Payments customisation is a little more limited, but we’ve made it a priority to update these features and you will soon be able to take your payments experience to a whole new level.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vHufnC6gPf0Gm6Ixpp61_g.jpeg" /></figure><h4><strong>Avoiding content duplication</strong></h4><p>If you are using your own UI, feel free to skip this section and jump to the next. If you are using our dialogs (or you are a TrueLayer agent), read on.</p><p>We often come across client UIs that contain duplicate content already covered in our dialogs, especially regarding consent and compliance.</p><p>This creates friction.</p><p>If you’re required to use the TrueLayer flow because we are the regulated body, it’s highly recommended that you leave that stuff to our dialog. Our screens cannot be removed from the flow, and there’s simply no need to explain the same thing twice — you run the risk of frustrating or even scaring off your user.</p><h3>2) Be transparent: users want to understand what they are doing 👀</h3><p>Content performs better when it’s contextualised. So give your flow context and <strong>create UX goals based on user motivation</strong> for each and every element. That way you can make sure that everything is tied to user interaction and creates a clear, easy to follow journey.</p><p>With that covered, there are two additional steps you can take to further ensure transparency:</p><ol><li>divide the flow into logical sections</li><li>explain errors, success states and redirects</li></ol><h4><strong>Divide the flow into logical sections</strong></h4><p>Dividing a flow into sections helps the user understand what action they are about to perform. And by following general information architecture (IA) principles such as <em>focused navigation</em> and <em>objects</em>, you can achieve great results.</p><p>The <em>principle of</em> <em>objects</em> suggests that you should consider the content of your flow as a living thing with its own lifecycle, behaviours and attributes. By understanding and defining the nature of this content into classes, you can create better structure and a more effective journey. For more information, <a href="https://medium.com/@hollabit/the-eight-principles-of-information-architecture-6feff11f907a">this article covers the eight principles of information architecture in more detail</a>.</p><p>The <em>principle of focused navigation</em> suggests that you should keep navigation clean to avoid confusing the user. Give each page a clear purpose, and don’t mix subjects or introduce unnecessary links.</p><p>In practice this can be achieved by grouping steps together into relevant sections. For example: the <em>select payment method</em>, <em>select your bank</em> and <em>make a payment</em> steps can be combined into a section called <em>top up</em>.</p><p>If your custom flow has more than five screens, we recommend that you make the steps of the flow visible in the UI. This will help your user understand where they are in the journey, reduce their anxiety and increase conversion.</p><p>On the other hand, if you are redirecting to a third party provider’s UI, it’s best to omit the steps as it can cause confusion.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Yx15ggbGRfECFtgZn1bA2w.jpeg" /></figure><h4><strong>Success and errors states</strong></h4><p>Error handling is one of my favourite UX topics. I cannot overstate how important it is for designers, engineers and product managers to dedicate more time to this critical part of the design process.</p><p>And while some may say that it’s better to design to prevent errors rather than designing for error states — which you should — I want to stress that <strong>errors will still occur</strong>. Especially when technology is dependent on third party integrations.</p><p>In the case of open banking, most errors originate from the banks’ APIs. And a lot of the time the banks do not provide specific information about why the error occurred, making it difficult to pass on a meaningful message to the user, or create a suitable API response.</p><p>In this situation, we need to create more generic error pages that will <strong>reassure the user and provide next steps</strong>. So give your user a clear action to perform — you could include a simple <em>try again</em> button, for example.</p><p><strong>Error pages that look like dead ends, with no available action or unclear error message, are huge no-nos.</strong> They almost certainly mean losing the user from the flow as they will have no choice but to turn back. Even worse, you run the risk of losing the user forever as <a href="https://www.jstage.jst.go.jp/article/ijae/15/2/15_IJAE-D-15-00042/_article/-char/ja/">a bad experience can translate to brand abandonment</a>.</p><p>On the flip side, when a status returns as successful, let the user know. This may seem obvious, but we’ve encountered countless client flows that omit this step after a money transfer or successful authentication. Leaving the user wondering whether their money is safe or the transaction actually went through…</p><p>So yes, add that positive friction. It’s vital for ensuring your user’s peace of mind.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mrLN5UIlPIZz9UUNZXcPZQ.jpeg" /></figure><h3>3) Use common patterns and shortcuts: users want to perform actions that make sense ☝️</h3><p>In the section above we learned that using<a href="https://www.interaction-design.org/literature/article/the-magic-of-semantic-interaction-design"> semantic IxD practices</a> and dividing a flow into sections helps the user better understand what action they are about to perform. Now, let’s dive a little deeper into why this is particularly useful for open banking.</p><p><a href="https://www.emarketer.com/content/us-adults-will-spend-over-three-hours-per-day-on-mobile-apps-2020">Statistics</a> tell us that adults spend an average of 50 days a year looking at their phone. That’s more than a month and a half spent learning what good UX looks like. So it should come as no surprise that the average user demands a first class experience — especially when it concerns their money.</p><p>Which is why you should integrate common UX patterns into what you’re building. There’s no need to reinvent the wheel every single time when you can simply re-use existing logic and apply that to your use case.</p><h4><strong>Use common UX patterns</strong></h4><p>When designing your app’s flow, ask yourself the following questions:</p><ul><li>Why is this page at this step of the flow?</li><li>What are the steps before and after this one?</li><li>Are there any technical reasons for its position in the flow?</li><li>Can we propose changes to the backend logic to improve user experience?</li><li>Can we combine two screens into one?</li></ul><p>Let’s look at a checkout journey for an example. Where should the <em>select amount</em> page sit in the flow? Before or after the bank selection? At the beginning of the flow, or closer to the make payment button?</p><p>If you don’t have any technical constraints, just follow common patterns. In this case, the standard is:</p><ol><li>select item/amount</li><li>select payment method</li><li>select your bank</li><li>make payment</li></ol><p>Stick to this order. If things can be merged together (such as <em>select amount</em> and <em>payment method</em>), merge them. Shorter flows convert better in some scenarios.</p><p><strong>A word of warning:</strong> all of the above is true, until you come face to face with your conversion rate data. Remember that user motivation varies from case to case, so if your conversion rate is low, it’s time to challenge your assumptions. A/B testing will help you find the truth. Data is king, after all.</p><h4><strong>Use shortcuts</strong></h4><p>In our previous article on<a href="https://blog.truelayer.com/ux-ui-guides-how-to-increase-open-banking-adoption-71513643827e"> how to increase open banking adoption</a>, we explained that users just want to get things done and get on with their day. They don’t want to jump through hoops, make difficult choices or be confused by complicated next steps. So it follows that using shortcuts and making the journey more logical and digestible is an absolute must to increase conversion.</p><p>This is true both for first-time and returning users, but is definitely more important for the latter. When it comes to payments user journeys, it is good practice to save the user’s previous choices in order to avoid asking them the same things over and over.</p><p>For example: if you already know the user’s preferred bank, don’t ask them again. Simply show it as a pre-selected option.</p><p>Still, don’t take things for granted. Your user may want to move money from a different account or wallet, so give them an extremely simple way to change their default bank. Do <strong>not</strong> hide this option in complex account settings or secondary menus.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FHj24O91UbZ6klq29b3VKA.jpeg" /></figure><h3>4) Simplify complexities: users only want to read what they want to read ✏️</h3><p>Dulcis in fundo, the real key differentiator for your conversion rate: simplicity.</p><p>A clear user journey is a high-converting journey. And the rules here are straightforward:</p><ol><li>use visual hierarchy</li><li>keep font size readable</li><li>use a concise and friendly tone of voice</li><li>reduce the number of steps in the flow (where possible)</li></ol><p>Don’t hide or delete relevant information. Include it in the UI and make it accessible, just make sure it’s not intrusive. Some ways of doing this:</p><ol><li>progressive disclosure (breaking information up into optional and easily digestible chunks)</li><li>positive friction (introducing extra screens that help the user navigate)</li></ol><p>All of the above points have been covered in details in our previous UX/UI article. If you want to know more, <a href="https://blog.truelayer.com/ux-ui-guides-how-to-increase-open-banking-adoption-71513643827e">you can check it out here</a>.</p><h3>Wrapping up</h3><p>So all said and done, what does this actually mean for your conversion rates? A/B testing and client implementations have resulted in a <strong>23% increase in conversion rate, </strong>which means happier users and an improved brand experience. And who doesn’t want that?</p><p>Stay tuned for the next in our series on increasing open banking adoption where we will be deep diving into different use cases and industries, and dragging up some serious pearls of wisdom based on top-performing client integrations. <a href="https://blog.truelayer.com/tagged/ux-guide">Watch this space</a>.</p><h3>✏️<strong> Optimisation checklist</strong></h3><p>As a little bonus, here’s an optimisation checklist you can use to make sure you’ve covered all bases:</p><pre>☐ build personas to understand users emotional and rational states<br>☐ explore user motivations<br>☐ design different flows for first-time and recurring users<br>☐ brand your flow<br>☐ remove duplicated content<br>☐ divide the flow into logical sections (eg combine top up screens)<br>☐ assess changes to the backend logic to improve user experience<br>☐ combine screens to make the flow simpler (optional)<br>☐ design a page for successful states<br>☐ design error pages so that there are no dead ends<br>☐ introduce positive friction before redirects<br>☐ save previous user choices (eg preferred bank)</pre><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=80a11c20cd4" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[UX/UI guides: how to increase Open Banking adoption]]></title>
            <link>https://medium.com/@mirtarotondo/ux-ui-guides-how-to-increase-open-banking-adoption-71513643827e?source=rss-85ddf429d16a------2</link>
            <guid isPermaLink="false">https://medium.com/p/71513643827e</guid>
            <category><![CDATA[ui]]></category>
            <category><![CDATA[open-banking]]></category>
            <category><![CDATA[ux-guide]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Mirta Rotondo]]></dc:creator>
            <pubDate>Tue, 24 Nov 2020 14:39:42 GMT</pubDate>
            <atom:updated>2021-01-05T12:27:01.560Z</atom:updated>
            <content:encoded><![CDATA[<h4>The best UX/UI practices to boost your product’s open banking conversion. Simply set them up, sit back, and watch the magic happen.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*AUbfgjS3flg_HYiBkegkiQ.png" /></figure><blockquote>Having connected several million accounts since 2017, we’ve learned a thing or two about your users. And by deep diving into behavioural data, we’ve managed to identify four key factors that affect whether they choose open banking over other available options. So if you want to increase open banking adoption, you’ve come to the right place…</blockquote><p><strong>First thing first, what do we mean by open banking adoption?</strong></p><pre>In this guide we’re using open banking adoption to refer to the percentage of users that select open banking to either connect their account (AIS) or make a payment (PIS).</pre><p><strong>Why should you care?</strong></p><pre>Because open banking is better for everyone — it’s cheaper, faster and more secure when compared to other methods such as cards.</pre><p><strong>How will it benefit your customers?</strong></p><pre>Open banking makes paying simple, and gives your users greater control over their financial lives.</pre><p><strong>What results can you expect to see?</strong></p><pre>Early stage testing with our clients has seen a serious increase in open banking adoption of <strong>10%</strong> (but this is just the beginning).</pre><p>So if that sounds up your street, read on to discover how to increase open banking adoption with your users.</p><blockquote>📥 Too much reading? <a href="https://info.truelayer.com/how-to-increase-open-banking-adoption">Download</a> our visual guide instead.</blockquote><h3>Key factors</h3><p>Through our research we have identified <strong>four key factors that affect whether first time users choose open banking</strong> over other methods:</p><ol><li>⏱️ <strong>Convenience</strong>:<em> will this take long?</em></li><li>💎 <strong>Clarity</strong>: <em>what exactly do I need to do?</em></li><li>👐 <strong>Familiarity</strong>: <em>have I done this before?</em></li><li>🔒 <strong>Security</strong>: <em>is this safe?</em></li></ol><p>How you specifically address these factors will differ slightly depending on your industry, user demographics and whether your app is using AIS or PIS. Regardless, keeping these questions in mind will help you to both increase open banking adoption and <strong>deliver an all-round better experience for your users</strong>.</p><h4>⏱️ Convenience: users will choose the most convenient option</h4><p>When it comes to new technologies, users expect their lives to be made easier, with faster ways to get simple tasks done. They don’t want to adopt new methods unless it’s going to save them (or their future selves) time. So they’ll ask themselves:</p><ul><li><em>Will this take long?</em></li></ul><p>Verifying identity via traditional methods can take the user several minutes, plus the extended time it can take for manual verification which often results in the user returning to the flow days later. Similar issues affect wallet top-ups and the settlement of funds. Payments can be initiated instantly via cards and other methods, but money tends to actually move days later.</p><p>With TrueLayer’s open banking APIs, identity verification takes an <strong>average of 35 seconds</strong>. Money settlement into a wallet is <strong>near instant</strong>. This is a huge incentive for your users, so why not brag about it?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VHPqinobAZFD-ABlnDosow.png" /><figcaption>Design for convenience: best UX/UI and copy practices</figcaption></figure><h4>💎 Clarity: the clearest journeys convert the best</h4><p><strong>Users just want to get things done and get on with their day. </strong>They don’t want to jump through hoops, make difficult choices or be confused by complicated next steps. To avoid these issues, answers to the following questions should be built into your flow:</p><ul><li><em>What exactly do I need to do?</em></li><li><em>Is this going to be difficult?</em></li></ul><p>To answer the first question, the solution is as simple as using pre-selected fields and indicating recommended options. (Yes, really.) The second can be a little more complicated.</p><p><strong>Most people can only comfortably handle </strong><a href="https://www.instructionaldesign.org/theories/information-processing/#:~:text=Miller%20(1956)%20presented%20the%20idea,chess%20positions%2C%20or%20people&#39;s%20faces."><strong>five to nine chunks of information</strong></a><strong> at any one time.</strong> The higher the number, the higher the cognitive load, and the less a user can actionably understand. When a user first tries open banking they’re introduced to a new financial concept, a never-before-seen authentication process, a litany of consents and an entirely new company — TrueLayer, in our case. That’s a lot for anyone to grasp.</p><p>The temptation is to add content and explain the complexity away, but we’ve found that can often cause more confusion. Instead, we suggest going for a <em>less is more</em> approach. Employ the concept of progressive disclosure by displaying only the most important information and actions, with the option to <em>read more</em> or <em>view</em> <em>advanced settings</em> by request. You can also look to use positive friction, but more on this later.</p><p>Long story short: <strong>give your users more, but only when they ask for it</strong>. This will improve learnability and efficiency, and reduce error rates. If they really want to know something, they’ll click. We promise. 👌</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UFskv62ljPfq9k2jhSHkEg.png" /><figcaption>Design for clarity: best UX/UI and copy practices</figcaption></figure><h4>👐 Familiarity: interactions should feel intuitive</h4><p>In UX, the word familiarity is almost synonymous with trust. To make your users feel like they’re at home, you need to address questions like:</p><ul><li><em>What is this?</em></li><li><em>Have I used it before?</em></li></ul><p>And most importantly:</p><ul><li><em>Do I trust it?</em></li></ul><p>Whenever possible, <strong>building on users’ existing knowledge of how a system works is the secret sauce for success</strong>. If a user intuitively understands the process, and knows how things will pan out, their anxiety is reduced and the likelihood of them completing the process is greatly increased.</p><p>But what do you do when the product or service you’re introducing is completely new? How do you drive the user to choose <em>that</em> thing over another?</p><p>Right now, <strong>most users don’t know what open banking is</strong>, let alone how to use it. And that’s not going to change over night. So if we want to increase awareness and adoption, the burden of responsibility is on us (that <em>us</em> includes you) to make open banking feel familiar.</p><p>We’ve found that the two most effective ways of doing this are: <strong>better</strong> <strong>copywriting</strong> and <strong>positive friction</strong>.</p><h4><strong>Copywriting</strong></h4><p>Some of our customers have used the words <em>open banking</em> or <em>TrueLayer </em>in titles or calls to action. <strong>This is inadvisable.</strong> While the consumer <em>may</em> have heard of open banking, most have not heard of TrueLayer. So we suggest using more recognisable terms in titles and CTAs, and using <em>open banking</em> and <em>TrueLayer </em>in body copy and descriptions. This will <strong>build familiarity</strong>, association and trust in the long term, and all without interrupting the user experience.</p><h4><strong>Positive friction</strong></h4><p>In both fintech and UX, we’re only ever two breaths away from talking about how we need to remove friction from one thing or another. However, sometimes friction can produce a positive impact on a user’s experience, especially when they need to learn new concepts.</p><p>By <strong>adding additional steps to the flow</strong>, you can build trust and better help users to navigate the journey. But be warned: this only works if you have employed positive friction in other aspects of your products, such as during the onboarding process. The repetition of these patterns will make it easier for the user to recognise what they’re being asked to do and to know how to react.</p><p><strong>Positive friction should give the user more context</strong>, and explain what will happen next. These extra steps could include additional information like “you’ll only have to do this once”, or a provide a simple explanation of what TrueLayer is. And they are most effective when combined with illustrations and icons that make them more identifiable and user-friendly.</p><p><strong>We only recommend adding one, two steps max.</strong> More than this and you run the risk of frustrating the user. And if you don’t use positive friction anywhere else in your app, it’s probably best to stick to progressive disclosure patterns instead.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uOlrRP-UFaz1ij7RWatH-A.png" /><figcaption>Design for familiarity: best UX/UI and copy practices</figcaption></figure><h4>🔒 Security: users must trust the method</h4><p>Security is an essential element of any digital transaction, and most users will abandon a flow if they have even half a reason to mistrust the authentication method. So, similar to the previous point, users want to know:</p><ul><li><em>Is this safe?</em></li><li><em>Do I trust it?</em></li></ul><p>When it comes to selling a new method, <strong>your focus should be on</strong> <strong>relieving user anxiety</strong>. This means balancing positives like convenience and speed, with vital trust indicators like data safeguarding and social proof.</p><p>How do you do this?</p><p>Progressive disclosure and positive friction. Which one you choose will depend on the UX patterns you’re already using in your app, but the point is that you can use these content spaces to spell out what happens to the user’s data and what safeguards are in place. Just <strong>make sure it’s all written in plain English.</strong></p><p>Reassuring terms like <em>read-only</em> and <em>bank-grade</em> can make users feel more confident, and familiar icons like padlocks 🔒 help to underscore the point.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jGK6SSwTLOwKk7DDu6vKvw.png" /><figcaption>Design for security: best UX/UI and copy practices</figcaption></figure><h3>The all important order of importance</h3><p>We talked about time, clarity, familiarity and security. In that specific order. And for good reason.</p><p>In the world of open banking, most users are <strong>first-time users</strong>. This is especially true of AIS service users, who need only connect their bank account to an app once and then re-authenticate in a few months. This makes the user journey unique, and means it needs to be treated as such.</p><p>By arranging page elements in the order we’ve outlined, you can help first-time users choose open banking by demonstrating that:</p><ol><li>It will save them time</li><li>It is super easy to use</li><li>Millions of people just like them already trust it</li><li>Their money and data are safe</li></ol><p>Of course, this isn’t always the case. When it comes to things like wallet top-up, users might encounter your open banking flow multiple times a month. In this situation, the order should be treated a little differently, and familiarity will take the top position. Always consider what will be the most important factor for your user given their entry into the flow.</p><h3>The bottom line</h3><p>So all said and done, what does this actually mean for your conversion rates?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*nCZ45vPYoutvtrxAhNci3Q.gif" /></figure><p>Early stage testing has resulted in a <strong>10% increase in adoption rate for our customers, </strong>which translates to a considerable amount saved on transaction costs, as well as the opportunity to offer personalised services to more of their users.</p><p>And that’s just from making a few minor tweaks here and there, not implementing all the changes we’ve suggested in this article.</p><p>If this has whet your appetite, you’re in luck. This is just the first in a series of studies we are publishing on how improved UX and consumer awareness will push for greater open banking adoption. <a href="https://blog.truelayer.com/tagged/ux-guide">Watch this space</a>. 👀</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=71513643827e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Design at TrueLayer: our shared principles and values]]></title>
            <link>https://medium.com/@mirtarotondo/design-at-truelayer-our-shared-principles-and-values-ea601da186d7?source=rss-85ddf429d16a------2</link>
            <guid isPermaLink="false">https://medium.com/p/ea601da186d7</guid>
            <category><![CDATA[consistency]]></category>
            <category><![CDATA[values]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[user-centered-design]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Mirta Rotondo]]></dc:creator>
            <pubDate>Wed, 11 Nov 2020 11:22:06 GMT</pubDate>
            <atom:updated>2020-11-11T11:22:06.909Z</atom:updated>
            <content:encoded><![CDATA[<h4>Our secret sauce for building a close-knit design community</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tH-pobncXZz67kLixGNABQ.jpeg" /></figure><blockquote><strong>TL;DR:</strong> Designing for fintech isn’t easy. This fast-paced market throws up new challenges and countless complexities every single day. With demand high and quality a must, discover how designers at TrueLayer find balance in the world of open banking.</blockquote><p>Hey. I’m Mirta, VP of Brand &amp; Design at TrueLayer. 👋</p><p>I lead a diverse team of talented designers who work across all functions of the organisation. Together, our aim is to disrupt the boring, old-school image of finance, and inspire others through interesting and intelligent design. <strong>Because we think banking is cool. 🤘</strong></p><p>Here’s how.</p><h3>🎯 Design org mission</h3><pre>Our mission is to increase <strong>open banking adoption</strong> by creating a more open, modern and human experience.`</pre><h3>🚶‍♀ How do we get there?</h3><pre>By establishing a <strong>positive</strong>, memorable and recognisable<strong> experience</strong> for those who interact with our brand.</pre><h3>🛠 How do we make this real?</h3><pre>By following our purpose, shared values and design principles.</pre><p>When it comes to delivering results, <strong>striking balance between alignment and autonomy is incredibly important</strong>. Though finding the right balance often isn’t easy.</p><h3>A bit of backstory</h3><p>Back in 2017 there was no such thing as the Design function at TrueLayer. It was just me, <a href="https://medium.com/u/97098943d64d">Desislava Genova</a>, <a href="https://medium.com/u/c062ce61a044">Nicki Clark</a> and Adobe. Actually, that’s not strictly true. There was that half-baked library of Sketch components — which would eventually evolve into our killer design system, Prisma — too. I’m proud to say that since then, the team has seven-x’d in size and has a seat at most TrueLayer tables.</p><p><strong>But scaling wasn’t easy</strong>. As the team got bigger, everything started to move faster. Delivery expectations grew and things got, well, messy. We were being pulled in different directions by business demands, and doing the work of 10 with just three.</p><p>It soon became clear that we needed to reorganise. To create an environment that increased everyone’s independence while keeping teams aligned and engaged. Simple enough, huh?</p><p>So Desi, Nicki and I sat on the third floor bleacher and began discussing ways to do this. Discussions became messy notes. Messy notes became slightly less messy notes. <em>They became messy documents</em>…</p><p>Then before too long (read: actually months later), we had something. Four shared values and four design principles. An ethos for us to design by. A way to <strong>shape our creativity</strong>, <strong>minimise indecision</strong> and <strong>keep our north star squarely in sight</strong>.</p><h3>Our shared values</h3><h4>TrueLayer’s designers are…</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-ItvDkBky6uYqNXbqtf0Mw.jpeg" /></figure><p><em>Why are we doing it?</em></p><p>Continuous research helps us deliver better solutions even faster. So if we don’t know something, we ask. If we don’t know how to do something, we learn. If we <em>do</em> know, we share.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WekUVGdgQEqHKb2Ecm0i7A.jpeg" /></figure><p><em>What directed your decision?</em></p><p>By using data to drive our decisions, we can really understand how designs perform. And by turning those results into insights, we can hone our ability to build truly user-centered products.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*a7kfYdG8FK2H_oTDXaWmsA.jpeg" /></figure><p><em>Can you use some help?</em></p><p>We take risks and own what we do. But we look to our team for insight and new ideas, rather than relying solely on ourselves. Because talent wins games, but teamwork wins championships.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LiOdbiSpNrMaku4n-Tt2iw.jpeg" /></figure><p><em>Have you incorporated feedback?</em></p><p>Whether we’re building new products or updating existing ones, end users, clients and colleagues are our eyes and ears. Feedback and testing are paramount to improve our products.</p><h3>Our design principles</h3><h4>TrueLayer design is…</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ttAbRELd-Sy9balzEF1EKg.jpeg" /></figure><p><em>Can anyone consume it easily?</em></p><p>Our design recognises cultural diversity and human values. By putting people at the centre of everything we do, we can create better performing products that work for everyone.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wSaoqI0nCt_ThzQ4v2Do9g.jpeg" /></figure><p><em>Can you get rid of something?</em></p><p>Less is more. Doing away with redundancies and distracting elements delivers higher engagement, greater usability and better aesthetic. Creating a more seamless experience.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IRM9EqH8t8YcVZjt_DwIVw.jpeg" /></figure><p><em>Have you introduced a new element?</em></p><p>We use Prisma components and follow our design primitives and Gestalt principles. All to keep friction away from the user experience and make new features feel natural.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IT5UlmxMjDcO7GuSsLOt2g.jpeg" /></figure><p><em>Is this design saving your future time?</em></p><p>We design to solve future problems, not today’s tasks. So our products need to be able to evolve and adapt. Easy to update and quick to implement. To keep us ahead of the curve.</p><h3>Key learnings</h3><p>So what did we learn from this journey?</p><p>When it comes to creating a set of team values and principles, there are three key things to focus on:</p><ol><li>structure</li><li>usage</li><li>longevity</li></ol><h3>1) Structure 🏗</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*B1DFtXiv_IZYxTk7.jpg" /></figure><p><strong>Objective</strong></p><p>Values and principles need to be associated with <strong>clear objectives</strong>. And these objectives need to align with your organisation’s mission.</p><p>Like: <strong>Be data-driven</strong> <em>so we can design more human experiences</em>.</p><p><strong>Action</strong></p><p>You should also make your values and principles <strong>actionable</strong>. Think of the objective as the <em>why</em> and the action as the <em>because</em>.</p><p>Why should I be data driven? <em>Because we want to </em><strong><em>make facts, not assumptions</em></strong>.</p><p><strong>Question</strong></p><p>We also found that it’s useful to associate <strong>simple questions</strong> with each value or principle. This gives teams a foundational review process that they can apply to their work, before they reach out for further feedback.</p><p>For example: <strong>What directed my decision</strong> during this particular project? I specifically needed to reduce the bounce rate on this page and designed around this requirement. We can use the bounce rate as a metric to understand how the new design performs.</p><p><strong>Icon</strong></p><p>Last but not least, <strong>make them visual</strong>. Associating visuals with your values is a great way to keep them fresh in your mind. 😉</p><h3>2) Usage 🧐</h3><p>Once you have your values and principles, it’s time to actually start using them. We found that the best way to do this was to <strong>ritualise them within our daily workflow</strong>.</p><p><strong>Technical reviews</strong></p><p>By asking the questions attached to each value or principle, designers can independently sort through initial doubts and better <strong>assess their own work</strong>.</p><p><strong>Performance reviews</strong></p><p>We found it super valuable to integrate our ethos into performance reviews, too. During one-to-ones with their teams, design leads provide feedback based on each value and principle. This approach gives us immediate insight into which areas the designer is exceeding in, and which areas need improvement. The results help managers <strong>nurture talent</strong> and provide designers with the <strong>tools and guidance</strong> they need to grow in their role, as well as to set <strong>clear expectations</strong> on delivery.</p><h3>3) Longevity ⏳</h3><p>The final thing we learned is that values and principles are not set in stone — <strong>they evolve along with the team</strong> and wider company needs.</p><p>At TrueLayer, we have iterated on ours multiple times and we’ll keep on doing that as we continue to grow. You see, we want our values and principles to be <strong>empathetic</strong> and truly <strong>represent the people using them</strong>, so it’s vital that we revisit them at set intervals.</p><p>Today, three years after their inception, our design values and principles are shared by more people than ever before. They’ve become essential to aligning our ever-growing team, especially as we’ve expanded internationally and continue to work remotely. And in times that we’ve felt isolated, they’ve provided a guiding light to keep us inspired.</p><p><strong>That’s the sort of balance we need to achieve our mission</strong>, and make banking a more open, modern and human experience. 🏦 🤗</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ea601da186d7" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Say hello to our brand new Console!]]></title>
            <link>https://medium.com/@mirtarotondo/say-hello-to-our-brand-new-console-8aee08e7003a?source=rss-85ddf429d16a------2</link>
            <guid isPermaLink="false">https://medium.com/p/8aee08e7003a</guid>
            <category><![CDATA[dx]]></category>
            <category><![CDATA[api-interface]]></category>
            <category><![CDATA[open-banking]]></category>
            <category><![CDATA[developer-experience]]></category>
            <category><![CDATA[banking-ui]]></category>
            <dc:creator><![CDATA[Mirta Rotondo]]></dc:creator>
            <pubDate>Tue, 10 Sep 2019 12:58:48 GMT</pubDate>
            <atom:updated>2019-09-10T12:58:48.044Z</atom:updated>
            <content:encoded><![CDATA[<h4>When it comes to picking a preferred API company, we know developers have the final word in the decision making process. We redesigned our Console from the ground up to foster automation and set the ground for a faster, more reliable product.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*kaqWSyNqXE3y1lJo.png" /></figure><p>After the series C we recently secured, our CEO Francesco Simoneschi <a href="https://blog.truelayer.com/today-and-tomorrow-180ef88fa4a0">shared his intentions</a> to invest more in one of the most valuable assets that an API company can think of: <strong>the developer experience</strong>.</p><p>Ensuring that all the developers integrating the TrueLayer’s APIs are happy, is vital to guaranteeing the success of our company. Because of that, we assembled a brand new team of designers and front-end developers focused on building a developer experience that is functional, stable, fast, easy to use, and clear. Because we believe that <strong>if it doesn’t work well, then it just doesn’t work</strong>. 🤓</p><p>To show you our commitment in fulfilling our promises, we have worked hard in the past few quarters to bring you a new version of the TrueLayer Console. 🎉 <strong>Let’s take a look at what’s new!</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZUkM7RZaLkY_lFrbLF9SoQ.jpeg" /></figure><h4>Improved on-boarding experience 👁️</h4><p>Creating your application with TrueLayer is now easier. A better design will guide first time users through each step of the wizard to better understand what is what and how we are handling things behind the scenes, for the sake of transparency.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DOn3J4V_L5dBP7J-NpB3VQ.gif" /></figure><h4>Multi-products</h4><p>Our full product offering is now supported in Console. Both Data API and Payments API details can be configured in the “application settings” page. But there’s more: getting started guides and plan upgrades are now integrated in an effort to <strong>prepare the ground for a complete self-serve experience</strong>.</p><h4>Customisation 🎨</h4><p>We understand the importance of <strong>brand recognition</strong> and we believe that incorporating your brand values is essential for a successful UX. A branded UI not only provides a more natural and harmonic feeling of the brand, but it also increases credibility. Our clients can now customise the Truelayer Dialogs autonomously, directly from our Console. From logo upload, skipping specific steps of the flow, background colour, to text updates and more, your branded experience is just a colour picker away!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*m39Clwi2nTepOmdGjWv9dA.gif" /></figure><h4>Auth link builder</h4><p>Our plan to expand into new geographies and to build global connectivity will inevitably add complexity to our APIs. The greater our reach, the more we’ll have to support new access methods, provider brands, groups, and types, in a thoughtful way that is suited to each country or market. However, any new functionality from our expansion shouldn’t create friction for the developers who are integrating with our product. So, we have done our best to <strong>minimise the complexities for you</strong> by providing a clear and easy to use interface.</p><p>You can use our brand new Auth link builder to generate your Auth link in a few clicks. Tabs, filters, and bulk actions will help you go live with your product in no time!</p><p>Note: Please bear in mind, that this is not just an update to the UI: the Auth link itself is now using new flags and filters, so make sure you <a href="https://blog.truelayer.com/customise-your-providers-selection-page-with-the-new-auth-link-698419d93447">read about the new version</a> of the Auth link.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bRtekgINos32N1k6iDpkZQ.png" /></figure><h4>Alerts &amp; Notifications 📣</h4><p>One of our design team mottos is: “if it’s not clear, provide context!” Context is what makes seemingly unclear problems, tangible. With the introduction of alerts and notification, we aim at <strong>sharing the bigger picture with you</strong>. Need help understanding the behaviours of a specific UI component? Need more context on the latest regulatory updates that permit/prevent usage of a specific feature? All this will be embedded in the UI so you don’t have to go elsewhere to find your answers.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_LS18S0mVqpac3IaVkwBEA.gif" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZUkM7RZaLkY_lFrbLF9SoQ.jpeg" /></figure><h4>And more… 😎</h4><p><strong>Tailored content</strong></p><p>Whether you are a client testing in the Sandbox environment, a client interested in using one product only, both of them, or a TrueLayer Agent, our Console will only show content that is relevant for you. Because you deserve an experience that is built around your needs and not the other way around.</p><p><strong>100% Responsive</strong></p><p>We built the new Console with our proprietary design system: Prisma. Our styled components guarantee a consistent experience and adapt to a beautifully hand crafted grid so that you can integrate our APIs from (almost) any device and browser. Sorry IE11… 🤷</p><p><strong>GDPR updates</strong></p><p>Your privacy is golden. We are always updating the structure and design of our product to implement privacy by design. If you want to know more about something, or you have suggestions, please let us know!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZUkM7RZaLkY_lFrbLF9SoQ.jpeg" /></figure><p><strong>We </strong>❤️ <strong>Feedback</strong></p><p>We wanted to thank all of our clients who reached out to provide feedback and request new features. We built this new Console based on your suggestions and analysing usage data.</p><p>We really hope you will enjoy it and keep on getting in touch at design@truelayer.com so that we can keep on improving your experience and higher the standards of our products.</p><p>Ad maiora! 💪</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8aee08e7003a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Customise your providers selection page with the new Auth link]]></title>
            <link>https://medium.com/@mirtarotondo/customise-your-providers-selection-page-with-the-new-auth-link-698419d93447?source=rss-85ddf429d16a------2</link>
            <guid isPermaLink="false">https://medium.com/p/698419d93447</guid>
            <category><![CDATA[apibank]]></category>
            <category><![CDATA[open-banking]]></category>
            <category><![CDATA[bank-ux]]></category>
            <category><![CDATA[psd2]]></category>
            <dc:creator><![CDATA[Mirta Rotondo]]></dc:creator>
            <pubDate>Wed, 14 Aug 2019 16:18:16 GMT</pubDate>
            <atom:updated>2019-08-14T17:11:07.977Z</atom:updated>
            <content:encoded><![CDATA[<h4>We redesigned our Auth link to allow you to show only the banks that you want, when you want!</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*ol8oVI9_7HxzNPQo.jpg" /></figure><p>At TrueLayer, our connectivity team works hard to release new banks every month, so that your business can support multiple providers both in the UK and in other EU countries. But as they say… “with great power there must also come great responsibility!”. ✨After TrueLayer releases a new connector, the freshly added bank is immediately shown in the provider selection page of all your applications, to millions of users. Even though this sounds like a cool feature, for some of our clients it can be a problem. Why? Because they want to control which banks are visible in their applications, and when.</p><p>The <strong>customisation of the AuthDialog Provider Selection page</strong> is crucial to a healthy user experience. In fact, some clients want the flexibility to customise the bank selection page, based on their use case and audience type. This is to reduce the amount of time an end-user spends on the Provider Selection page looking for their bank. Further, this customisation allows the application to guide the end-user through the right authentication method.</p><p>As committed advocates of great journeys, our Developer Experience team endeavour to make our clients happy and rethink the way our Auth link was designed.</p><p>Let’s take a quick look at what the TrueLayer Auth link looks like. 🔍</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*2ZXuGKFxvjN-h9Pu.jpg" /></figure><h3>The anatomy of an Auth link</h3><p>The Auth link is a formatted link used by our clients to redirect the end-user to TrueLayer’s Authorisation Server.</p><p><strong>For those who are not familiar with it, this is what an old Auth link could look like:</strong></p><pre><a href="https://auth.truelayer.com/?response_type=code&amp;client_id=testingapp-1jsc&amp;nonce=3121014159&amp;scope=info%20accounts%20balance&amp;redirect_uri=https://truelayer.com&amp;enable_open_banking_providers=true">https://auth.truelayer.com/?response_type=code&amp;client_id=testingapp-1jsc&amp;nonce=3121014159&amp;scope=info%20accounts%20balance&amp;redirect_uri=https://truelayer.com&amp;enable_open_banking_providers=true</a></pre><p>Let’s disassemble it, and take a closer look at some of its <a href="https://docs.truelayer.com/#auth-link">parameters</a>:</p><pre><strong>client_id=</strong>testingapp-1jsc</pre><p>(the unique name of your application)</p><pre><strong>scope=</strong>info accounts balance</pre><p>(the permissions you will show to your user in the consent page)</p><pre><strong>redirect_uri=</strong>https://truelayer.com</pre><p>(where the user is redirected after the TrueLayer flow)</p><pre><strong>e̶n̶a̶b̶l̶e̶_̶o̶p̶e̶n̶_̶b̶a̶n̶k̶i̶n̶g̶_̶p̶r̶o̶v̶i̶d̶e̶r̶s̶</strong>=̶t̶r̶u̶e̶</pre><p>(the <strong>old flag</strong> used to select an authentication method)</p><p>So far, so good, but… what if you want to <strong>specifically select the banks</strong> that you show in your flow? Till yesterday, you couldn’t. But <strong>now you can. </strong>🎉</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*4x-IZCq3-RydAYaF.jpg" /></figure><h3>Yesterday: The old Auth link</h3><p><strong>Banks Opt-out only </strong>👎</p><p>The old version of the Auth link allowed you to opt-out from specific banks.</p><p>Problem was: every time we released a new bank, it would automatically be added to your flow, and you would need to update your Auth link to disable the newly released one. So, we decided to deprecate our predefined boolean groups:</p><p><strong>Deprecated Flags</strong></p><pre>e̶n̶a̶b̶l̶e̶_̶c̶r̶e̶d̶e̶n̶t̶i̶a̶l̶_̶s̶h̶a̶r̶i̶n̶g̶_̶p̶r̶o̶v̶i̶d̶e̶r̶s̶<br>e̶n̶a̶b̶l̶e̶_̶o̶p̶e̶n̶b̶a̶n̶k̶i̶n̶g̶_̶p̶r̶o̶v̶i̶d̶e̶r̶s̶<br>e̶n̶a̶b̶l̶e̶_̶o̶a̶u̶t̶h̶_̶p̶r̶o̶v̶i̶d̶e̶r̶s̶</pre><h3>Today: The new Auth link</h3><p><strong>Banks Opt-out and Opt-in </strong>👍</p><p>With the new Auth link, you can opt-out and opt-in only for the banks you want, when you want!</p><p>Let’s take a look at how we built the new logic.</p><p>🆕 <strong>Extended Provider ID Format</strong></p><p>First off we re-mapped our provider_ids format to fit the expansion into new countries and support multiple access methods. The new format is:</p><pre>CountryCode-AccessMethod-BankIdentifier</pre><p>🆕 <strong>Filtering and Grouping</strong></p><p>We decided to introduce filters to permit you to customise your permission page easily, instead of sticking to predefined boolean groups:</p><pre><strong>providers=</strong>uk-ob-lloyds uk-cs-hsbc</pre><p>You can now mix and match banks from different authentication methods, at your own convenience. In this way, only the banks you define in your Auth link will be returned.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*1bGIERPop-C1urmY.jpg" /></figure><p>But wait! What if you wanted to show all the banks of a specific authentication method, including the new releases in real-time? You can still do it by using predefined groups in the provider flag. For instance:</p><pre><strong>providers=</strong>uk-oauth-all</pre><p>On a side note, keep in mind that the <strong><em>providers</em></strong> filter is optional. If not defined, we will return the TrueLayer default which is currently <strong><em>providers=uk-oauth-all uk-cs-all</em></strong>.</p><p>In this context, you have probably heard about the <a href="https://blog.truelayer.com/scas-not-too-far-away-switch-to-ob-now-33d8b3693af5">upcoming introduction of SCA</a> — a new PSD2 legal requirement — which will require us to deprecate our UK Credential Sharing authentication method in the upcoming months. Therefore, we will update our Auth link default shortly to <strong><em>providers=uk-oauth-all uk-ob-all</em></strong>. No need to worry, we will ensure our clients are notified in due time. 👌</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*TYrEtEXmDsoywWyW.jpg" /></figure><h3>Implementation</h3><p>Ça va sans dire, we are <strong>deprecating the old version of Auth link</strong>, and we will discontinue its availability in ~ 6 months. You will have plenty of time to rebuild your link with the new flags.</p><p>Please note that during this transition phase, we will prevent the mixed usage of old and new flags. For instance, you won’t be able to select <strong><em>enable_credentials_sharing=true and providers=uk-cs-lloyds</em></strong> at the same time, because providers will override <strong><em>enable_credentials_sharing</em></strong>.</p><p>All of these changes are taking place on our side. To help you update your integration, we will be updating our documentation. If you cannot wait to use the new Auth link, and need a bit of help customising it, see the <a href="https://truelayer.zendesk.com/hc/en-us/articles/360019754134">FAQs </a>in our Support portal, or get in touch with our CSM team at <a href="/service/mailto:csm-team@truelayer.com">csm-team@truelayer.com</a>.</p><p>Need some automation? No worries! We are about to release a new improved version of Console, where you’ll be able to generate your new Auth link using the <strong>new Auth link builder</strong>.</p><p>Stay tuned! 🤘</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*2ya3RZo7I3uXL3aY.jpg" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=698419d93447" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Introducing the TrueLayer Sandbox V1]]></title>
            <link>https://medium.com/@mirtarotondo/introducing-the-truelayer-sandbox-v1-82a56ee8214d?source=rss-85ddf429d16a------2</link>
            <guid isPermaLink="false">https://medium.com/p/82a56ee8214d</guid>
            <category><![CDATA[open-banking]]></category>
            <category><![CDATA[data-api]]></category>
            <category><![CDATA[payments-api]]></category>
            <category><![CDATA[fintech]]></category>
            <category><![CDATA[sandbox]]></category>
            <dc:creator><![CDATA[Mirta Rotondo]]></dc:creator>
            <pubDate>Thu, 23 May 2019 09:01:00 GMT</pubDate>
            <atom:updated>2019-08-06T09:49:45.979Z</atom:updated>
            <content:encoded><![CDATA[<h4>Fancy trying the power of instant payment initiation directly from your user’s bank account? Try Open Banking APIs in test mode with no constraints today!</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*2DcMKSnt2X1rc5S6.png" /></figure><p>We are highly committed to providing secure services to our clients. Because of this, we constantly do our best to improve the security measures, design, and architecture of our product offerings.</p><p>With the release of our isolated Sandbox environment, we aim to improve <strong>security</strong>, enable <strong>testing</strong> for our <a href="https://truelayer.com/payments-api/">Payments API</a> product, and ultimately, enhance the <strong>developer experience</strong>.</p><p>The segregation of environments between the Sandbox Console and the Live Console, will permit you to:</p><ul><li>Test our Payments API product without moving real money;</li><li>Test our Payments API autonomously — no humans in the way;</li><li>Have separate applications for testing and live usage.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3TI2AdDaxsh8ZNIBPhxgkw.jpeg" /></figure><h3>Live vs Sandbox: what are the differences?</h3><p>In each environment, you will be able to generate a unique <strong><em>client_id,</em></strong> corresponding unique <strong><em>client_secret</em></strong> and an <strong><em>access_token</em></strong>. In this way, your applications are independent, and not related one to the other in any way. Due to the separation of <strong><em>client_ids</em></strong> — for instance — your applications and how they are customised, are completely independent of one another.</p><p>The <strong><em>authorisation link</em></strong> and <strong><em>API endpoints</em> </strong>will be identical, but instead of ending with the domain <a href="http://truelayer.com/">truelayer.com</a>, they will end with the domain <a href="http://truelayer-sandbox.com/">truelayer-sandbox.com</a>.</p><p>To differentiate it from production accounts, your sandbox account <strong><em>client_id </em></strong>will always have the prefix <strong><em>sandbox-</em></strong>. It will not be possible to add this prefix to a production account <strong><em>client_id</em></strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*YfWBLcjnGW0T79bj.gif" /></figure><h3>First sign-up</h3><p>Ready to try it out? You can signup to the Sandbox via <a href="https://console.truelayer-sandbox.com/">https://console.truelayer-sandbox.com</a>. If you already have a TrueLayer account in our Live Console, you can log in using the <strong>same credentials</strong>.</p><p>When you are signing up for the first time in the Sandbox environment you will be guided through our wizard to create your <strong><em>client_id</em></strong> and download your <strong><em>client_secret</em></strong>.</p><p>Once your application is created in both the Sandbox and Live environments you can easily <strong>switch from one to the other</strong> with the same login.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*N2SDIegODY_Qu-Qa.gif" /></figure><p>TrueLayer’s Sandbox V1 is currently available for the Payments API product. If you are interested in testing our <a href="https://truelayer.com/data-api/">Data API</a> product instead, you can signup to test with our mock bank or with real banks by setting up a FREE account in the <a href="https://console.truelayer.com/">Live Environment</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3TI2AdDaxsh8ZNIBPhxgkw.jpeg" /></figure><h3>The Payments Sandbox</h3><h4><strong>Features</strong></h4><ol><li>The TrueLayer Sandbox is integrated into an actual bank sandbox. This enables an end-to-end test including a sandbox payment consent journey while testing the Payments API;</li><li>All data is completely segregated from the live environment:</li></ol><ul><li>Sandbox client credentials cannot be used to create a production access token;</li><li>Sandbox access tokens cannot be used to call production API endpoints;</li><li>Resources created in the sandbox cannot be accessed via production APIs, e.g. if a payment is created in the sandbox, an attempt to GET the payment resource in the production environment will return a 404 response (and vice versa).</li></ul><p>Please note that the Payments Sandbox does not include a full bank simulation with consistent bank accounts, it is only intended to facilitate API testing.</p><p>To get started with integrating the Payments API, follow our <a href="https://docs.truelayer.com/#payments-api-quick-start">Payments API Quick Start Guides</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3TI2AdDaxsh8ZNIBPhxgkw.jpeg" /></figure><h3>In the next release:</h3><ul><li>Data API Sandbox environment;</li><li>Single entry point for both sandbox and live from <a href="https://console.truelayer.com/">console.truelayer.com</a>;</li><li>Single wizard — only in Sandbox environment;</li><li>Same client-id for both environments (the sandbox will always have the prefix sandbox-).</li></ul><p>Questions? Suggestions?</p><p>Please <a href="https://truelayer.zendesk.com/hc/en-us">reach out</a>! We are happy to talk!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=82a56ee8214d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Open Banking 2018: Building trust in end users]]></title>
            <link>https://medium.com/@mirtarotondo/open-banking-2018-building-trust-in-end-users-2d0cd541224b?source=rss-85ddf429d16a------2</link>
            <guid isPermaLink="false">https://medium.com/p/2d0cd541224b</guid>
            <category><![CDATA[cma9]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[open-banking]]></category>
            <category><![CDATA[trust]]></category>
            <category><![CDATA[banking-design]]></category>
            <dc:creator><![CDATA[Mirta Rotondo]]></dc:creator>
            <pubDate>Mon, 03 Dec 2018 18:37:34 GMT</pubDate>
            <atom:updated>2018-12-03T18:37:34.772Z</atom:updated>
            <content:encoded><![CDATA[<h4>We analysed the authentication flows of Open Banking and Challenger Banks to identify negative friction. Here’s some constructive feedback addressed at CMA9s to design better products and promote Open Banking adoption.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*ZboMGcHEbargltEu.jpg" /></figure><blockquote><strong>TL;DR</strong></blockquote><blockquote><strong>Building End User Trust: </strong>Compliance is not enough. UX and tone of voice are the key differentiators to increase Open Banking adoption.</blockquote><blockquote><strong>CMA9’s UX: </strong>Some banks need to redesign their flows and use better 2FA to stay competitive;</blockquote><blockquote><strong>Challenger’s UX: </strong>Challenger Banks are leading the market with frictionless authentication flows;</blockquote><blockquote><strong>Data Analysis: </strong>A qualitative comparison between the user journeys shows how each bank is performing;</blockquote><blockquote><strong>Information</strong>: Educational campaigns addressed to end-users are needed to demystify wrong perceptions about data usage and empower new financial services.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3TI2AdDaxsh8ZNIBPhxgkw.jpeg" /></figure><h3>Creating Trust for End Users</h3><p>PSD2 precipitated the urgency of developing a unified ecosystem for all the EU financial products.</p><p><a href="https://www.openbanking.org.uk/customers/what-is-open-banking/">Open Banking</a> — the new UK initiative implemented by the CMA9 banks aimed at empowering consumers and businesses over their banking data — is a great start to deliver some of the benefits of PSD2. <strong>But the regulation itself is not enough to win end users’ trust.</strong></p><p>It’s as simple as this:</p><ul><li>If users can easily use your service, they will be loyal to your offering.</li><li>If they cannot, they will start looking for other options.</li></ul><p>That said, it’s important for all the players involved (high street banks, challenger banks, fintech platforms, and financial applications) to understand that user experience and transparency are the key differentiators that will gain consumer loyalty.</p><p>The Open Banking Implementation Entity (OBIE) took this challenge seriously. In December 2017 they started producing a series of guidelines for participants in the Open Banking ecosystem. Specifically, their “<a href="https://www.openbanking.org.uk/wp-content/uploads/Customer-Experience-Guidelines-V1-01.pdf">Customer Experience Guidelines</a>” provides insights and recommendations based on extensive user research to help both banks and applications delivering a “<em>consistent and ubiquitous experience which will be familiar and trusted by customers</em>”.</p><p>CMA9s, Challengers, infrastructure platforms, and applications approached UX in very different ways in order to win end users’ trust, to encourage them to connect their bank accounts.</p><p>For our UX team at TrueLayer, 2018 was a great opportunity to learn about different business use cases in the industry, their user journeys, and end user behaviour.</p><p>Here is what we learned.</p><h3>One Goal, Different Journeys</h3><p>Accessing users’ identity information, balance, and transactions in real-time allows companies to build account aggregation functionalities, perform fast and accurate bank account verification, and helps them make better credit decisions.</p><p>Consequently, market players — lenders, marketplaces, credit bureaus, personal financial management applications, accounting firms, but also payment processors, insurance, rental and retail companies — understood the importance of redesigning their products to provide a better, seamless, and more reliable service to their users.</p><p>Today, almost all the high streets banks — AIB, Bank of Ireland, Barclays, Lloyds, Nationwide, Danske, Royal Bank of Scotland, and Santander — published their APIs in the Open Banking directory. Each of them created a unique user interface that tried to be consistent with their own brand and their own visual language. But while some of them were able to release fairly usable journeys, for others, <strong>there’s still a long way to go to keep their users loyal</strong> <strong>and survive the competition of other CMA9s</strong>.</p><p>Additionally, challenger retail banks such as Monzo, Starling, and Revolut are trying to disrupt the complexities of traditional banking. A relevant part of their business strategy is to provide simplified user experiences, and most of them, you’ll find, use a reassuring <a href="https://monzo.com/tone-of-voice/">tone of voice</a> and transparency. And, given their fast and increasingly large portfolio of users, we’d say it’s definitely working.</p><p>Let’s take a look at both CMA9s and Challengers’ authentication flows.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3TI2AdDaxsh8ZNIBPhxgkw.jpeg" /></figure><h3>CMA9s’ Flows</h3><p>Lloyds, Natwest, HSBC and Barclays.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FIBg0tOwSDTA%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DIBg0tOwSDTA&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FIBg0tOwSDTA%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="640" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/ae23edeab96d549acd0401d95f09a8ce/href">https://medium.com/media/ae23edeab96d549acd0401d95f09a8ce/href</a></iframe><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FLwVkmxwXNEw%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DLwVkmxwXNEw&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FLwVkmxwXNEw%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="640" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/f1ce1488b816d327d2309efa2f874bcb/href">https://medium.com/media/f1ce1488b816d327d2309efa2f874bcb/href</a></iframe><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FmibOG0vhEHI%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DmibOG0vhEHI&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FmibOG0vhEHI%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="640" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/c5c3b02cfee8a01d4448de339ffa7d2c/href">https://medium.com/media/c5c3b02cfee8a01d4448de339ffa7d2c/href</a></iframe><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2Fo-3G4-RugW0%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3Do-3G4-RugW0&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2Fo-3G4-RugW0%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="640" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/00703b2530b2dc2f80d486fc64cfa191/href">https://medium.com/media/00703b2530b2dc2f80d486fc64cfa191/href</a></iframe><p>The visual hierarchy and the scalability of information of some of the flows make the end-user journey more complex and convoluted than necessary. Some interfaces look cluttered and extremely verbose. Consequently, the end-user journey becomes tedious and un-engaging.</p><p>We think that to leverage the attention-information gap and succeed in the so-called “<a href="http://www.eyequant.com/blog/why-scalable-ux-is-the-next-revolution">Distraction Economy</a>”, the rule of thumb is to understand that what end users want is <strong>focus and clarity</strong>. Especially when dealing with sensitive data.</p><h3>Challenger Banks’ Flows</h3><p>Starling and Monzo.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2F9cqu0TP6vsk%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3D9cqu0TP6vsk&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2F9cqu0TP6vsk%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="640" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/d348e37c12c27d4811c6764b92bdf0da/href">https://medium.com/media/d348e37c12c27d4811c6764b92bdf0da/href</a></iframe><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2Fl0EAPOQqJoQ%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3Dl0EAPOQqJoQ&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2Fl0EAPOQqJoQ%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="640" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/d5c920414066db894e8d118f5d26e840/href">https://medium.com/media/d5c920414066db894e8d118f5d26e840/href</a></iframe><p>Challenger bank customers can forget about the verbose and cluttered interfaces, and leave the “remember username and password” struggle behind. The connection between their challenger bank account and applications, is very likely just a QR code or a magic link away. <strong>Hopefully CMA9s will take these simple and delightful flows into consideration when revising their current solutions.</strong></p><p>If you want to play with the Open Banking, Challenger Banks, and Credentials Sharing flows yourself, you can do it now by using our Data API demo application: <a href="https://demo.truelayer.com/">Piggy Bank</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3TI2AdDaxsh8ZNIBPhxgkw.jpeg" /></figure><h3>“Worst User Journey 2018” Awards</h3><p>There’s not enough quantitative data available yet to analyse Open Banking conversions and current usage. Still, we are constantly monitoring its uptake and collecting data based on what’s available through our customers, their users, and across the industry.</p><p>At TrueLayer, we identify negative friction that causes the end user to not complete some authentication journeys. To better understand their behaviours, we decided to analyse some UI features of certain CMA9 and Challenger banks’ flows:</p><ul><li><strong>Avg completion time</strong> — How many minutes are needed to complete the journey?</li><li><strong># steps</strong> — How many steps are needed to complete the journey?</li><li><strong># inputs </strong>— How many input fields need to be filled by the user?</li><li><strong>Avg # words</strong> — How many words are contained in each step of the process?</li><li><strong>2FA enabled </strong>— Is two-factor authentication needed to authorise access?</li><li><strong>Page length </strong>— Are actionable items going below the fold?</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*HGYup30KablHlrkS.jpg" /></figure><p>According to the data collected, HSBC, Barclays, and Lloyds’ UIs are the most cluttered because of the number of words used. Lloyds, NatWest, and Barclays, are the slowest. Lloyds, NatWest and HSBC are the most complex in terms of usability.</p><p>Needless to say, challenger banks just nail it. They also demonstrate how 2FA can be used without creating additional friction.</p><p>Ideally, the number of steps should be as few as possible in order to reduce the average time of the whole journey, and prevent the end user from leaving the flow prematurely.</p><p>In terms of readability, our suggestion for some banks is to re-approach copywriting and visual hierarchy. It is well known that complex and verbose sentences are harder to read than simpler ones.</p><p>Banks that have two-factor authentication steps have more friction than the ones not using it. 2FA, though, will be enforced for all banks starting in September 2019 as part of <a href="https://www.europeanpaymentscouncil.eu/news-insights/news/european-commissions-final-rts-are-official-journal">PSD2 RTS</a>. Consequently, banks should think about integrating better 2FA methods such as <strong>the ones used by challenger banks </strong>— QR codes and magic links — but also biometric, fingerprint or face scans. This concept is also advocated in the latest version of OBIE customer experience guidelines. Approaching decoupled redirect and deep-linking in the right way, can definitely reduce friction and help increasing adoption.</p><p>Last, but not least: page scrolling. It is true that people scroll vertically more than they used to, but new eye-tracking data shows that 80% of users’ viewing time is spent above the fold. (<a href="https://www.nngroup.com/">Nielsen Norman Group</a>) Some of the banks’ Open Banking pages are incredibly long and show input fields at the end of the page, rather than at the beginning. End users’ laziness and inattentiveness should lead to very specific UI decisions, such as designing the content to be fully contained above the fold or — at least — showing input fields on top.</p><h3>What End Users Want</h3><p>With the Open Banking flows being released just 10 months ago, more time is needed to see relevant adoption in order to analyse hard data, and monitor how end users’ interaction changes over time.</p><p><strong>Demographic targeting</strong> into user testing sessions may be helpful in the process of establishing more about differences in users’ behaviours. Demographic variables such as age, income, and education — specifically for financial products — can be predictable indicators of the user interaction with the interface.</p><p>According to our data, for example, end user behaviours are different depending on our client use case.</p><p>On the other hand, the great majority of usability experts agree that UX metrics are more accurate when measuring the <strong>prior experience</strong> or knowledge about an industry a user has, rather than looking into demographic details.</p><p>We’ve assumed that Open Banking flows may be perceived as more credible by end users because of their shared traits with their own bank’s UI. Still, <strong>credibility is not enough to ensure that end users find value in what has been provided to them</strong>. The complexity of the information, along with the slow, demanding experience, causes frustration which leads to failure in completing the authorisation process.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Rn3SqOKdONlqRM40.jpg" /></figure><p>According to Peter<a href="http://semanticstudios.com/user_experience_design/"> Morville</a> — author of “Architecture for the World Wide Web” and acclaimed IA and UX keynote speaker — a balance of usability, desirability, accessibility, credibility, usefulness, and availability are mandatory in order to create a meaningful and valuable user experience. The content should be original and fulfil a need. It should also be easy to use and accessible for people with disabilities. It should evoke emotions and appreciation. Finally, it should be able to create trust and lead the user to believe what the interface is telling them.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3TI2AdDaxsh8ZNIBPhxgkw.jpeg" /></figure><h3>Educating End Users</h3><p>High-street banks encouraged users via misleading ‘educational’ campaigns not to use their bank credentials in third party applications, except for their official bank website and app. Despite the understandable security reasons, this created <strong>skepticism and misconceptions</strong> about banking data usage.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Ix9y4XTALc2aW-Et.jpg" /></figure><p>Now with GDPR insuring data protection and privacy for all individuals within the European Union, <strong>end users are informed about the security aspects of sharing their data</strong>, and can be assured of the resultant benefits they will derive from giving explicit consent and access of their data to applications.</p><p>In early 2018 when PSD2 came into force, the UK regulator, the Financial Conduct Authority (“FCA”) asked banks to update their Terms and Conditions (“T&amp;Cs”):</p><blockquote><em>&lt;&lt;Your banking terms and conditions should not prevent you from sharing your credentials with regulated AIS or PIS providers. Your bank cannot hold you responsible for unauthorised transactions just because you have shared your credentials with regulated AIS and PIS providers.&gt;&gt; (</em><a href="https://www.fca.org.uk/consumers/account-information-and-payment-initiation-services"><em>FCA</em></a><em>)</em></blockquote><h3>What’s Next?</h3><p>It is our belief that the <strong>OBIE’s Open Banking standards and PSD2 requirements provide substantial guidance</strong> to help both banks, platforms, and applications delivering great experiences. Yet, they are definitely not imputable for creating additional obstacles in the end user journey.</p><p>We think that <strong>banks need to keep iterating on their authentication flows; they need to raise the UX bar, higher</strong>. We consistently attend workshops organised by the CMA9s to review their flows and provide feedback with one common goal: providing a smooth, frictionless experience for end users.</p><p>In parallel, applications need to continuously monitor their user behaviour, learn from the data collected, and thus, improve their interfaces and journeys.</p><p>At TrueLayer we firmly believe that clear, transparent and honest communication is needed to demystify wrong perceptions about data usage and empower new financial services. Educating end users is one of the most effective ways to <strong>make the future of banking data more reliable, accessible, and useful.</strong></p><p>Whether you are a high street bank, challenger bank, or application — we can collaborate to make this happen.</p><p>Let’s <strong>grow the Open Banking economy</strong>.</p><p>Together! 💪</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2d0cd541224b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Introducing Auth Dialog V2]]></title>
            <link>https://medium.com/@mirtarotondo/introducing-auth-dialog-v2-ea7818016597?source=rss-85ddf429d16a------2</link>
            <guid isPermaLink="false">https://medium.com/p/ea7818016597</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[open-banking]]></category>
            <category><![CDATA[fintech]]></category>
            <category><![CDATA[banking-technology]]></category>
            <category><![CDATA[ui-ux]]></category>
            <dc:creator><![CDATA[Mirta Rotondo]]></dc:creator>
            <pubDate>Wed, 01 Aug 2018 07:31:01 GMT</pubDate>
            <atom:updated>2018-11-10T15:49:33.045Z</atom:updated>
            <content:encoded><![CDATA[<h4><em>How the Design Team at TrueLayer designed a brand-new authentication dialog that permits end-users to share their banking data more easily.</em></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*WRKqQCIUA-csteDw.png" /></figure><h3>Hello Auth Dialog V2!</h3><p>After several months of intensive design, product, and engineering work, we are incredibly thrilled to launch our new, <strong>customisable</strong> authentication dialog.</p><blockquote><em>For those not familiar with it, the “Auth Dialog” is the </em><strong><em>end-user facing interface</em></strong><em> used by our </em><strong><em>Data API</em></strong><em> clients to ask for their consent. Its purpose is to guide our client’s end-users through the process of sharing their banking data with financial applications via both </em><strong><em>Open Banking</em></strong><em> and </em><strong><em>credential sharing</em></strong><em>.</em></blockquote><p>Since our very first release of Auth Dialog V1, almost a year ago, a lot has changed in financial technology; Open Banking, PSD2, and the FCA released their official guidelines; financial applications started to integrate bank APIs to build their products; end-users approached financial applications / challenger banks and got exposed to financial user interfaces (‘UIs’).</p><p>Consequently, we decided that our Auth Dialog V1 needed a deep re-design to offer our clients an experience that is:</p><ul><li><strong>better integrated</strong> into our clients user journey through customisation;</li><li><strong>more intuitive</strong> UX/UI to increase the flow<strong> </strong>completion rate<strong>;</strong></li><li><strong>compliant</strong> with FCA and PSD2.</li></ul><h3>How we did it: design thinking and client feedback</h3><p>To achieve a better product, we aimed at solving both <strong>known and ambiguous aspects</strong> of V1 through <strong>Design Thinking</strong>. This non-linear and practical method led us to intermediate solutions that then became the starting points of alternative paths. Those paths allowed us to redefine the initial issues, and solve multiple, unexpected problems.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*pNRWVQX2f-PDUuFO.jpg" /></figure><p>UX/UI research, several design brainstorming sessions, a lot of prototyping and user testing sessions kept us busy and led to the brand new version. Still, <strong>the most valuable information, </strong>was<strong> client feedback</strong>. Thanks to their suggestions, we’ve shaped an interface that aims to<strong> reduce friction </strong>and provides <strong>universal guidance</strong> for a broad, mixed audience of end-users.</p><p>Let’s explore the new interface and take a closer look at its features!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3TI2AdDaxsh8ZNIBPhxgkw.jpeg" /></figure><h3>Customisation: making the end-user journey better and better!</h3><p>And here comes the long awaited news: the new dialog is <strong>customisable</strong> for all of our clients!</p><p>In our previous version, the only dynamic parts were the client logo and application name. With Auth Dialog V2, instead, you will be able to personalise:</p><ul><li><strong>Colour Palette</strong> — Change the background, buttons, and drop-down colours to fit your UI;</li><li><strong>Help link </strong>— Redirect your users directly to your own FAQs page hosted on your domain;</li><li><strong>Data Usage Copywriting </strong>— Explain to your users what do you need their banking data for, using your brand and tone of voice;</li><li><strong>Skip Consent Page</strong>- If you are an authorised FCA company, you can skip our consent, and use your own consent page.</li></ul><blockquote><em>This </em><strong><em>customisation will offer a better experience to your users</em></strong><em> and will better integrate within your brand guidelines. Accordingly, the transition between your UI and our Dialog is going to be more subtle, and will give your end-users a smoother, friction-less journey.</em></blockquote><p>Want to take a look at some of our clients’ customised UI? Here’s what <a href="https://www.clearscore.com/">ClearScore</a>, <a href="https://www.zopa.com/">Zopa</a>, <a href="https://www.creditladder.co.uk/">CreditLadder</a> and <a href="https://www.bitbond.com/">Bitbond</a> did.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*mUp61VaVFd1hW2kr.gif" /></figure><h3>Plenty of new UX features:</h3><p>We’re not finished yet!</p><p>One of the most important parts of the whole journey, is when we ask the end-user to input their bank credentials. We worked hard to make this specific step friction-less by introducing:</p><ul><li><strong>Input labels:</strong> The labels are meticulously tailored to follow the ones of the banks;</li><li><strong>Live validations: </strong>A pre-check of the credentials is done by using regular expressions;</li><li><strong>Caps lock detection: </strong>Warn the end-user if caps-lock is activated. Useful for case sensitive details;</li><li><strong>Password field visibility:</strong> Turn password field visibility on/off. Great for the end-user to see what they are typing; prevent typographical and validation errors;</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/490/1*GJd8XB9UBycAIkbWmDmhJQ.gif" /></figure><ul><li><strong>Embedded Banks FAQs:</strong> Bank FAQs are at hand, so the end-user doesn’t need to leave the flow;</li><li><strong>Dynamic colours:</strong> A cool background colour animation smoothly transitions to the bank login page; bank specific colour palettes are used;</li><li><strong>Error handling:</strong> End-users will not get lost. We completely reviewed our errors copy writing and UX and provided actionable items for the user to retry and/or better understand what they are experiencing;</li><li><strong>Loader: </strong>The loader now shows the real amount of time needed to connect to the bank. We are also “hiding” a second automatic retry into that, in case the first connection doesn’t work.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/655/1*Co5fsCUsc5mBwSGMixv6dA.gif" /></figure><h3>Unfolding the new User Interface</h3><p>Following the end-user behaviour during the journey is one of the most important things the Design team at TrueLayer took into consideration while reviewing products’ UX. Monitoring end-user actions is a continuous effort that helps us understand what works, and what doesn’t.</p><p>Once we collected this data, we started questioning our design. First, we analysed friction points, then we began to take radical decisions to meet and keep up with the <strong>consumers’ demands &amp; expectations</strong>. It is by following this UX review process that we started redesigning our Auth Dialog UI and decided to release a V2.</p><p>When it comes to UI decisions, we strongly rely on standard design principles and logic such as:</p><p><strong>1) Task-focused approach</strong></p><p>We decided to divide the operations available to the users into two columns and present them in terms of the problem domain. The left column solve problems and create trust, and the right column guides the user to perform an action.</p><p><strong>2) Proximity and spatial distribution of elements</strong></p><p>We grouped similar information and organised the content in order to declutter the layout. By following recurring pattern and intuitive positioning for common elements such as navigation bar, back arrow, and “Allow” button, we aimed at simplifying the user’s effort to complete the task. The use of colours in strategic elements such as the help toolbar creates continuity with our client UI. In this way the resolution of a specific problem it’s mentally associated to our client’s brand.</p><p><strong>3) Visual Hierarchy</strong></p><p>We wanted each area to have one kind of control that represents one important action, without other controls getting in the way. We emphasised the “Allow” button and the client logo as the 2 most important elements on the interface. A “Z-Shaped” pattern starts from the client logo and finishes on “Allow”. The visual, unconscious result is, that the user is “Allowing the client” to perform an action.</p><p>Beyond UI, we also decided to change the dialog’s front-end and convert it into a single page application built in React, with the goal of providing a more fluid user experience.</p><h3>So … Welcome Auth Dialog V2!</h3><p>We are delighted with the outcome we achieved, and cannot wait to see the new Auth Dialog V2 with your logo and custom colours on it!</p><blockquote><em>If you wish to try the new experience you can see it in action in PiggyBank: our </em><a href="https://demo.truelayer.com/"><em>demo application</em></a><em>.</em></blockquote><blockquote><em>Or, if you can’t wait to see it branded with your company logo and colours, you can try it out directly in our self-serve </em><a href="https://console.truelayer.com/"><em>console</em></a><em>. If you have feedback or questions please reach out on </em><a href="https://truelayer.zendesk.com/hc/en-us"><em>ZenDesk</em></a><em>.</em></blockquote><p>We look forward to tracking any new UX data we receive, and to analyse end-user behaviour, so that we can iterate on our UX process, and continue to delivery a better, improved product to you.</p><p><strong>Cheers to a better banking experience!</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ea7818016597" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Brand, Branding, and Moroccan Tajines.]]></title>
            <link>https://medium.com/@mirtarotondo/brand-branding-and-moroccan-tajines-c3aa1fec38c7?source=rss-85ddf429d16a------2</link>
            <guid isPermaLink="false">https://medium.com/p/c3aa1fec38c7</guid>
            <category><![CDATA[branding]]></category>
            <category><![CDATA[brands]]></category>
            <category><![CDATA[company-retreats]]></category>
            <category><![CDATA[morocco]]></category>
            <category><![CDATA[fintech]]></category>
            <dc:creator><![CDATA[Mirta Rotondo]]></dc:creator>
            <pubDate>Tue, 14 Nov 2017 16:04:08 GMT</pubDate>
            <atom:updated>2017-11-14T16:06:40.229Z</atom:updated>
            <content:encoded><![CDATA[<h4>Building an identity along with our people.</h4><p>Clay-tinted landscapes extending as far as the eye can see. Echoing prayers of a nearby Mu’adhin. Mysterious <em>Tifinagh</em> glyphs and intriguing, sinuous Arabic scripts disclosing undecipherable information. The comforting warmth of the African sun hitting the skin. The cozy, mint scented vapour released from the silver teapot left on the table. Then, the peaceful and hearth-filling silence of the desert.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QSZVPnCz5nvLpPuwM6nsRg.jpeg" /><figcaption>P<a href="https://www.tripadvisor.co.uk/ShowUserReviews-g293734-d610173-r120041632-Bahia_Palace-Marrakech_Marrakech_Tensift_El_Haouz_Region.html">alais de la Bahia</a></figcaption></figure><p>Nothing is as good as <strong>getting lost</strong> in unfamiliar places to get a good dose of <strong>motivation </strong>and take a well-deserved mind-break. For creative people like me, a full immersion into unexplored hues, sounds, and scents combinations opens the way to the <strong>unexpected</strong>.</p><h3>Our first company retreat</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*plyrPlmmxYuA7tVEoQAhTA.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KbQXT_uVqJKFPszvyWM45Q.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*W4VxS8n5OTOP1r9a6f5EXg.jpeg" /><figcaption>Our amazing riad</figcaption></figure><p>As soon as we arrived in our charming, majestic <em>riad</em> in <strong>Marrakesh</strong>, the feeling of being far away from our tickling keyboards, scribbled whiteboards, and wet raincoats was an immediate relief. The average Londoner sweater-and-scarf look turned into espadrilles-and-harem-pants in no time. While we gathered around the swimming pool, everybody’s face looked relaxed already. We just landed in Morocco, and the whole team seemed more than ready to lay back and enjoy their very <strong>first TrueLayer retreat</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hZ1cqFbF674zXCVS4iKwog.jpeg" /></figure><p>Long walks, hikes, and city sightseeing. But also, peculiar activities such as finding out who the werewolves were, clubbing with monkeys and cave men, out-of-the-office conversations, plenty of couscous, and endless Tajines shaped the three-days journey into a mixture of feelings and experiences that created a <strong>sincere bond</strong> in our growing team.</p><blockquote>“Traveling — it leaves you speechless, then turns you into a storyteller.”<br><em>-Ibn Battuta- XIV Century, Moroccan geographer and explorer</em></blockquote><h3>Yallā Yallā! (hurry up)</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SHXI0wkwLDOZnFicGpTWvQ.jpeg" /><figcaption>Jamaa el Fna</figcaption></figure><p>Our visit inside the Medina was a <strong>full immersion</strong> into the colourful Moroccan culture. The crowded, noisy <em>Jamaa el Fna</em> (UNESCO Masterpiece of the Oral and Intangible Heritage of Humanity) was pure chaos.</p><p>Galloping donkeys and two-stroke engine mopeds hogging the labyrinthine alleys. Busy women concentrated in pan-frying buttery, square-shaped <em>Msemen</em>. Merchants’ hands popping out from a myriad of dusty bazars. Stoned snakes dancing at the sound of the charmers’ song. Finical turret-shaped compositions of pungent, exotic spices apparently not affected by gravity; eye-catching doors surrounded by playful geometric <em>Zellige</em> tiles; the soft scent of almonds of the freshly baked <em>Ghoribas</em>. People. People everywhere — going who knows where — rushing in a slow, rhythmic pace.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*f2s2oJzL8zvyRGhGacc5Yg.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OYxTKhiVt6XG57WPLswhGA.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*koEJj0ABZinIL8Svv61daQ.jpeg" /></figure><p>This <strong>intricate and complex</strong> “open-air performance” left each one of us with a different feeling, a different opinion, but — truly — it left us speechless. While we were intent in observing this incredible flamboyant world, some locals managed to lead us in “the belly of the beast”. In Marrakesh — apparently — whatever you ask for, whatever you look at, and whatever you take pictures of, well, you should expect to pay a price for it. And that’s when we realised that our desire to see the leather market resulted in an — unsolicited — escorted 40-minute twilight walk into the unexpected: urban decline, pigeons’ manure, and slime. All of this for a “reasonable” amount of dirham, of course.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5BFatqXflcOaLFLD8nlEFw.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*riUDKXlbAo_EiYAGXsgwpA.jpeg" /><figcaption>The Tanneries</figcaption></figure><p>The surreal and somewhat uncomfortable circumstance <strong>created an occasion</strong> to share thoughts, perceptions, and get closer one to each other.</p><blockquote>“When we establish human connections within the context of shared experience we create community wherever we go.”<br><em> -Gina Greenlee- Solo-world-traveler</em></blockquote><h3>TrueLayer. True story.</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*g5RIv8MO3elFdznOY26KFw.jpeg" /></figure><p>I’ve been designing brands for the past 10 years and — more or less — the branding strategies I followed, along with my fellow art directors worldwide, have always been the same. <strong>Brands were approached as destinations, rather than journeys.</strong> The <em>iter </em>was to start from the company name creation, its pay-off, and the design of a unique, remarkable logo. Next: corporate identity, marketing collateral, POP materials, and social-media branded content. Then all of this was ready to be used, and re-used, and re-used again. Right. But what were the results following this standard branding process? I think it created — for the vast majority of cases — anonymous, cold, and static brands dictated by the narcissism of the company founders, or by strained, user-centric strategies.</p><p>In 2017, this shouldn’t be the case anymore. Branding gurus of leading creative agencies around the globe agree on the fact that customers are “sick of the bullshit” (<a href="https://www.fastcodesign.com/3066981/the-radical-future-of-branding">Labarre</a>). They say that <strong>brands will have to offer a more truthful, transparent version of themselves</strong>. Also, with the rise of artificial intelligence, brands will have to inspect their moral and ethical responsibilities, with the ultimate goal of becoming more and more human.</p><p><strong>The era of static brands has come to an end.</strong> A company who wants to be respected and trusted by its consumers, needs to open its boundaries to different ideas and stimuli. We are talking about companies who are ready to include their people in every process. Companies who give voice to both their teams and customers, and are strongly committed to represent them.</p><blockquote>“Authentic brands don’t emerge from marketing cubicles or advertising agencies. They emanate from everything the company does.”<br><em>-Howard Schultz- Starbucks Founder</em></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MM2GgQNatk8aghGVdPwtoQ.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mTByKqBmysW8H3yNLy8Mvg.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3UW2OsBQ7KXZkOFcHUaKSQ.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*i_YIUClj25Wm21aLF665zw.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5JTBl10pHyfNzY9b_Oxnqw.jpeg" /></figure><p><strong>At TrueLayer</strong> we are trying to shape our brand around our team, rather than branding our team with a pre-established brand. We are not interested in selling a status. We recognise the importance of <strong>authentic storytelling</strong>. We want our enthusiasm and shared beliefs to be visible to everybody. We want our products to communicate our <strong>passion and commitment</strong>. We want to learn from our mistakes and inspire others. We want a brand that is fluid, versatile, and able to adapt to our vision.</p><p>This colourful Moroccan adventure helped us understand that everyone in our company — regardless of their experience, background, or specialisation — has something valuable to say. We believe that involving everybody in multiple functions is a necessary step to better understand what works and what doesn’t. Our diverse, enthusiastic, and hard working team is excited to learn. And, as Leonardo da Vinci once said “<em>Learning never exhausts the mind.</em>”</p><p>We are growing. And our brand is growing with us.</p><p>Bsslama!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c3aa1fec38c7" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>