Multi-currency settlement — one wallet for every market you sell in

Fifteen countries. One wallet. No FX queue.

A business that sells to customers in Europe, North America, and Southeast Asia operates, in the traditional system, across three different sets of payment rails, three different settlement timelines, and three different FX conversion moments — each one happening at a rate set by someone else, at a time chosen by a bank's batch-processing schedule rather than by the business. The money arrives. It just arrives slowly, at a cost, and never all at once.

That is not a problem unique to large multinational companies. It applies to any online business with an international customer base, any service firm that invoices clients across time zones, and any B2B operation that pays suppliers in one currency while collecting revenue in another. The traditional payment stack was not built for cross-border as a default. It was built for one country, extended to others as an afterthought, and the seams show in the fees and the timing.

What multi-currency settlement actually means

Settlement is the moment a payment becomes real — when the money crosses from a customer's account into a merchant's. In a single-currency domestic context, settlement is straightforward: the same currency moves between two accounts at the same bank or on the same national rail, and the timing is predictable.

In a multi-currency context, settlement involves an FX conversion at some point in the chain — either at the sending end, the receiving end, or inside the correspondent-bank network in between. Each conversion introduces a rate, a margin, and a timing variable. A business that accepts EUR from a European customer and GBP from a UK customer and USD from a US customer is dealing with three different conversion events, each with its own cost and its own moment of execution.

The standard response to this complexity is to choose one currency to settle into — usually the currency of the business's home market — and accept that every other currency gets converted at whatever rate the processor applies on the day. The business takes the conversion risk and pays the conversion cost, and the ledger is simpler for it.

Multi-currency settlement takes a different approach: keep the currencies separate, let the business decide when and whether to convert, and reduce the forced-conversion steps that the traditional stack imposes.

How Spondula handles it

The Spondula business wallet holds multiple tokens simultaneously. USD-S, GBP-S, and EUR-S can all sit in the same wallet at the same time, each balance visible separately, each available for outgoing payments or held until the business chooses to move it.

When a customer pays through Spondula — via a payment link, a QR code, or a checkout integration — the payment arrives as the token the customer sent. A European customer paying EUR-S adds to the EUR-S balance. A US customer paying USD-S adds to the USD-S balance. The merchant receives what was sent, without a mandatory conversion at the point of receipt.

Settlement is instant on the Spondula network. The payment arrives in the wallet the moment the customer confirms it — not at the end of a processing day, not after a correspondent-bank overnight run, not on the next business day after a weekend. For a business that monitors cash flow closely, the difference between seeing a payment land in real time and seeing it arrive forty-eight hours later is not trivial.