Currencycloud: The Payment Company Behind Someone Else's App

Currencycloud sells the awkward middle

Imagine a payroll app that wants customers to hold dollars, convert them into euros and pay contractors in Poland. Building the interface is only the visible work. The company also needs regulated accounts, beneficiary validation, FX execution, sanctions controls and access to payment systems or banks. Currencycloud sells much of that middle as a service.

The API menu is fairly concrete. A client can open a beneficiary record, show a balance, quote the conversion and finally release the payment. Virtual or named accounts help identify incoming funds for individual customers. Webhooks and status records feed the result back into the client's own screen. Teams that prefer a dashboard can do the same work in Currencycloud Direct.

Industry shorthand calls this embedded finance, a woolly name for somebody else's financial functions inside your product. The end customer may mainly recognise the payroll, wealth or travel brand. Legal disclosures should still identify who issues e-money or provides the payment. In Britain, The Currency Cloud Limited is an FCA-authorised electronic money institution, not a bank account quietly wearing somebody else's colours.

One client screen can hide several payment routes

Currencycloud currently advertises 180-plus-country reach, stitched together from local payments and Swift. The route changes by currency. For zloty, that can mean Poland's Elixir system; choose priority delivery and Swift enters the picture. Cut-off time, maximum value and required data differ between those options.

Local payout generally means the recipient receives a domestic bank payment from an account or partner already connected in that market. Swift reaches farther, although an intermediary bank may send its own bill. Currencycloud's payment overview warns that those institutions can take handling fees. An API removes manual work; it cannot repeal correspondent banking.

Coverage has edges. Currencycloud labels several currencies, including Indian rupees and Philippine pesos, as restricted for direct funding. Some local USD services are unavailable for clients or beneficiaries linked to specified countries. An industry buyer must inspect the actual corridor matrix rather than place 180-country reach into every sales slide.

The fintech still owns the customer problem

The client decides its retail price and customer experience. Nothing stops it from putting a fee or FX margin on top of Currencycloud's wholesale terms. This is why two apps using related infrastructure can show different recipient amounts. Shared plumbing does not produce shared pricing, any more than two restaurants using the same card terminal produce the same lunch bill.

Customer-checking responsibilities vary. Currencycloud can support compliance and payment requirements, but the programme design decides which company checks the end user and who handles suspicious activity. Support follows a similar split. The customer complains to the app. Its team may then need Currencycloud or a payout bank to work out what happened.

Reconciliation deserves equal attention. A payment company needs identifiers that join a bank credit, conversion, fee and beneficiary payout back to one customer record. Virtual accounts help because an incoming account number can identify the owner without somebody reading a reference field. The awkward exceptions still need operations staff and auditable corrections.

Treasury is not abolished either. Somebody must fund balances, manage currency exposure and plan for weekends. Some clients put cash on the platform first. A smaller group may be allowed to owe the platform within an agreed limit. Good API documentation can make the instruction immediate while the commercial arrangement decides whether money is available to honour it.

Visa paid for the infrastructure, not a universal rail

Currencycloud has belonged to Visa since the deal closed in December 2021. The strategic fit was broader than card payments: Currencycloud added wallets, virtual account management and bank-transfer FX to Visa's network ambitions. It continues to operate a platform for banks and technology companies rather than turning every payout into a Visa card transaction.

Competitors package the stack differently. Wise Platform exposes parts of Wise's own payment network to banks and enterprises. Nium markets global payouts and local collections. Thunes emphasises a direct network reaching bank accounts and mobile wallets. Comparing logo counts is unhelpful unless the required currency, entity and payout method match.

For a business buyer, I would ask for a live route matrix, named regulated entities and a failed-payment workflow. Then I would price local and Swift delivery separately and test the reconciliation data. Infrastructure earns its fee when the awkward cases are legible, not when the happy-path diagram has the fewest boxes.