Where is the action in retail payments?

 In the beginning there was gold  followed by cash. Then came the check. And then came technology where we are now.

The best analogy to understand  the action in retail payments is that of a kitchen table where the transaction occurs. The table has 4 legs and the table top. 

The four legs together with the table top  in our kitchen table example are the basic requirements of creating a transaction.

Customer:

The  first leg is a card holder who wants to purchase goods or services for which the payment card is used. Many flavors of cards exist- credit card, debit card, prepaid card and virtual cards. With the rise of smart phones a new breed of payment vehicles called digital wallets has emerged. Here you load funds from your bank account. Open Banking allows you to choose from the smart phone which bank you want to use to load funds.

The action is in offering the customer  multiple choices in making payments--cards, wallets, QR codes, Buy now pay later(BNPL), Request to pay(RTP), EMT or email money transfer, account to account to split a restaurant bill to name a few. 

Merchant:

This second leg is the entity that sells you the goods or services. This can take place in a physical store or online in a website or app. The payment is accepted in a Point of sale terminal or  in a secure area of their website called Payment Gateway where you enter the card details. In facilitating a payment, they accept any of the payment vehicles  the customer chooses to pay. Once received, they send the transaction over to the third leg called processor.

The action is in enabling Merchants accept the various payment vehicles. This is driven by the need to offer convenience and personalization to the customer which ultimately drives revenue.

Processor:

The third leg goes by various names --acquirer, payment processor, PSP, merchant aggregator. Sometimes a bank can offer the processing. With the rise in transaction types the action for the processors is making sure the transaction goes through and also to route the transaction at the least cost  for themselves and the Merchant. 

Issuer:

The fourth and final leg of our kitchen table analogy  is a bank or fintech who has issued the card or payment vehicle to the customer. These entities are responsible for funding the transaction by taking money from the customer bank account  and sending it on to the Merchant's bank account. 

The action here is that the Issuer has to provide these new payment vehicles to the customer . The success lies in how well they market the vehicle leading to more acceptance in the market.

Networks:

Finally the table top or the network that connects all the parties . They are the trusted brands we know so well like Visa, Mastercard, Amex. New payment networks based on current technologies are disrupting the legacy Networks business models. This is where the action lies.

 These new  networks are domestic networks in nature ,usually driven by the government and are provided to increase the availability of new payment vehicles . The goal of these governments is to enable transition from cash and financial inclusion. Absent legacy costs, these networks offer speed , convenience and lower costs to all the legs of the kitchen table top in the payment ecosystem. Examples of these networks are Interac in Canada, UPI in India, M-pesa in Kenya, SEPA in EU.

The legacy networks are not resting . They are also building these new networks in addition to their legacy infrastructure.

Some of the technology building blocks that enable this action in the retail payments area include ISO20022 payment messaging, tokenization, digital identity. They all take advantage of rich data now available about customer behavior to reduce operational risk elements like failing transactions in straight through processing, fraud mitigation, cloud infrastructure to cut costs and digital trends to attract new customers.

All in all a great time to be in this space.

Read More

Embedded Finance and Payments

 We have seen a lot of exciting developments in the consumer space introducing payments as a way to enhance revenue and customer interaction. Starting with major tech players like Apple and Google offering wallets for paying merchants, Square added debit cards to its Cash App P2P platform, Uber used the Visa  rails to provide instant payments to its drivers to Shopify adding Stripe's payment processing capability for its merchants.

These initiatives have led to revenue gains for all parties but more importantly taken away customers which would have belonged to banks. JP Morgan's CEO was moved to announce that some of these fintechs are a threat to their business. Couple with the valuations these tech companies are getting in the tens of billion in many cases , you can understand the impact embedded finance is having on the traditional banking industry.

How are these results possible? Its possible by embedding the payment APIs into the company's business process such that the consumer can take advantage of the rich UXs the fintech offers and it gives benefits in terms of data about the customer behavior. 

With ISO20022 payment message standard gain traction, the benefit of embedding payment flows and interactions with the data generated will be an opportunity for serving the B2B sector as well with products such as virtual card for vendor payments.

