Businesses need payments. This is not a groundbreaking revelation, but it is fundamental to how businesses operate. So, why is there still such fragmentation in the payments space?
If a business can’t receive payments from customers, then it wouldn’t be in business for long. As a counterpart to this, if a business can’t make payments, it can’t stock its shelves, delight customers with food and drink, or pay its employees, thereby grinding the economic wheel to a halt.
Payments have evolved in tandem with technological revolutions over millennia. The digital revolution over the last 50 years has seen card payments soar globally, and as we progress into the intelligence revolution, payments must continue to evolve. We are on the cusp of seeing agentic commerce and AI-based searching revolutionise the way businesses and customers interact. Businesses face a key challenge of managing the complexities of incoming and outgoing payment solutions before even considering AI-based innovations.
Data from RFI Global’s UK Business Payments Council demonstrates that the number one area for improvement in the domestic payments experience is the ability to manage all payments in one place – across banking and external software. A third of businesses interviewed (32%) feel this would most improve their domestic payments experience.
The key insight here is not necessarily that all businesses want every payment visible on their banking software, or that they want every payment on an external software. It varies substantially. Even two businesses with the same profile in terms of revenue, industry, region, or even the individual decision maker in a business might prefer one solution over the other.
Understanding the complexities of businesses’ integration needs is a topic in its own right, but it is clear that unified management is a key issue for businesses. The main reason behind this desire for improvement is to save businesses’ time. Reducing the manual reconciliation process is a much-wanted improvement for over a quarter of businesses (28%) – being able to flexibly use any type of payment method for any expense. This matters for banks and financial institutions because it indicates a key shift in payments. The method of payment is less of an issue than the means by which payments are managed.
Creating a perfect solution that meets the needs of every business is a near, if not totally insurmountable, task due to the immense variation in solutions and preferences. Fortunately, this is not the route that needs to be taken. Businesses already have enough solutions to use. One in four UK businesses are multi-banked, and additionally, businesses have accounting software, acquiring, enterprise resource planning (ERP) solutions, inventory management, logistics management, CRM solutions, ecommerce solutions, POS systems… and more. With so many solutions already available, trying to create one tool that captures everything is something certain brands have been working on for decades.
Instead, our data shows that the focus needs to be on granting businesses the flexibility to manage payments, holistically, in the tool that they prefer. There isn’t a strong preference for banking to be integrated into external software, or vice-versa.
Most businesses (48%) want to have both sets available in either solution – i.e., omni-directional integration. What this data does not show is that everything, everywhere, all at once needs to be integrated. Instead, it reflects the latent need for flexibility among UK businesses. There isn’t a uniform direction for integration – it varies down to the level of individual decision makers in the same business.
Our data shows clear priorities on what should be integrated. Access to cashflow forecasting tools is the most desired integration (32%), regardless of the direction of integration.
The preference for cashflow forecasting tools indicates another latent need – a desire for greater visibility, predictability and insight from the data a business already has. This is the true characteristic of the new intelligence revolution. Data is not the new gold but instead the new oxygen for businesses. A seamlessly integrated solution that enables holistic payments management, with information on money in and out, incorporating tax liabilities and forecasting? While this isn’t perhaps needed for the one-man-band gardeners of the UK, it is undoubtedly needed for the scaling SMEs that will drive the economy through the intelligence revolution.
UK businesses are looking for digital payment tools that streamline their operations, provide insight into these operations and drive their next phase of growth. The UK has maintained its reputation as a global financial innovation hub despite the trials and tribulations over the last 10 years. RFI Global has been helping financial institutions worldwide to understand the payments landscape and advise on effective change for two decades and will continue to do so throughout the next stage of the payments revolution.
For more information on how RFI Global can help your business drive effective payment strategies, get in touch for further insights from the study.
UK businesses want the ability to manage all payments in one place, across both banking platforms and external software. RFI Global data shows around a third of businesses prioritise unified payment management to improve efficiency and reduce manual processes.
Payment fragmentation persists due to the growing number of systems businesses rely on, including banking, accounting, ERP and payment solutions. This creates complexity in managing money in and out, increasing manual reconciliation and reducing operational efficiency.
Not necessarily. RFI Global data show that businesses do not have a uniform preference for where payments should sit. Instead, they want flexibility to manage payments in their preferred environment, whether within banking platforms or external software.
The key driver is the need to save time, reduce manual reconciliation and improve visibility across all financial activity. As payment options expand, businesses are increasingly focused on how payments are managed, rather than the specific method used.
| Cookie | Duration | Description |
|---|---|---|
| __cf_bm | 1 hour | This cookie, set by Cloudflare, is used to support Cloudflare Bot Management. |
| __hssc | 1 hour | HubSpot sets this cookie to keep track of sessions and to determine if HubSpot should increment the session number and timestamps in the __hstc cookie. |
| __hssrc | session | This cookie is set by Hubspot whenever it changes the session cookie. The __hssrc cookie set to 1 indicates that the user has restarted the browser, and if the cookie does not exist, it is assumed to be a new session. |
| AWSALBCORS | 7 days | Amazon Web Services set this cookie for load balancing. |
| AWSALBTG | 7 days | Amazon Web Services set this cookie for load balancing. |
| AWSALBTGCORS | 7 days | Amazon Web Services set this cookie for load balancing. |
| cookielawinfo-checkbox-advertisement | 1 year | Set by the GDPR Cookie Consent plugin, this cookie records the user consent for the cookies in the "Advertisement" category. |
| cookielawinfo-checkbox-analytics | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Analytics". |
| cookielawinfo-checkbox-functional | 11 months | The cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Functional". |
| cookielawinfo-checkbox-necessary | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookies is used to store the user consent for the cookies in the category "Necessary". |
| cookielawinfo-checkbox-others | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Other. |
| cookielawinfo-checkbox-performance | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Performance". |
| CookieLawInfoConsent | 1 year | CookieYes sets this cookie to record the default button state of the corresponding category and the status of CCPA. It works only in coordination with the primary cookie. |
| elementor | never | The website's WordPress theme uses this cookie. It allows the website owner to implement or change the website's content in real-time. |
| rc::a | never | This cookie is set by the Google recaptcha service to identify bots to protect the website against malicious spam attacks. |
| rc::c | session | This cookie is set by the Google recaptcha service to identify bots to protect the website against malicious spam attacks. |
| viewed_cookie_policy | 11 months | The cookie is set by the GDPR Cookie Consent plugin and is used to store whether or not user has consented to the use of cookies. It does not store any personal data. |
| wpEmojiSettingsSupports | session | WordPress sets this cookie when a user interacts with emojis on a WordPress site. It helps determine if the user's browser can display emojis properly. |
| XSRF-TOKEN | 2 hours | This cookie enhances visitor browsing security by preventing cross-site request forgery. |
| Cookie | Duration | Description |
|---|---|---|
| AWSALB | 7 days | AWSALB is an application load balancer cookie set by Amazon Web Services to map the session to the target. |
| AWSALBTG | 7 days | Amazon Web Services set this cookie for load balancing. |
| AWSALBTGCORS | 7 days | Amazon Web Services set this cookie for load balancing. |
| Cookie | Duration | Description |
|---|---|---|
| __hstc | 6 months | Hubspot set this main cookie for tracking visitors. It contains the domain, initial timestamp (first visit), last timestamp (last visit), current timestamp (this visit), and session number (increments for each subsequent session). |
| _ga | 1 year 1 month 4 days | Google Analytics sets this cookie to calculate visitor, session and campaign data and track site usage for the site's analytics report. The cookie stores information anonymously and assigns a randomly generated number to recognise unique visitors. |
| _ga_* | 1 year 1 month 4 days | Google Analytics sets this cookie to store and count page views. |
| hubspotutk | 6 months | HubSpot sets this cookie to keep track of the visitors to the website. This cookie is passed to HubSpot on form submission and used when deduplicating contacts. |
| wmc | 1 year 1 month 4 days | Workable sets this cookie to assign a unique visitor ID for statistical purposes. |
| Cookie | Duration | Description |
|---|---|---|
| _cfuvid | session | Description is currently not available. |