Routefusion found its business in everyone else's plumbing

Payment Labs had a problem that sounds almost offensively basic: paying people. Its operations stretched across more than 100 countries, and it needed an international payment provider that would work with its existing systems. It evaluated more than thirty vendors. In Routefusion’s published case study, the eventual choice produced two striking results: onboarding took two weeks, and payment returns fell from 10% to below 1%. For a business whose product involves delivering money, a returned payment is a particularly awkward form of customer feedback.

That last question helps explain Routefusion. A payment button occupies very little screen space. Behind it sits a collection of banks, currency providers, recipient requirements and operating hours. The company sells access to that collection, together with the work required to make it behave like a product.

01 / The bank that became the plumbing

Colton Seal’s first idea, in 2016, was to build a bank. The route to Routefusion included a wallet-style app, international accounts payable and a proposed exchange-rate comparison network. In his retrospective, stacked provider markups made the early economics unattractive. In April 2018, Seal and Richard Scappaticci each called 50–100 prospective businesses a day. The conversations exposed how little a nicer interface distinguished their offering.

The more consequential discovery followed: their partnerships connected providers with different strengths. Bringing those capabilities together became the product. There was another mistake along the way. Seal wrote that fundraising had distracted them from acquiring customers. The practical lesson is wonderfully unfashionable: keep talking to the people who might pay you.

02 / One entrance, several routes

Routefusion now puts local payment networks, SWIFT and stablecoin-funded settlement behind one integration. Its customers can build payouts into their own software, while the infrastructure handles the underlying movement. The company lists Jeeves, Clara and Plane among its customers; its intended audience includes payroll and employer-of-record platforms, marketplaces, payment service providers and financial institutions.

The engineering proposition is concrete. Routefusion’s developer tools include a GraphQL API, a testing sandbox and webhooks that notify a customer’s software when events occur. A platform can create a transfer, retrieve its status and update its own user experience. The sandbox gives engineers somewhere to test before their experiment acquires a disappointed recipient.

Local rails are an important part of the argument. Routefusion supports networks such as Brazil’s PIX, Mexico’s SPEI and Europe’s SEPA. Domestic delivery can offer lower costs and better visibility than a wire. But the company’s own routing guidance is conditional: currency, beneficiary data, amount and receiving-bank requirements determine the sensible path. A country appearing on a coverage map does not settle those questions.

That network is assembled through partnerships. In April 2024, Routefusion said it had a gap in real-time FX payment rails. Adding Thunes expanded local-network coverage into more than thirty additional countries. The admission is more informative than a sweeping coverage claim: even a global API has specific holes to fill.

03 / Money needs an identity

Sending funds is half the administrative problem. Incoming money must also be attributed. Routefusion’s virtual accounts assign distinct receiving details to a customer, transaction or department. That gives a finance team a way to identify a payment without turning reference numbers into a weekly detective serial.

Named non-resident USD accounts tackle a related access problem. Eligible platforms can issue accounts in their end users’ names through multiple sponsor banks. Routefusion emphasizes independent reconciliation at each sponsor. This detail matters: several banking relationships are useful only if the operating records can explain what happened at each one. Its Ledger product consolidates balances, transactions and reconciliation across currencies for reporting and customer-facing account activity.

04 / The transfer fee is the beginning

Routefusion charges transaction service fees, with commercial terms shaped around the customer’s flows. Its documentation makes a small but consequential distinction: when a transfer specifies the source amount, the fee comes out before conversion; when it specifies the destination amount, the required source amount includes the fee. Buyers should test what the recipient actually receives.

“the team was very honest and upfront on how they charge for services”Ronak Desai · CTO & co-founder, Payment Labs

Desai’s assessment accompanies the case study’s results. Those are customer outcomes reported by Routefusion, rather than a universal promise. Still, they suggest a better purchasing exercise: compare fees alongside onboarding effort, failed-payment work and reconciliation. An inexpensive transaction can be an expensive support ticket.

Routefusion’s buying guide asks customers to count the work beyond the quoted rate: maintaining integrations, reconciling accounts, handling banking disruption and getting support when money stalls. That is a sensible frame for a platform team. Request a demonstration of the exception workflow as well as the successful transfer. The finance team will eventually need both, even if the sales presentation prefers the happier screen.

Treasury adds another wrinkle. Routefusion’s Hedge product offers forward contracts to lock rates for future obligations. Settle accepts USDC funding and advertises conversion to USD at 1:1 before global payouts. These solve different problems: currency uncertainty and funding availability. Neither removes the final payout’s bank, rail or compliance conditions.

05 / Buy the route you actually need

The company’s October 2025 Series A brought total reported funding to $40.7 million. PeakSpan led, with Silverton participating. Planned spending included partner coverage, liquidity, compliance and launch operations. Those priorities reveal how much of the business lives beyond the API.

For a buyer, the comparison includes providers such as Wise Platform, Airwallex and Nium, as well as direct bank integrations. Routefusion’s proposition combines multiple partners with onboarding and operational support. Its own release makes the boundary clear: Routefusion is not a bank; regulated partners provide services, and availability varies by jurisdiction.

A useful first step is to specify one real payment corridor, then test recipient fields, funding, fees, delivery timing, returns and ledger entries. A platform adding international payouts may benefit from that arrangement. A business needing only one uncomplicated domestic flow may have less reason to buy a broad network. The founders’ discovery remains relevant: the valuable product is the one the customer’s actual problem requires.