Read More

The business of banking and payments

 What does a bank do? From the perspective of a consumer of business here are the core functions:

-Offers consumers banking services around their day to day needs of payroll, paying bills, cash requirements, mortgages, deposits and managing wealth.

-Offers businesses a way to receive money from customers and pay their suppliers, loans to fund their business, handle domestic and international  payments 

Between themselves, they offer loan syndication, securitization, investments , stocks and bonds.

A common theme is the use of information technology to support their transactions and service their constituents with information about their money.

Since thousands of years this has been the function of banks. A trusted repository of your money and a facilitators of transactions for business benefit from financing wars to paying for your coffee. 

What has changed in the last two decades? The rise of internet as a set of technologies to enable banking. The unintended consequence is that Internet has enabled banks to take advantage of scale and hide bad behavior such as creating complex derivate trades without responsibility  for the underlying asset. 

But what about payments? The Internet has been of net benefit to the payments segment by enabling tracking of the legal beneficiaries and cost transparency for the end user of banking services. Trends like modernization of payment rails, APIs, Open Banking, ISO20022 messaging are facilitating deep integration across the payments value chain. This is a clean , fee based business with few places to hide for bad actors.

Read More

Why should banks care about ISO20022?

 Consider some of this data:

-Total transition costs for migration to ISO 20022 payment message standard cost the SEPA $9 billion as per a 2017 study.

-Payments Canada expects a migration from checks will save the Canadian economy $4.5 billion.

This is good for the economy and society as a whole but I am a bank running for profit so why should I care? I have a system that works fine, the inefficiencies and delays in my current system is to my benefit as I can enjoy the float and charge more plus its been working fine for decades.

Well too bad, bank. Customers and regulators are insisting on this change and if you don't change you risk rising operational costs. falling behind the curve leading to loss of customers and regulatory burdens.

Lets peel this onion, shall we?

Rising operational costs: Drop in STP rates means less and less of your transactions will be completed without manual intervention. As it is, only about 60-80 % of your transactions go through STP and this is already  impacting the cost vectors of your payment business. ISO20022 rich data messaging allows you to do better reconciliation leading to improved STP rates.

Regulatory burdens: Sanctions screening, AML, KYC, purpose of making the transaction, legal entity, ultimate beneficiary  all these are checks you are doing today. With tools like LEI in ISO20022 this information travels with the message reducing your regulatory obligations.

Loss of customer: If I am a customer expecting a wire transfer and its going to take a week to get the money in my bank account and cost me $40 for this  , I will certainly look for options to get the funds faster and for lesser cost. No brainer here.

So the cost of not moving to ISO20022 is not the factor .Rather, it is the when and what deadlines I am facing that drive this decision. See this chart and note that many market players in North America are yet to go live but be assured all regulators are working in this directions.

Read More

Data Security in ISO 20222 with Tokenization

 With increasing use of account level credentials being used for facilitating payments it comes with risk of ensuring safety of the remittance information. Compounded by various real time rails and the rise of immediate payments the new payment methods such as wallets, ecommerce, QR code and  other payment methods have increased the chance of fraud . Given lack of delay in the real time rails and that payments are irrevocable, fraud mitigation is taken on a higher priority.

Tokens , which can be thought of as surrogates for the PAN or primary account number have increasingly been thought of  as viable solution to address the risk of not securing rich remittance data. They use the same format numbers as the original transaction so the processing protocols can do their job while the customer experience is not impacted.

The processor receives a transaction from the customer's bank , maps a token value to the transaction and sends it to the issuing  bank for clearance. Alternatively the issuing bank and send both the token and the transaction to the processor who then sends the account information to the acquiring bank for fulfillment.

Read More

Customer minutes and friction as a metric for Banks

 Everywhere we see especially in ecommerce what used to be complicated method of paying for goods and if required getting refunds used to be fraught process. Nowadays Amazon has shown the way with One click ordering and refunds.

This consumer focus to help make their lives easier while interacting with a machine has been rewarded both by customers and the stock markets . What are some examples where banks have made the difference?

