DEV Community: Belyfted

Why Two Money Transfer Apps Never Quote You the Same Number (A Builder's Look at Cross-Border Pricing)

Belyfted — Tue, 21 Jul 2026 18:11:21 +0000

Why Two Money Transfer Apps Never Quote You the Same Number (A Builder's Look at Cross-Border Pricing)

TL;DR: If you've ever wondered why a "£0 fee" transfer can still cost more than a competitor charging £3.99, the answer isn't marketing, it's how FX pricing, liquidity, and payout rails actually work under the hood. This is a quick breakdown from the payments side, not the consumer-tips side.

The problem most fintech explainers skip

Most "how to send money abroad" content stops at "compare fees." That's surface level. The real cost of a cross-border transfer is built from a few layers most users never see, and honestly, a lot of builders outside payments don't think about either:

The FX spread: Every provider sources currency at, or close to, the interbank mid-market rate, then marks it up before quoting the sender. That markup is the actual profit margin on a "free" transfer. You can watch this live by comparing any provider's quoted rate against the mid-market rate published by XE.com or Reuters at the same moment.
Liquidity and settlement rails: Corridors like UK to Nigeria, UK to India, or UK to the Philippines don't all settle the same way. Some route through correspondent banking, some through local mobile money aggregators, some through licensed payout partners. Each hop adds cost and latency, and that cost gets priced into the spread, not itemised as a fee line.
Regulatory overhead per corridor: A provider licensed to operate in the UK still needs the receiving side to be compliant. For Nigeria specifically, that means holding an International Money Transfer Operator (IMTO) licence recognised by the Central Bank of Nigeria, on top of UK obligations like FCA authorisation and HMRC money laundering registration. None of that is free to maintain, and it shows up in pricing.

Why "zero fee" is a UI decision, not a cost decision
A provider can absolutely charge £0 upfront and still make more money than a competitor charging a flat fee, simply by widening the FX spread. From a product perspective, this is a deliberate framing choice: users respond to a visible fee number far more than an invisible rate gap, even when the rate gap is the bigger cost.

If you're building or evaluating anything in this space, the number that actually matters is total cost: fee plus spread, benchmarked against the real mid-market rate, not the advertised fee in isolation.

What determines whether a corridor is "easy" or "hard" to build for
Some corridors are structurally harder than others, independent of how good your app is:

Payout method fragmentation, a recipient in one country might expect a bank transfer, another might expect mobile money, another might expect cash pickup. Supporting all three, and doing it reliably, is an integration and reconciliation problem, not just a UI toggle.

Local licensing requirements, being FCA-authorised on the sending side covers you in the UK. It says nothing about whether you're legally allowed to pay out in Lagos, Nairobi, or Manila. Each receiving country has its own rules, and providers that skip this step are the ones that eventually get flagged or shut down.
Settlement time variance. Same-day payout in one corridor might be a two or three business day wait in another, purely because of how the local rail clears funds, not because of provider laziness.

Takeaway for anyone building in payments or fintech
If you're building anything adjacent to cross-border payments, the lesson generalises: hidden cost usually lives wherever transparency is hardest to enforce, and regulation is usually a proxy for whether the operational plumbing actually works.

Belyfted's own build has had to account for all three layers above across corridors into Nigeria, Ghana, Kenya, Bangladesh, Pakistan, India, the Philippines, and Vietnam, which is part of why "just compare the fee" is such incomplete advice for users of any app in this space, ours included.

Curious how others building in this space have handled the licensing-per-corridor problem, would love to hear how you approached it if you've shipped anything similar.

The Real Reason Cross-Border Transfer Pricing Varies by Corridor

Belyfted — Wed, 15 Jul 2026 14:48:46 +0000

The Real Reason Cross-Border Transfer Pricing Varies by Corridor

TL;DR
The fee you see at checkout is rarely the real cost of an international transfer. The exchange rate spread against the mid-market rate usually is.

That spread is not just a margin decision. It is downstream of how a provider funds and settles a specific corridor: prefunded balances, correspondent banking chains, and settlement timing.

A provider that is competitive on a UK to Nigeria transfer can be mediocre on a UK to Vietnam one, because those are two different liquidity problems, not the same rail wearing a different flag.
Building across 11 corridors at Belyfted, we treat each one as its own pricing and liquidity problem, and use a rewards mechanic, Bonus Points, to lower the effective cost of frequent transfers, instead of trying to force every corridor's spread to the same number.

Everyone compares the wrong number
Ask someone how they picked a money transfer provider and they will usually say they compared the fee. It is the number every app puts front and centre: £2.99, zero fee, 1 percent. It is also, on its own, close to meaningless.
The bigger cost usually sits in the exchange rate. Every provider converts your money at a rate that includes a markup against the mid-market rate, the real rate you would find on a financial data platform. That markup rarely shows up as its own line item, and on a meaningful transfer it can dwarf the visible fee. The World Bank's Remittance Prices Worldwide database tracks this properly, total cost, fee plus rate markup, corridor by corridor, and it is a genuinely useful sanity check before sending anything.
The fee is a product decision. The spread is an infrastructure constraint

Here is the part that does not get discussed enough outside payments teams: the fee is largely a pricing and positioning choice. The spread mostly is not.
Cross-border payments researchers increasingly describe the space as a balance sheet problem before it is a messaging problem. A provider moving money into a corridor typically needs liquidity already sitting there, in a correspondent bank, a local payout partner, or a prefunded account, ahead of the transaction happening. That capital has to be positioned and maintained corridor by corridor, and it is not free to hold.

A recent BIS working paper on cross-border payment technologies walks through exactly this: settlement finality and liquidity risk management sit underneath every model, correspondent banking or otherwise.

In a high-volume corridor, a provider can net flows, forecast demand accurately, and keep that prefunded capital working hard. In a lower-volume corridor, the same capital sits idle more often, and the cost of holding it has to land somewhere. It usually lands in the spread, quietly, rather than in a fee anyone would notice.

This is also why zero-fee offers are not automatically the good deal they look like. A provider absorbing the visible fee has to recover the cost of that transaction somewhere, and the exchange rate is the easiest place to do it without anyone comparing two numbers side by side.

**
Why UK to Nigeria and UK to Vietnam are not the same engineering problem**
Treating cross-border payments as one product is a mistake that shows up in pricing fast. Each corridor has its own payout infrastructure (bank rails, mobile wallets, cash agents), its own regulatory requirements, and its own demand pattern.

Kenya is a good example of a corridor taken seriously at the infrastructure level: remittances are one of the country's top sources of foreign exchange, and the Central Bank of Kenya tracks and publishes diaspora remittance inflows every month as routine monetary data. Nigeria sits in similar territory by volume, which is part of why UK to Nigeria pricing tends to be sharp across providers, competition and netting opportunity both push spreads down.

Smaller UK-specific corridors do not get that same natural pressure. A corridor where the UK is a smaller sending market relative to, say, the US or Gulf states will not see the same volume-driven spread compression, even if the receiving country's total remittance market is large.

Pricing and payout infrastructure built around the biggest global corridors does not automatically carry over well to a smaller, UK-specific route.
The practical result: a provider that is genuinely competitive for UK to Nigeria can be mediocre for UK to Vietnam or UK to Tanzania. Not because it is being dishonest, but because it is solving a materially different liquidity problem in each one, and most providers do not price that difference transparently.

What this looks like from the building side

We build across 11 corridors at Belyfted (Nigeria, Ghana, Kenya, Bangladesh, Benin, Thailand, Tanzania, Indonesia, Uganda, the Philippines, and Vietnam), and the lesson that stuck with us is that a flat global spread strategy quietly punishes whichever corridors are smaller or newer, while a single cheapest-corridor headline rate hides how uneven the rest of the book actually is.
One lever we lean on instead of chasing an identical spread everywhere is Bonus Points: users earn points on every transaction, redeemable against future transaction fees, and a Referral Bonus when a referred contact completes a qualifying transfer. It does not solve the underlying liquidity economics of a given corridor by itself, but it does give frequent senders a way to bring their real cost down over time, rather than only rewarding whoever happens to catch the best headline rate on a single transaction.

The practical takeaway
If you are building or evaluating a cross-border payments product, the useful question is not "what is our spread", it is "what does our spread need to be, corridor by corridor, given how we fund and settle each one."

If you are sending money, the useful question is not "what is the fee", it is "what is the total cost against the mid-market rate, for this specific corridor." The World Bank's Remittance Prices Worldwide database will get you most of the way to answering that yourself, and checking a provider's FCA authorisation or, for Nigeria specifically, its listing on the Central Bank of Nigeria's International Money Transfer Operators list, takes a couple of minutes and is worth doing before sending anything meaningful.

What corridor-specific pricing quirks have you run into, building or using cross-border payment products. Curious what other builders in this space have seen.

Sources and further reading

World Bank, Remittance Prices Worldwide database
BIS Papers No. 167, Cross-border payment technologies: innovations and challenges
FCA, how to check if a firm is authorised
HMRC, money laundering supervision for money service businesses
Central Bank of Nigeria, International Money Transfer Operators list
Central Bank of Kenya, Diaspora Remittances

Disclaimer
This article is for general informational purposes only and reflects a general understanding of how cross-border payment pricing and liquidity typically work, not a technical specification of any single provider's systems. Corridor economics and regulatory requirements change over time. Always verify current rates, fees, and provider authorisation directly before making a transfer.

Belyfted Regulatory Information
Belyfted is registered by the CBN under IMTO and Financial Conduct Authority under the Payment Services Regulations 2017 (PSRs) (FRN 911399), Licensed and regulated by HMRC (MSB) XLML00000175194, Company number 11139735 United Kingdom.