Skip to main content

A frictionless check-out experience, what does that actually mean?


In today’s design of (software) solutions, providing a frictionless user experience is (and should be) a top priority within every organization.
While payments have already gone through a major evolution eliminating much of the frictions (from cash payments to card payments up to contactless card payments and mobile payments), the entire checkout process at a merchant is still a complex and not very user-friendly experience. And when I talk about the checkout process this includes not only the payment process, but also steps like scanning the products or asking the bill (e.g. in a restaurant), loyalty card scanning, coupon and discount management, handling guarantees (warranties) and delivering the cash ticket (and potentially VAT ticket or invoice generation).
Integrating all those steps into a single, fully frictionless experience should not be that complex, as all technology exists already today. Evolutions need to take into account however security, data privacy, the value of data (many merchants don’t want to expose the data of a customer’s consumption, as this data is considered a valuable internal asset) and legacy infrastructure with dozens of players involved (cash register providers, terminal providers, acquirers, card issuers, coupon wallet providers, PSPs…​).
The advantages of an evolution towards a frictionless checkout process are however numerous both for the merchant and for the consumer:
  • Reduces waiting time at the cashier and allows a faster checkout (saving customer’s valuable time) for both physical and online shopping (e.g. avoid having to enter your credit card data for each transaction or input online discount codes). The easier it is to pay, the more customers are going to spend (as there is less thought and consideration given to purchases).
  • Allows a more detailed analysis of customer’s spending (e.g. in bank PFM tools)
  • Reduces customer’s cognitive strain (no need to remember PIN code, no need to think about loyalty card or coupons, no need to safely store your warranty receipt…​), making the troublesome checkout process less visible and painful.
  • Reduces churn and shopping cart abandonment, especially for online shopping (according to SaleCycle, up to 75% of customers abandon their online shopping carts without making a purchase)
  • The Covid-19 crisis shows also the need for contactless end-to-end processes, i.e. from scanning products (e.g. with your own mobile), payments, coupons…​ Such a streamlined process not only reduces the workload for the personnel in supermarkets, but also ensures a fully contactless experience, which helps with the hygiene prescriptions.
When purely looking at the payment step at a physical store, mobile payments like Apple Pay or Google Pay, already provide a very frictionless and secure experience. Nonetheless these solutions still pose several issues:
  • Only possible on NFC enabled terminals
  • Very difficult and costly for card issuers to onboard their card on the Apple or Google platforms (often resulting in extra costs for merchant)
  • No solution for vouchers and other niche payment products
  • Difficult to select the card you want to use
  • For certain use cases (like paying for a single ticket in the metro) the authentication process is still too complex and time-consuming (resulting in queues).
  • Still considered as less secure (even when protected via biometric authentication), meaning their usage is usually limited to a specific threshold
Most of these issues are caused by the fact that these payment methods don’t disintermediate the value chain, but instead create an additional intermediary. Unfortunately, without a drastic change in the payment landscape (e.g. via crypto-currencies or Libra-like initiatives), it will be difficult to simplify the landscape.
It is therefore likely that an additional layer of abstraction should be introduced to resolve some of the above issues:
  • A first problem to be solved is selecting the right payment method. Today, people have dozens of choices for paying at a merchant, like paying via cash, merchant specific gift vouchers, legislative vouchers, debit cards and credit cards (contact or contactless), mobile payment (via Apple Pay, Google Pay or via QR code scanning like e.g. Payconiq-Banconctact), loyalty cards linked to bank accounts (e.g. Colruyt Xtra card)…​ And many webshops offer even more options, like also direct debits, payment via credit transfer (before or after delivery), PayPal, Bitcoin, iDEAL, Sofort, bank PAY buttons, Klarna…​
    A rule-based intermediary layer (like Curve) could do the selection of the best payment method automatically for the user (e.g. by consuming first pre-paid vouchers with expiration date and then taking a payment methods which give the best conditions for the customer).
  • A second problem is the onboarding of payment methods into platforms like Apple Pay and Google Pay. The above described intermediary layer (for selecting payment method) could also play a role here, as this layer could onboard a single virtual card on these platforms, abstracting away all other payment methods behind.
    Remains of course the onboarding of all payment methods in this intermediary layer, but via well-documented open standard APIs, the onboarding could be made freely available for any payment provider to onboard.
  • A third problem is to get all necessary information of the merchant (or more specifically its terminal) to apply the rules for payment method selection. While it will be difficult to change the entire payment infrastructure to pass all necessary information about the cash ticket, guarantees/warranties, loyalty card info…​ an easier solution could be that every merchant (or outsourced to a third-party) exposes an Open API, where based on the payment reference, all info can be recuperated in a secure way. This way the existing payment infrastructure does not need to be adapted and information can be automatically retrieved by the above intermediary layer.
  • Finally, we have the problem of the authentication. For small amounts, people want a very frictionless experience (maximum 2-3 seconds, but for small amounts this is often still considered too long), but for large amounts, people like a whole payment ceremony, as it gives them a sense of security and comfort.
    Risk-based authentication is here the solution, i.e. based on the amount, merchant and/or customer’s profile (e.g. has the user shopped before at the merchant, typical amounts the user is spending, typical products the user is buying, did the user buy something in the neighborhood earlier…​), the system can strengthen (requiring additional authentications) or loosen the authentication requirements. Via mobile payments, many authentication means are available (like fingerprint, voice and face recognition, PIN code, SMS code verification…​), making it more easy to implement this type of risk-based authentication.
    Good AI-based models are however required to ensure that authentication becomes not too severe, when shopping at a new merchant for the first time, as the first experience is usually the one that makes or breaks the chances of a continued relationship.
