How Wise Built a Cross-Border Payments Infrastructure Business

Cross-border payments are an everyday operating problem for exporters, remote-service firms, online sellers and companies that buy from overseas suppliers. A payment can appear simple at the point of instruction while its true cost remains spread across an exchange-rate margin, a transfer fee, intermediary-bank deductions and the value of time lost while money is in transit. Wise’s growth offers a useful business-model case study because the company did not begin by inventing a new reason to move money. It redesigned the infrastructure and price presentation around a familiar but poorly explained task.

This is not a recommendation to use Wise or to invest in the company. Availability, fees, protections and features differ by country, currency and customer type. The case is valuable because it shows how a startup can turn a narrow consumer frustration into a broader financial-services network—and why regulation, risk controls and operational reliability become part of the product as that network grows.

The original proposition: make the hidden cost visible

Wise was founded in 2011 as TransferWise. Its early proposition challenged a common feature of international transfers: a provider could advertise a low or zero transfer fee while earning money through the exchange rate. Wise instead built its customer message around the mid-market exchange rate and a separately disclosed fee. That separation made comparison easier and converted transparency from a compliance detail into a product feature.

The deeper operational idea was to reduce unnecessary cross-border movement by using local payment connections. In a simplified example, a customer funding pounds in the United Kingdom and a recipient expecting euros in Europe do not require the same units of money to travel through a long chain of correspondent banks. A network that can receive locally, match liquidity and pay out locally can remove steps, although actual routing varies by currency, regulation, liquidity and transaction conditions.

Scale came from infrastructure, not only an app

A polished interface can attract customers, but a payment company’s durable capability lies behind the screen: licences, bank and payment-system connections, treasury operations, fraud controls, reconciliation, customer support and software that can make millions of transaction decisions reliably. Wise’s current model combines services for individuals, Wise Business accounts and Wise Platform, which allows banks and enterprises to connect to parts of the company’s payments infrastructure through APIs or Swift.

Wise says its Platform network covers more than 160 countries and 40 currencies, with direct access to domestic payment systems in eight markets. On its Q1 FY2027 product page, the company reported that 77% of payments arrived in under 20 seconds and 96% within 24 hours. These are company-reported network measures, not a guarantee for an individual transfer; payment speed depends on the route, checks, funding method and receiving institution.

FY2026 results show the economics of lower unit pricing and higher volume

For the financial year ended 31 March 2026, Wise reported 18.9 million active customers, up 21% from the prior year, and US$243.5 billion in cross-border volume, up 31%. Net revenue increased 19% to US$2.50 billion. The company’s average cross-border take rate—the proportion of transfer volume retained as cross-border revenue—fell from 0.58% to 0.52%. In plain language, the disclosed numbers show volume growing faster than the average revenue rate on transfers.

Nearly half of FY2026 net revenue came from sources other than cross-border transaction revenue, including net interest income, cards and other revenue, according to the company’s results. Customer holdings reached US$39.0 billion and card spending US$43.6 billion. That mix illustrates a familiar platform strategy: win trust through one frequent problem, then build adjacent services around the customer’s workflow. It also increases responsibility because customers may begin treating a payments account as part of their daily financial infrastructure.

The second business model is infrastructure for other companies

Wise Platform turns capabilities originally built for Wise’s own customers into services that other financial institutions and enterprises can integrate. This business-to-business layer matters strategically. A bank, payroll platform, marketplace or spend-management provider may want global payouts without building every local connection, compliance process and currency route itself. The infrastructure provider can then grow through partners while the partner retains its own customer relationship.

For entrepreneurs, the transferable lesson is not simply to create an API. First build a repeatable internal capability that solves an expensive operational problem. Only then consider whether that capability can become a product for other businesses. A logistics company might expose shipment tracking; an accounting service might productise reconciliation; a manufacturer might offer quality-testing capacity. The new service must have clear ownership, pricing, service levels and data protections rather than being an informal side job.

Trust and regulation are operating costs, not marketing decoration

A payments company cannot scale responsibly on speed and price alone. It must verify customers, screen transactions, protect systems, investigate fraud, meet reporting duties and comply with the rules of each market in which it operates. Those requirements create costs and can delay some transactions, but ignoring them would expose customers and the financial system to much larger risks.

The distinction between a bank deposit and safeguarded money is especially important. The UK Financial Conduct Authority says authorised payment and electronic-money institutions must safeguard relevant customer funds, generally through segregation or qualifying insurance or guarantees. Safeguarding is intended to protect funds if a firm becomes insolvent, but the FCA also explains that money with payment and e-money firms is not directly covered by the Financial Services Compensation Scheme and repayment after a failure may take time or be reduced by administration costs.

Rules also change. New UK safeguarding requirements took effect in May 2026, adding more detailed client-asset and reporting obligations for affected firms. An international SME should therefore check the regulated legal entity serving its country, not assume that a global brand provides identical protections everywhere.

Five practical lessons for a growing SME

First, make the customer’s total cost legible. A buyer should be able to understand the price, taxes, delivery charge, recurring fee and cancellation terms before committing. Transparency can reduce support questions and create trust even when a business is not the cheapest.

Second, improve the operating system behind the promise. If a company advertises fast delivery, it needs inventory accuracy, dispatch controls and carrier visibility. If it promises dependable bookkeeping, it needs reconciled records and review procedures. Marketing cannot permanently compensate for an unreliable process.

Third, turn scale into a customer benefit. Wise reports that its cross-border take rate declined while volume rose. That does not mean every company should cut prices. It means an enterprise should identify which savings from automation, purchasing or process design can be shared with customers without weakening cash flow.

Fourth, treat compliance as product design. Privacy notices, identity checks, refund procedures, tax records and sector licences affect how customers experience a service. Building them late is usually more expensive than including them in the workflow from the beginning.

Fifth, consider a business-to-business extension only when the core capability is proven. Selling infrastructure can diversify revenue, but business clients expect security reviews, documentation, integration support, reliable uptime and clear accountability. A weak internal process does not become stronger merely because it is offered through an API.

A cross-border payment checklist for SMEs

Before choosing any provider, compare the amount the recipient will actually receive—not only the advertised fee. Record the exchange rate, fixed and percentage charges, potential intermediary deductions, expected delivery time and refund process. Confirm whether the provider and the relevant legal entity are regulated in the sender’s or recipient’s jurisdiction. Check account limits, supported business activities, customer-service access, data-export options and whether payments can be reconciled with the company’s accounting system.

Businesses should also maintain a backup payment route. Compliance reviews, bank holidays, technical failures, beneficiary errors and country restrictions can interrupt even a well-designed service. Supplier contracts should state the invoice currency, who bears transfer charges, when payment is considered complete and how exchange-rate differences will be handled.

The larger lesson

Wise’s case is often presented as a story about cheaper transfers. The more useful interpretation is that it is a story about making an opaque cost visible, redesigning the operating network, and then offering that network to other companies. Its reported FY2026 scale demonstrates the commercial power of that sequence, while current safeguarding rules show the responsibility that accompanies it. For SMEs, the objective is not to copy a fintech product. It is to find a costly point of friction, explain the economics honestly, build dependable operations and earn the right to expand.