- Transaction alerts on the mobile app 

-Customer authentication on the phone if calling from a registered number

-Servicing via chat if customer is on the online banking portal.

These use cases showcase how to reduce friction by reducing "Customer minutes" i.e. time spent by customers to address their issues. Think of how the internal business processes have been rejigged to permit these outcomes.

ISO20022 rich payment messaging data is a building block for enabling these types of friction reductions in business and the real benefit is in terms of better cash flow and the opportunity to innovate on top of the payment message data set.

Read More

Business in the instant payment world

 Many jurisdictions are working on implementing a low value system on real time rails. Built on ISO20022 payment messaging standards, these promise the availability of instant and irrevocable settlement as well as rich data about the transaction such as invoice details.

Some well established business use cases that will benefit from these new capabilities  where payments are available 24x7  as opposed to time delay for ACH and checks are:

-Ecommerce vendors buying and selling online

-Gig economy payroll for workers for payment of hourly wages

-Emergency relief payments that we have become familiar during this pandemic

The benefit to the receiver are obvious-- money in hand instantly. But the business are also needs to step up in managing this sea change such as :

-How will information on the remittance be stored and reconciled

-If you are receiving funds after hours how will this be managed in an automated manner in your AR.

-What approvals will be in place to release the payment noting these are irrevocable and instant.

Think of the improvement in cash flow with these new tools. Also the reduction in time spent reconciling payments. Paying by installment may lead to new and more revenue.

Read More

CSM Opportunity for Banks

 Given the huge innovation in payment initiation  for consumers its only a matter of time that businesses would ask banks what options are available for them to participate in the instant payment world.

Its not going to be easy for banks. They will have to take calls that may or may not pan out. One area they can start thinking about is the Clearing and Settlement function. There is a history of lag and costs in this area. However there is sporadic innovation as well. Ripple's cross border RippleNet system has shown the potential for reducing costs in Cross Border clearing and settlement.  Swift GPI is showing a method to introduce transparency and tracking in cross border payment flows.

But these are technology based offerings. Regulators in many countries are encouraging development of new instant payment rails such as IMPS in India . China, Japan, Australia, Canada, USA and lastly EU have plans to set up these rails and are various points in their rollout.

By taking calls on which  technology to utilize and what networks to participate in , banks can offer differentiated clearing and settlement-- based on  countries they want to focus on, speed of settlement, transparency of payment journey, SLA based straight through processing STP to name a few.

However the table stakes in all these offerings will be an end to end ISO20022 message compliant network

Read More

What is LEI?

 LEI stands for Legal Entity Identifier . This is a 20 character alpha numeric code based on ISO 17442 standard. This code helps in identifying the legal entities in a payment transaction. 

For example in Canada all counterparties to the derivatives transactions need to have an LEI. As faster payments and pay mod initiatives kick  in, more market participants including legal companies, their subsidiaries, government departments, charities will be expected to have this code.

The LEI Common Data File Format v.2.1 is expected to record previous legal names, "operating under", "brand name", "trading as". This clarity is expected to reduce operating cost and false positives.

In future once LEIs are incorporated into the business processes substantial cost savings accrue  in verifying entity during loan origination, KYC refresh, credit worthiness monitoring , compliance reporting etc.

Banks can consider using LEI as a business case to step up the ISO20022 modernization effort.

Read More

The Age of Open Banking

 Let us pivot for a moment from the back office of ISO20022 payment messages to the front office where the customer meets the bank.  Imagine your legacy bank has worked hard to modernize its payment systems and now carries rich data about a transaction end to end.

What challenges do banks face? Several in fact. 

Sharing Customer Data: Who do I share this data with?  What is the risk to the bank, the customer? How is my API strategy shaping up?  Regulations are spotty at best and cant be depended to course correct us.

Partner: As a bank, I don't know the use cases of the rich data I am bringing, so let me partner with a third party. While I do benefit with customer acquisition is it damaging  my brand? Do I promote my APIs to anybody or restrict it and if so what do I restrict ? Case in point--TD Bank sued Plaid recently. 