In the end a frictionless checkout process can be reduced to 2 distinct end-user steps, i.e. identifying the person doing the purchase and providing consent to exchange info and value.
Via the identification, the account number can be derived and security can be enforced, while the consent step gives the payment provider the authorization to retrieve the money, but also to store all associated information in your personal vault.
The target is a frictionless, even invisible, checkout process of which several real-life examples, already come close:
  • Amazon Go Store shop (Amazon’s Just Walk Out Technology), where the customer is automatically identified when entering the store (via facial recognition), where the products the customer takes are also automatically identified and where the entire checkout processes is automatically executed (as the customer’s identity is linked to a digital account, in which his payment details are stored)
  • Uber: one of most important reasons for Uber’s success is the frictionless payment process. Paying a taxi driver used to be a hassle, but via the Uber app this can be done fully frictionless.
  • Parking garages scanning automatically your license plate (upon entry and exit) and charging automatically to your linked payment account
  • Fuel stations, which identify your arrival automatically based on geo-location services. The user just selects the pomp number on his mobile and can start fueling.
  • Employers and some hotels and amusement parks using the access card/badge/band not only to gain access, but also to manage payments
  • Restaurants: pay in-app, eliminating the need to wait for a waiter or waitress to bring the check and execute a payment.
  • IoT device payments, like fridges ordering and paying itself. Similar are the voice-controlled devices like Google Home (Google Assistant) or Amazon Echo (Amazon Alexa), which can order and pay products automatically.
  • Chatbot payments and payment buttons in social media websites
  • Joyn in Belgium offers a digital loyalty card for small merchants and has integrated Payconiq and Monizze as payment methods, allowing to execute the collection of loyalty point and payment in 1 step on your mobile phone.
  • The Colruyt Xtra card in Belgium combines coupons/discounts, payment, ticketing (details of spending is available online) and loyalty points in 1 card transaction, which can even be done mobile via the Colruyt Xtra app.
  • Merchants setting up their own apps, allowing to place orders, pay for them, but still collect the order in a physical shop. This creates a strong relationship with the customer and removes costs of intermediaries, but requires the customer to install the app and onboard a payment method (and this for every merchant app). E.g. Starbucks Rewards app (Starbucks has over $1.2 billion in deposit on their pre-paid cards), Tesco Pay or Walmart Pay app.
  • Super-apps, which offer a lot of third-party services integrated in the app, for which payments can be done directly in the app. The advantage for the customer is that he only needs to install 1 app and onboard only once for executing payments. Example: bank apps like KBC or Belfius, Alipay, WeChat…​
In order to make the checkout process fully frictionless, we should however not only consider the end-to-end checkout process, but also all processes post-checkout, which are impacted by the way the checkout process is managed. Easy and complete (i.e. deliver all necessary data) integration with tools facilitating these processes is essential.
For customers, this consists of processes like:
  • Automatic handling of cash-backs
  • Retrieving all details of an acquisition, so that your PFM tool can properly allocate all expenses (allowing to manage and optimize budget plans)
  • Easy handling of refunds in case of issues
  • Storing ticket/guarantees/invoices/VAT ticket for future reference
  • Easily finding back guarantees in case of issues
  • Expense management for employees to get reimbursed by their employer
  • Split-bill or refund colleagues, friends, family…​
  • Tax declaration (personal declaration or submitting all info to accountant)
