If your business pays a supplier in Spain, invoices clients in Singapore or settles a contractor in Poland, you have probably watched a payment leave your account on a Tuesday and arrive on a Friday, minus a fee nobody can fully explain. Most of that plumbing runs on SWIFT. A growing share is being pitched as RippleNet. The two are often framed as rivals, but they do different jobs, and understanding which one sits behind your payment helps you ask sharper questions of your bank or payment provider.
Two networks, two different jobs
SWIFT is a messaging cooperative owned by its member banks. It does not move money. It carries payment instructions between institutions — in effect, "pay this amount to this account". The funds themselves travel along correspondent banking relationships: your bank holds an account with a larger bank, that bank holds an account with another, and eventually a bank in the recipient's country credits the beneficiary. Every hop is another opportunity for a fee, a delay or a compliance query.
RippleNet is Ripple's network for payment providers and financial institutions. Members settle with each other directly rather than through a chain of intermediaries. There are two mechanisms worth knowing. The first is bilateral credit between partners who have agreed to fund each other. The second is On-Demand Liquidity, which uses XRP as a bridge between two currencies so a provider does not have to hold idle balances in every currency it supports.
Settlement on the XRP Ledger is quick and the network fee is small. That is only the ledger leg, though. Converting sterling into XRP at one end and out of XRP into the destination currency at the other still depends on local partners, liquidity and their cut-off times.
Settlement speed: what "instant" really means
SWIFT has improved markedly with its gpi service, which attaches a reference number to each payment and lets banks track it. Many payments are credited within minutes. Credited, however, is not the same as available. A payment can clear one bank's systems and then sit with the beneficiary bank until its own checks are done, its cut-off passes, or the next business day begins in that time zone.
RippleNet's proposition is end-to-end speed, because fewer parties are involved and settlement happens on a public ledger rather than through batch processing. In well-supported corridors with good payout partners, payments can complete in minutes. In thinner corridors — less common currency pairs, smaller markets, weekends and local holidays — you will meet the same frictions as traditional rails.
Ask for the median, not the marketing
When a provider claims "seconds", ask for the median end-to-end time for your specific corridor and currency pair over the last quarter. That single question separates a real capability from a network diagram.
Where the cost actually sits
Banks rarely quote one price. The cost of an international payment arrives in pieces, and the largest piece is usually invisible at the point of sending.
- The FX margin. The gap between the mid-market rate and the rate you are given. Often the biggest cost by far.
- The provider's transfer fee. A flat charge, sometimes tiered by amount.
- Intermediary deductions. Correspondent banks in the chain may take a slice before the money reaches the beneficiary.
- Beneficiary bank charges. A receiving fee that lands on your supplier, who may pass it back to you.
- Pre-funding and float. Money parked in overseas accounts to make payments work is capital not doing anything else.
RippleNet's structural advantage is fewer hops, which means fewer deductions and less trapped capital. That is a genuine benefit, not an automatic saving. The provider still sets an FX margin, and that margin rarely disappears just because the rails underneath changed.
Transparency: can you see where the money is?
SWIFT gpi gives each payment a unique end-to-end reference, so participating banks can trace it and answer "where is my payment?" with something better than a shrug. It is a real improvement, and most large banks now support it. What it cannot fix is the beneficiary bank's own handling.
RippleNet is designed to pass status information back along the chain, and some providers use it to quote a rate, a fee and an estimated arrival before you confirm. That pre-trade quote is the feature most worth testing. If a provider cannot tell you, before you press send, the exact amount your supplier will receive and roughly when, the technology underneath is not doing much for your business.
How a UK SME should compare providers
- Pick one corridor that hurts most — the payment you make most often, or the one that causes the most chasing.
- Get written quotes from three providers: your bank, a specialist payment institution and a fintech that uses RippleNet rails.
- Compare the all-in cost: the recipient's received amount for the same sterling value, not the headline fee.
- Test with a small live payment before moving volume. Ask how long it took, and how long the money sat before it was spendable.
- Check who the payout partner is in the destination country, and what happens when a payment fails or is returned.
- Review quarterly. FX margins drift, and a provider that was competitive last year may not be now.
Compliance, tax and the details people skip
If a payment touches cryptoassets at any point, your accounting treatment and record-keeping need to reflect that, and the regulatory position of tokens differs between jurisdictions. Providers handling client money should hold the appropriate permissions — check the Financial Conduct Authority's register, and ask about safeguarding arrangements for funds in transit. Expect anti-money-laundering checks on both sides, and budget time for them rather than treating them as an obstacle. For anything specific to your circumstances, take advice from an accountant or solicitor who knows your sector.
Choosing on evidence rather than branding
SWIFT remains the default for large, complex or unusually structured payments, and its reach is hard to match. RippleNet-based providers tend to win on smaller, repeatable payments in corridors where speed and visibility matter more than universal coverage. The sensible approach is not to pick a network but to pick a provider you can hold to a number — the amount your recipient actually gets, and when. Test it, measure it, and revisit it as your payment mix changes.
Photo: Ralphs_Fotos / Pixabay