Plus and minus points to consider such as how will the data be used by the third party and what risks arise to me as a custodian of this data. Key benefits of my product are a convenient way to compare accounts, some financial services and loans. Will price comparison benefit me or not? Upside is my sales channels and distribution increase. What are the downsides?

Distributor: In addition to my own products as a bank I can resell third party products like mortgage calculators, education and tools around budgeting for example. This leads to better customer journey. But what if the third party leaves and goes to another bank? Case in point--Mogo bank account origination was with one bank and they flipped to another--in this case Mogo is reselling the partner banks' balance sheet leading to some basis points yield but customer information is with Mogo so who has more value?

No easy answers here. Lot depends on the assessment of your capability as a bank to go to the market, what are your strategic goals near term and whether a Partner or Distributor model has buy in of the executives.

 

Read More

Cost and Value in Payments

 Today cross border payments have a reputation for high cost and lack of transparency in the fee structure.

Coupled with a 600 year old system of Vostro/Nostro accounts and Correspondent banks as middlemen the system is opaque as best and takes 5-7 days for settlement to conclude.

Where are these costs coming from? This graphic from Payments Canada will help.

Can fintechs help reduce costs? See this graphic from RBC in one of their pilot studies with Ripple 

Dramatic reduction in costs and speed yes. But real life is not a tech project. SWIFT with its network of 10000 banks, each node in the network has painstakingly negotiated contracts and SLAs , regulations in each jurisdiction have to be understood and compliance has to be managed.

The solution is ISO20022. The vision is end to end payment messaging with rich data to overcome barriers in speed, compliance and processing costs.

Read More

Value of digital transformation

 

Customer onboarding at Visa

Customer onboarding at Plaid

Visa paid $5.3 billion for Plaid. What does this tell us about the potential for digital transformation and embedded finance with ISO20022?

Read More

How to use data from ISO20022?

 

 

The attraction of ISO20022 messaging data is:

-It is unambiguous: the meaning of each data element is known

-It is credible: the origin point of the data is known.

-It is consistent: all ISO messages follow a standard that is universally understood.

 

These factors lend itself to data analytics at scale. Many banks have data lakes and initiatives to use AI/ML to develop insights. The building blocks are in place.

What is payments data?

Data generated by providing payment services such as card payments, mobile payments, debit and credit transfers, ATM transactions etc. The type of information about the persons doing the transactions collected are PII data, sort and account codes, payment date and time as examples. Enriched data that is not necessary for payment processing such as location, mobile device id, cookie for online store, channel, frequency of use are other features that can be incorporated while developing insight from the payment data.

Use case for these analytics

-Internal

Operational efficiency such as cash loading cycle for ATMs, designing reward programs for encouraging a specific banking channel, loan underwriting feeds, better AML/KYC to start with and these can go deeper as the bank becomes familiar with exploiting the use cases and repurpose for other areas

-External

Developing premium products such as integration to corporate ERP systems for real time cash flow analysis, treasury collateral forecasting, sharing purchasing behaviour with customers is helpful for predicting seasonality in purchase, value or impact of a promotion or sale offers. These offerings build deeper touch points with customer and ring fence the customer from competition by fintechs.

 

 

 

Read More

Brief on ISO20022 CAMT Reporting

 

 

Under the ISO20022 payment messages for credit transfers, direct debits and electronic payments will all need to use the same standards, languages, procedure, and format to be compatible. The new format is called CAMT for Cash Management. CAMT ensures the customer a continuous XML process from submission through to the account statement with no disruption and specifically covers Bank to Customer Cash Management reporting

The three most relevant CAMT formats for payment processes are listed below:

• camt.052 – Electronic Account Report

This bank-to-customer account report will provide you with information on all transactions and entries. The camt.052 will enable you to control your cash assets and take advantage of interest on credit balances. This is your intraday information and provides the customer with a near real time view of their accounts. The camt.052 replaces the Swift MT942 Interim Transaction Report.

• camt.053 – Customer Statement

This bank-to-customer statement provides you with the required information about your entries. With camt.053, you have detailed, exact, and organized information on all entries for your prior day. The camt.053 is an alternative to the MT940 Customer Statement Message.