For merchants, this includes processes like:
  • Matching invoices and payments (and reconciliation) and identification and follow-up of missing payments
  • Collecting money from different payment providers (and reconciliation if 1 transaction is partially paid via different payment methods).
  • Global recovery of funds and forex handling
  • Cash management, e.g. cash pulling and sweeping
  • Direct Debit mandate management (onboarding, sending payment instructions and follow-up of failed direct debits)
  • Automatic loading of payments in accounting systems (with necessary details to do proper tax management, like VAT calculation and recuperation)
  • Automatic stock management based on executed payments
  • Automatic collection of money from manufacturers when processing coupons
  • Automatic handling of reversals and cash refunds
  • Automatic validation and pay-out of cash-backs
  • Liberating goods/services when payments are done
  • …​
Often this end-to-end value chain is not fully considered by a merchant choosing his payment infrastructure (like cash register, terminal, PSP, bank…​). E.g. many merchants opt for a collecting PSP, as this offers better rates, but forget that this leads to issues for customers afterwards (in PFM apps, for cash-backs, for understanding transactions) as payments are all happening with the PSP as counterpart.
When we really want to get a frictionless checkout experience, all players should consider every step in the process both for themselves, but also for other stakeholders in the process.
Check out all my blogs on https://bankloch.blogspot.com/

Comments

Popular posts from this blog

Transforming the insurance sector to an Open API Ecosystem

1. Introduction "Open" has recently become a new buzzword in the financial services industry, i.e.   open data, open APIs, Open Banking, Open Insurance …​, but what does this new buzzword really mean? "Open" refers to the capability of companies to expose their services to the outside world, so that   external partners or even competitors   can use these services to bring added value to their customers. This trend is made possible by the technological evolution of   open APIs (Application Programming Interfaces), which are the   digital ports making this communication possible. Together companies, interconnected through open APIs, form a true   API ecosystem , offering best-of-breed customer experience, by combining the digital services offered by multiple companies. In the   technology sector   this evolution has been ongoing for multiple years (think about the travelling sector, allowing you to book any hotel online). An excellent example of this

Are product silos in a bank inevitable?

Silo thinking   is often frowned upon in the industry. It is often a synonym for bureaucratic processes and politics and in almost every article describing the threats of new innovative Fintech players on the banking industry, the strong bank product silos are put forward as one of the main blockages why incumbent banks are not able to (quickly) react to the changing customer expectations. Customers want solutions to their problems   and do not want to be bothered about the internal organisation of their bank. Most banks are however organized by product domain (daily banking, investments and lending) and by customer segmentation (retail banking, private banking, SMEs and corporates). This division is reflected both at business and IT side and almost automatically leads to the creation of silos. It is however difficult to reorganize a bank without creating new silos or introducing other types of issues and inefficiencies. An organization is never ideal and needs to take a number of cons

RPA - The miracle solution for incumbent banks to bridge the automation gap with neo-banks?

Hypes and marketing buzz words are strongly present in the IT landscape. Often these are existing concepts, which have evolved technologically and are then renamed to a new term, as if it were a brand new technology or concept. If you want to understand and assess these new trends, it is important to   reduce the concepts to their essence and compare them with existing technologies , e.g. Integration (middleware) software   ensures that 2 separate applications or components can be integrated in an easy way. Of course, there is a huge evolution in the protocols, volumes of exchanged data, scalability, performance…​, but in essence the problem remains the same. Nonetheless, there have been multiple terms for integration software such as ETL, ESB, EAI, SOA, Service Mesh…​ Data storage software   ensures that data is stored in such a way that data is not lost and that there is some kind guaranteed consistency, maximum availability and scalability, easy retrieval and searching

IoT - Revolution or Evolution in the Financial Services Industry

1. The IoT hype We have all heard about the   "Internet of Things" (IoT)   as this revolutionary new technology, which will radically change our lives. But is it really such a revolution and will it really have an impact on the Financial Services Industry? To refresh our memory, the Internet of Things (IoT) refers to any   object , which is able to   collect data and communicate and share this information (like condition, geolocation…​)   over the internet . This communication will often occur between 2 objects (i.e. not involving any human), which is often referred to as Machine-to-Machine (M2M) communication. Well known examples are home thermostats, home security systems, fitness and health monitors, wearables…​ This all seems futuristic, but   smartphones, tablets and smartwatches   can also be considered as IoT devices. More importantly, beside these futuristic visions of IoT, the smartphone will most likely continue to be the center of the connected devi

PSD3: The Next Phase in Europe’s Payment Services Regulation

