Multi-currency is fintech’s favourite vanity metric. Founders often treat it as an essential badge of credibility, viewing it as a feature required simply to look complete alongside established players. Yet for the vast majority of programmes, multi-currency is not just unnecessary. It is completely irrelevant.
Before putting it on a roadmap, product teams must answer the question they usually skip:
Do your customers actually live multi-currency lives, or are you building operational complexity just to add a tick on a feature list?
The assumption is that they must. People travel more frequently. Businesses operate internationally. Workforces are increasingly mobile. If other providers allow customers to hold and spend multiple currencies, surely any credible new programme must do the same. But the presence of a feature elsewhere is not evidence that it belongs in your programme.
Multi-currency can be extremely valuable for people who genuinely live multi-currency lives. The problem is that most people do not.
Most People Live Their Lives in One Currency
The majority of people are paid in one currency, pay their bills in that currency, and conduct the overwhelming majority of their lives in it.
International spending is overwhelmingly temporary. People travel, attend a conference, or buy from an overseas website. They do not need to hold foreign balances to do that; they just need their card to work. Standard payment card schemes already handle FX conversions seamlessly, simply and fairly at the point of sale.
For most consumers, a clear and transparent FX arrangement is far more valuable than being forced to act as an amateur FX trader managing leftover balance friction. Forcing customers to decide when to convert funds, predict exchange rate movements, or manage leftover funds after a trip forces operational friction onto the end user.
There are customers for whom holding multiple currencies solves a genuine problem. Someone paid in dollars who also has outgoings in dollars may benefit greatly. So might an expatriate, an international contractor or someone regularly moving between countries.
But that does not mean the same capability is necessary for a mass-market programme whose customers overwhelmingly earn and spend in pounds.
One Feature Can Create a Mountain of Complexity
The customer need is only one part of the equation. Multi-currency may appear to be a single feature on a product roadmap, but delivering it creates an entire layer of technical and operational complexity.
Behind a single roadmap item lies a heavy operational burden. You must pre-fund foreign balances, manage daily liquidity, and handle complex FX reconciliation. Then the edge cases hit. If a customer spends $120 with $100 and £500 in their account, what happens? Do you decline the transaction, auto-convert other currency balances, or prompt for approval? Every decision introduces a new point of friction, a potential for a failed transaction, or customer dissatisfaction.
The questions become more complicated if the customer also holds euros. Which balance should be used first? What happens if the programme converts pounds when using euros would have produced a better result for the customer? Even if the programme acts entirely within its terms and regulatory obligations, the customer may still believe the wrong decision was made.
Every additional option creates another point at which the experience can become confusing, a transaction can fail or introduces a potential point of failure. That complexity might be justified when the feature solves an important problem for a valuable customer group. It is much harder to justify when it has been included primarily because competitors offer it.
Prove the Need Before Building the Feature
Omitting multi-currency at launch is not a compromise. It does not mean rejecting it permanently. It means refusing to introduce complexity before its true value to end customers has been established.
The first step is to understand the people the programme is being built for. Do they regularly receive income in different currencies? Do they maintain financial commitments in more than one country? Are they moving between currencies frequently enough for separate balances to make their lives easier?
Once the programme is operating, transaction data can help identify patterns of international spending. But even that is not proof of demand.
A customer spending money abroad may simply want their existing card to work without an excessive or unexpected charge. They may have no interest in buying and managing foreign currency themselves. The data should tell you where to investigate. Conversations with customers should then reveal the problem they are actually trying to solve.
If a meaningful need exists, multi-currency can be introduced for the customers who will value it. The organisation can then assess whether the likely demand, commercial return and competitive opportunity justify the additional cost and complexity.
That is a much stronger basis for investment than assuming the feature is necessary because the rest of the market appears to have adopted it.
Relevance is Not Measured By the Number of Features
Multi-currency is an excellent capability for the right programme, serving the right customers. But innovation is not about making a product capable of doing everything. It is about understanding which capabilities will make the greatest difference to the people it is intended to serve.
Sometimes the most important decision is not what to add, but what to leave out. The best card programme is not necessarily the one with the longest list of features. It is the one that does what its customers genuinely need, as simply, reliably and effectively as possible.