• camt.054 – Bank-to-Customer Debit/Credit Notification

The camt.054 format provides you with specific account debit and account credit information on all transactions entered on your account. The reports in camt.054 allow you to carry out the processing of individual transactions entered on your account as a total figure. The camt.054 replaces Swift MT900 Confirmation Debit, and MT910 Confirmation Credit messages.

Form payments to reconciliation the business process is enhanced in CAMT. CAMT reporting enables consistency, moving towards a standard where banks populate the information in a specific and defined manner since there are specific tags to report specific information.

 

 

 

 

Read More

Case for ISO20022 migration

 

Its not about a technical specification and the fact that a lot of data travels with the payment in ISO20022.In making a business case for migrating to ISO20022, its very hard to sell to executives why a change of this magnitude is desirable. I collected a couple of data points both for the bank and its customer to showcase why this migration is desirable.

 

For Bank:

Banks have a very complex legacy architecture that has served them well for most part. However, the cost of servicing failed STP payment transactions is becoming prohibitive.

In Singapore for example a 60% STP rate is the norm. What is the norm for your bank? Is it acceptable? Factor in costs for false positives in sanctions screening. The business case can be built around these two cost factors as a starting point.

 

For Customer:

An Insurance company for example can expect 400 invoices to be paid in 10 payments. If the bank can provide enriched data about these invoices and payments the reconciliation effort is substantially reduced. The reporting around this information can be built into the value proposition.

 

What if the bank does nothing?

Over time the legacy infrastructure burden will render the bank unable to compete even if there is time available to migrate to ISO20022. The bank may have to start somewhere, perhaps look at message translation options as a starting point.

 

The way to build the business case will be in terms of operational costs, customer servicing and mandate timelines coming from bodies like SWIFT and country specific modernization deadlines.

 

Read More

ISO20222 and Straight through processing (STP)

The main benefit of ISO20022 rests on the fact that it will allow higher STP throughput. Let’s peel this onion a little bit.

What we know:

-The ISO 20022 standard defines a methodology for the development of financial message standards.

- It relies on UML3 (Unified Modeling Language) models representing financial business processes, flows and transactions in a neutral notation.

-These business transaction models are then subsequently converted into physical messages in the desired syntax, like XML (eXtensible Mark-up Language).

- ISO 20022 defines the methodology for encapsulation business transactions and the data dictionary that is required to support those transactions. For example, a financial message can be completely compliant with ISO 20022 but be expressed as fixed width record layouts or API-based constructs such as JSON.

 

So what?

UML offers a standard way to visualize a system’s architectural blueprints and associated components like actors and activities.

What it means is:

-Take a business process such as a payment or securities instruction between parties.

-Break it down into the flow of information between the parties and/or systems (the actors)

-Think of an instruction sent (an activity), followed by status updates, a notification of settlement and a final end-of-day statement.

-Next,  break down into the components that define the information required, for example what is a currency, what is an account, etc.

Conclusion:

The result of the exercise is that you end up with a “Repository” of base business definitions that underpin all compliant messages that adhere to the standard. The advantage of this is that anyone who wants to create a compliant message is at liberty to call the elements what they like, but by linking them to the base types in the repository you can be sure that all parties involved in the processing of the message will have a common understanding of what a currency or account is and what its format is. This represents a major building block for effective inter-organization STP (Straight-Through-Processing) of information.

References:

www.volantetech.com

Read More

Compliance a Concern for Banks migrating to ISO20022

As ISO 20022 becomes more prevalent as a message standard of choice, banks are wrestling with the compliance risks that come with implementing this standard.

 