With the successful rollout of PSD2, the European Union (EU) continues to advance innovation in the payments domain through the anticipated introduction of the   Payment Services Directive 3 (PSD3) . On June 28, 2023, the European Commission published a draft proposal for PSD3 and the   Payment Services Regulation (PSR) . The finalized versions of this directive and associated regulation are expected to be available by late 2024, although some predictions suggest a more likely timeline of Q2 or Q3 2025. Given that member states are typically granted an 18-month transition period, PSD3 is expected to come into effect sometime in 2026. Notably, the Commission has introduced a regulation (PSR) alongside the PSD3 directive, ensuring more harmonization across member states as regulations are immediately effective and do not require national implementation, unlike directives. PSD3 shares the same objectives as PSD2, i.e.   increasing competition in the payments landscape and enhancing consum

Trade-offs Are Inevitable in Software Delivery - Remember the CAP Theorem

In the world of financial services, the integrity of data systems is fundamentally reliant on   non-functional requirements (NFRs)   such as reliability and security. Despite their importance, NFRs often receive secondary consideration during project scoping, typically being reduced to a generic checklist aimed more at compliance than at genuine functionality. Regrettably, these initial NFRs are seldom met after delivery, which does not usually prevent deployment to production due to the vague and unrealistic nature of the original specifications. This common scenario results in significant end-user frustration as the system does not perform as expected, often being less stable or slower than anticipated. This situation underscores the need for   better education on how to articulate and define NFRs , i.e. demanding only what is truly necessary and feasible within the given budget. Early and transparent discussions can lead to system architecture being tailored more closely to realisti

Low- and No-code platforms - Will IT developers soon be out of a job?

“ The future of coding is no coding at all ” - Chris Wanstrath (CEO at GitHub). Mid May I posted a blog on RPA (Robotic Process Automation -   https://bankloch.blogspot.com/2020/05/rpa-miracle-solution-for-incumbent.html ) on how this technology, promises the world to companies. A very similar story is found with low- and no-code platforms, which also promise that business people, with limited to no knowledge of IT, can create complex business applications. These   platforms originate , just as RPA tools,   from the growing demand for IT developments , while IT cannot keep up with the available capacity. As a result, an enormous gap between IT teams and business demands is created, which is often filled by shadow-IT departments, which extend the IT workforce and create business tools in Excel, Access, WordPress…​ Unfortunately these tools built in shadow-IT departments arrive very soon at their limits, as they don’t support the required non-functional requirements (like high availabili

An overview of 1-year blogging

Last week I published my   60th post   on my blog called   Bankloch   (a reference to "Banking" and my family name). The past year, I have published a blog on a weekly basis, providing my humble personal vision on the topics of Fintech, IT software delivery and mobility. This blogging has mainly been a   personal enrichment , as it forced me to dive deep into a number of different topics, not only in researching for content, but also in trying to identify trends, innovations and patterns into these topics. Furthermore it allowed me to have several very interesting conversations and discussions with passionate colleagues in the financial industry and to get more insights into the wonderful world of blogging and more general of digital marketing, exploring subjects and tools like: Search Engine Optimization (SEO) LinkedIn post optimization Google Search Console Google AdWorks Google Blogger Thinker360 Finextra …​ Clearly it is   not easy to get the necessary attention . With th

Deals as a competitive differentiator in the financial sector

In my blog " Customer acquisition cost: probably the most valuable metric for Fintechs " ( https://bankloch.blogspot.com/2020/06/customer-acquisition-cost-probably-most.html ) I described how a customer acquisition strategy can make or break a Fintech. In the traditional Retail sector, focused on selling different types of products for personal usage to end-customers,   customer acquisition  is just as important. No wonder that the advertisement sector is a multi-billion dollar industry. However in recent years due to the digitalization and consequently the rise of   Digital Marketing , customer acquisition has become much more focused on   delivering the right message via the right channel to the right person on the right time . Big tech players like Google and Facebook are specialized in this kind of targeted marketing, which is a key factor for their success and multi-billion valuations. Their exponential growth in marketing revenues seems however coming to a halt, as digi

AI in Financial Services - A buzzword that is here to stay!

In a few of my most recent blogs I tried to   demystify some of the buzzwords   (like blockchain, Low- and No-Code platforms, RPA…​), which are commonly used in the financial services industry. These buzzwords often entail interesting innovations, but contrary to their promise, they are not silver bullets solving any problem. Another such buzzword is   AI   (or also referred to as Machine Learning, Deep Learning, Enforced Learning…​ - the difference between those terms put aside). Again this term is also seriously hyped, creating unrealistic expectations, but contrary to many other buzzwords, this is something I truly believe will have a much larger impact on the financial services industry than many other buzzwords. This opinion is backed by a study of McKinsey and PWC indicating that 72% of company leaders consider that AI will be the most competitive advantage of the future and that this technology will be the most disruptive force in the decades to come. Deep Learning (= DL) is a s