A vision for a future of frictionless commerce

Payments connect the people, systems and markets that make commerce possible. When a payment depends on manual work, disconnected data or an unclear settlement process, that friction reaches beyond the finance team. It affects the experience of buying, selling, supplying and getting paid.

Nium's whitepaper A Vision for a Future of Frictionless Commerce sets out a framework for changing that experience: make payments simple, seamless and scalable. This article adapts the original 2021 whitepaper by Arnav Gupta and Spencer Hanlon into a practical guide for business and technology leaders. Its framework is presented here without treating the report's historical forecasts, product examples or network figures as current commitments.

What is frictionless commerce?

Frictionless commerce is an approach to buying, selling and moving money that reduces unnecessary steps for customers and businesses. In the whitepaper's vision, payments fit naturally into the activity they support, while the processes behind them handle payment information, identity, risk and operational requirements.

A simpler interface is only one part of the work. The payment must also connect to your business systems, carry useful information and support the markets and transaction volumes your business needs. That is why the report treats simplicity, seamlessness and scalability as connected principles.

For business leaders, the aim is to make payment capabilities part of business strategy. For technology and operations teams, it means looking at the complete journey, including onboarding, approval, funding, payment status and reconciliation.

Where payment friction holds businesses back

The whitepaper identifies four sources of friction that can make payment processes difficult to improve. Start by finding where each appears in your own workflow.

Manual processes slow the payment journey

Manual B2B payment workflows take time and create opportunities for errors. Supplier onboarding, payment preparation and reconciliation can each require people to move information between systems. Improving the transfer itself leaves those surrounding tasks unresolved.

Map who collects payment details, who approves a transaction and how the completed payment is matched to an invoice. The report recommends examining those steps as one journey rather than treating each department's task in isolation.

Disconnected systems make information harder to use

Different payment platforms, messaging formats and processing schedules can create separate islands of information. When counterparties use different systems, the work of connecting a payment to its business purpose becomes more complicated.

The report links fragmented data with limited straight-through processing and manual reconciliation. A payment process needs information that can move between systems as well as funds that can move between accounts.

Compliance requirements add operational complexity

Cross-border payments involve identity, risk and regulatory requirements across markets. The whitepaper describes the difficulty of incorporating these requirements into payment processes as infrastructure and rules change.

Its design principle is to integrate necessary checks into the journey. Reducing visible friction does not remove the need for appropriate controls. The relevant responsibilities and information requirements still need to be understood for each service and market.

Legacy integrations make change difficult

Businesses can accumulate layers of payment technology that are hard to replace or upgrade. Batch processing and file sharing may then remain central to the workflow even when other parts of the business operate through connected digital services.

The whitepaper recommends real-time APIs as a way to connect payment capabilities with business systems. The integration decision should include the data and processes surrounding a payment, alongside the instruction to send it.

Simple payments start with the user experience

The first principle is simplicity. People want to buy a product, receive a service or be paid for their work. A payment experience should support that purpose without making users navigate unnecessary screens or repeatedly provide information.

The report explores how payments can become part of the wider experience. It uses India's Unified Payments Interface as a historical example of payment capabilities embedded within applications, and discusses identity and authentication technologies as part of that design direction.

The useful lesson is to consider convenience and security together. Identify where users must repeat information, switch applications or wait for confirmation. Then examine which steps serve a necessary purpose and which result from disconnected systems.

The whitepaper also considers loyalty and rewards within the payment experience. Its broader point is that a payment is part of an ongoing relationship with a customer or supplier. The experience of completing it can matter as much as the surrounding product journey.

Seamless payments connect the work behind the scenes

The second principle is seamlessness. A clear customer experience depends on coordinated work across identity verification, payment processing, risk controls and business systems. Those processes should exchange the information needed to keep the transaction moving.

Connect payments with treasury and finance

The report describes the role of treasury management and enterprise resource planning systems in providing insight into working capital, liquidity and payment status. When payment information arrives late or must be entered manually, finance teams have more difficulty understanding the position of funds.

API connections and useful status information can support accounts payable, accounts receivable and reconciliation workflows. In an evaluation, look at how the payment record reaches your finance system and how your team handles incomplete information.

Build risk and identity processes into the journey

The whitepaper discusses coordinated identity data, transaction information and risk checks as part of a more connected payment process. It also considers pre-validation and payment tracking as ways to improve visibility across borders.

These are workflow considerations, not reasons to assume a check can be skipped. When assessing a provider, establish what information your team must collect, which checks the service performs and how exceptions are returned to your systems.

Support connected business ecosystems

Payments often sit within a wider set of services, such as accounting, payroll, point of sale and supplier management. The report uses software ecosystems to illustrate how businesses can access connected services through the tools they already use.

That perspective changes the integration brief. Instead of asking only how to initiate a payment, ask how the payment supports the surrounding business activity and what information other participants need.

Scalable payments support growth and changing demand

The third principle is scalability. Businesses need payment processes that can respond to changes in transaction volume, business cycles and market requirements. A workflow that depends on additional manual work for every payment becomes harder to manage as activity grows.

The whitepaper considers APIs and modular payment capabilities important to that growth. Connections between payment providers and specialist services can support onboarding, risk processes and access to payment methods. The practical question is how those connections work for your intended use case.

International expansion adds another dimension. A business may need different payment methods and operating requirements in different markets. The report argues for considering geographic reach and the ability to add capabilities alongside transaction capacity.

When comparing partners, examine support for the markets and methods on your roadmap, integration requirements and service continuity. The original report's network counts and availability statements describe its publication period; confirm current service details for the routes you plan to use.

Four steps to start your payment transformation

The whitepaper closes with four recommendations. Together, they connect business priorities, user needs, technology and provider selection.

1. Make payment improvement a business priority

Look beyond payments as a processing cost. Identify how the current workflow affects operational efficiency, supplier experience and growth. Establish which problems are important enough to change and which teams need to participate.

2. Map the complete customer and business journey

B2B journeys can involve several departments, approval steps and decision-makers. Research the experience before and during the mapping process. Include the work users do before a payment is sent and after it arrives.

Record pain points such as repeated data collection, unclear status and manual matching. Use that evidence to define the integration and process changes you need.

3. Adopt APIs and richer payment information

The report recommends real-time APIs and global payment messaging standards, including ISO 20022. Its emphasis is on connecting systems and carrying richer information so that payment processes can become more automated.

Assess how your systems will use that information. Define the references, status updates and reconciliation data that must reach the right team, alongside the requirements for payment initiation.

4. Select a partner that can support your roadmap

A provider assessment should cover the capabilities you need now and the changes you expect as the business grows. The report highlights geographic reach, integration and service continuity as considerations.

Compare providers against your own journey map. Ask how each would support your payment methods, data requirements, operational processes and future markets. Use those answers to make the decision concrete.

Read the original frictionless commerce whitepaper

The original whitepaper brings these themes together around a clear idea: better payment experiences depend on simple interactions, connected processes and infrastructure that can scale.

Read A Vision for a Future of Frictionless Commerce (PDF), by Arnav Gupta and Spencer Hanlon, published by Nium in 2021. The PDF contains the original illustrations, examples and historical context.

To discuss your own payment journey and business requirements, talk to Nium.