For the last 40 years a name and address in Swift MT consisted of 4 lines of 35 characters each. MT focused on concise information as opposed to clarity since it was developed in the days of low bandwidth and leased data lines were every expensive. In addition, over the last few years there has been the requirement of AML screening against sanctions lists and enhanced KYC including more information about LEI, names and addresses of beneficiaries. Further, the MT formats only support a Latin syntax whereas the rise of Asian character sets like Chinese are required nowadays.

 The ISO 20022 message definitions specified by payment providers include more data than the corresponding MTs used in cross-border business. If an ISO 20022 instruction is converted to MT for a cross-border leg, there is a risk of data being dropped or truncated. This creates compliance concerns because dropping data in end-to-end payment processing is unacceptable. Incomplete data, truncated data, false positives around sanctions lists all lead to increased regulatory burden for banks. The cost of investigation of errors and customer service grows proportionally. 

Banks must consider several thousand man-days of effort to ensure the data flows seamlessly. Some areas they will need to look at:

 -Legal Entity Identifier reference look up database 

-Source data for KYC with more accurate data capture at payment origination point. 

-High value system gateway updates 

-Updates from clearing system need to have a process to manage and apply the changes periodically

-Support of ISO20022 data, XML middleware, storage, and security

Read More

Understanding ISO20022 Message Types

 

So what is the fuss all about? Currently the transaction related information is sent in legacy formats (e.g. SWIFT MT) and that is expected to change with the use of ISO20022.

Let us look at the different message formats and where they are used in ISO20022. These formats will cover debit, credit, mandates, settlement, investigations and statements to name the key ones. In ISO 20022’s naming scheme, message type is described with four letters followed by three sets of numbers.

 

Message Type:

Pain.001 or Payment Initiation—this depicts a credit transfer message. It can also be used for payment of salaries and checks. Other message versions are also being published by ISO.

Other message types include Camt (Cash Management and Reporting) and  Pacs ( Payment Clearing and Settlement)

The tables below summarize the different types of message formats

 

Customer and Bank
Payment	Pain.001	Pain.002	Pain.007	Pain.008
Mandates	Pain.009	Pain.010	Pain.011	Pain.012
Overlay Services
1.       Request to Pay	Pain.013	Pain.014
2.       Enhanced Data	Remt.001	Remt.002
Payment Reporting	Camt.052	Camt.053	Camt.054

 

 

Interbank Payments
Payments	Pacs.002	Pacs.007	Pacs.008	Pacs.004
Settlement	Pacs.009	Pacs.010	Pacs.002
Reporting, Admin	Camt.052	Camt.56	Admi.0nn
Investigations	Camt.029	Camt.030

 

 

Now that we understand the different message types lets look at this chart from SWIFT to see how a legacy MT message is mapped to an ISO20022 message.

 

This is the first challenge:

-To understand what systems are impacted by the new standard

-How to map the legacy message to ISO20022.

Read More

What is ISO20022?

 

ISO 20022 is the latest international financial messaging standard to exchange transaction information between the players in the financial ecosystem. With the growth in Internet Protocols and XML this standard was derived to capture the benefits of these new technologies. It was first released in 2004, so it has been around for while and well accepted. Around 200 FIs globally are considering implementing, in addition to market participants like SWIFT, Ripple and Visa to name a few.

 The standard allows users and developers to represent financial business processes and underlying transactions in a formal but syntax-independent notation. The business transaction models can be converted into physical messages in the desired syntax. ISO20022 can be used across various business domains, communication networks, and the infrastructures of financial institutions, clients and suppliers. This flexibility provides many benefits for financial institutions to improve transaction efficiency while reducing costs and exposure to risk.

The benefit of ISO20022 messaging to SME and large enterprises is reducing the effort and difficulty of matching customer payments to invoices, increasing accuracy of cash flow forecasting and better visibility into collections.

Banks that can help customers provide these details around their transactions will provide differentiated services leading to higher revenue generation. In future they can utilize the data gathered from these payment transactions to understand the customer’s business in finer detail and offer predictive insights.

Read More

 Welcome to my blog.

Here I will endeavor to post in brief some of the key issues facing the payments industry as banks modernize their financial messaging infrastructure. These are the common themes: ISO20022, APIs, Open Banking. In future posts you can see updates on current thinking on how to approach the major aspects and some more detail of what needs to happen at the frontlines.

I hope my content helps executives at banks and product managers who are not payment experts to get a birds eye view of the effort and opportunities in this journey.

Stay tuned!

Read More