Priya runs an online shop from Mumbai, selling handmade homewares to customers in the United States, the United Kingdom, and the EU. Her customers pay in their local currency. Her processor converts everything to Indian rupees, deposits the result into her bank account two days later, and takes a margin on every conversion that does not appear on the customer's receipt or her own dashboard.
Half of her FX cost is invisible — buried in the spread between the mid-market rate and the rate she receives. The other half is timing: by the time the money reaches her account, the rate she sees has already moved, and there is no record of the rate she was actually charged. She has no way to compare what she paid for the conversion to what she would have paid if she had moved the money herself.
What multi-merchant-account complexity actually costs
Cross-border merchants typically have one of two setups, and both impose costs the merchant did not choose.
The first setup is multiple merchant accounts. Some businesses set up a Stripe-US account, a Stripe-EU account, and a Stripe-UK account — each with its own contract, its own settlement bank account, its own compliance review, its own dashboard. The merchant accepts payments in each region's local currency, settles into a regional bank account, and then either operates regional banking infrastructure or pays a separate FX cost to consolidate funds back to their home market. The operational tax of running this is real: more accounts to reconcile, more compliance to maintain, more banking relationships to manage.
The second setup is single-account multi-currency. The merchant accepts payments in any currency through one processor account, and the processor converts everything to a single home currency at settlement. The operational complexity is lower, but the FX cost is higher and the merchant has no control over when the conversion happens or what rate it is converted at. Each sale carries an FX margin that the merchant pays without ever choosing to.
Why the FX margin is invisible
The exchange rate offered to a merchant on a cross-border card transaction is rarely the mid-market rate. It is the mid-market rate plus a margin, and the margin is extracted in the spread rather than displayed as a fee. A merchant whose dashboard shows "£100 received" on a $130 sale has no easy way to verify what mid-market rate would have applied at the moment of the sale, what rate the processor used, and how much margin was extracted in the gap.
This is not a hidden fee in the regulatory sense — most processors disclose that they charge an FX margin somewhere in their terms. But it is invisible in practice, because the merchant cannot see the two rates side by side. The cost is real, and on cross-border-heavy merchants it is large enough to materially affect margin calculations. A merchant with 30% of revenue from non-home-currency customers, paying a 2% FX margin on those transactions, gives up 0.6% of total revenue to FX alone — on top of the percentage card-processing fee.
Retail FX margins on cross-border transfers commonly range from 0.5% to 2% at digital fintechs to 3% to 5% at traditional banks, and can reach 6% on exotic corridors.
— Industry analyses of FX markup practice, 2025
How Spondula's gateway handles cross-border differently
Spondula's payment gateway is one network, used the same way regardless of where the customer is. A customer in the US, the UK, the EU, or any market with network coverage sends to the same merchant Shandle. The merchant does not need a separate Stripe-US, Stripe-EU, or Stripe-UK account. The same gateway, the same dashboard, the same settlement speed applies across every market the business sells into.
The merchant chooses what they hold. A US-headquartered merchant might hold their balance in USD-S; a UK merchant in GBP-S; a European merchant in EUR-S. A merchant with cross-border revenue can hold all three simultaneously, in the same wallet, and convert between them on their own schedule rather than at the moment of each sale. The forced-conversion model does not apply on this rail — the merchant chooses the timing, sees the rate before confirming, and is not paying an invisible margin extracted at the moment of customer payment.
Settlement is in seconds across every market, not just within a region. A customer paying from Singapore at 11pm local time settles to the merchant's wallet at 11pm local time — there is no waiting for a bank in either region to open, no T+2 wait for the cross-border leg, and no separate cut-off windows for international transactions versus domestic ones.
What it means for the cross-border merchant
The practical effect is that a cross-border merchant on Spondula's gateway operates as a single business, not as three regional merchants stitched together. The dashboard shows one balance, denominated in the tokens the merchant holds. The compliance is one relationship. The settlement timing is one expectation — instant, every time, in every market.
FX is no longer a cost extracted at the moment of every sale. It is a decision the merchant makes when they want to convert — at a rate they can see, on a schedule they choose, with the option to hold value in the source currency until the rate moves favourably. The merchant is not buying FX in 800 small transactions a month; they are choosing when to convert larger lumps, with full visibility into what they are paying.
For Priya, this means she would hold her US sales in USD-S, her UK sales in GBP-S, and her EU sales in EUR-S, until she chose to convert any of them — into INR, into another currency, or into GOLD-S as a holding layer. The customer paying her does not need to understand any of this; the customer just pays, and the payment lands in seconds.
Cross-border was the niche the card-processing model was supposed to solve. In practice, it is the case it handles least well — and the one a network-settled gateway handles most naturally.
Spondula's gateway is open for launch partners — online retailers selling internationally, marketplaces with sellers across regions, subscription services with global subscribers, and any business whose customer base does not fit inside one country's banking infrastructure. The waitlist is the starting point.
Frequently asked questions
Do I need separate merchant accounts for each country I sell into?
No. The same Spondula gateway accepts payments from customers in any market with network coverage. There is no need to maintain regional Stripe-US, Stripe-EU, or Stripe-UK accounts in parallel. One Shandle, one dashboard, one settlement model.
What currencies can I hold as a merchant on Spondula?
Merchants can hold value in USD-S, GBP-S, and EUR-S — the everyday network tokens — as well as in GOLD-S as a store-of-value layer. The same wallet holds all of them simultaneously; the merchant chooses what to convert and when, rather than having a forced conversion at every sale.
What FX rate applies when I do convert?
Conversions on the Spondula network show the rate before the merchant confirms — not as a margin extracted invisibly in a settlement statement. The merchant sees what they are paying for the conversion, decides whether to proceed, and the conversion happens on the network at the rate displayed.
How does this compare to card processors that offer multi-currency settlement?
Some card processors offer multi-currency settlement options, but they typically still operate on T+2 settlement timing and still extract an FX margin on conversions. The Spondula gateway differs on both: settlement is instant rather than T+2, and the merchant controls the timing and rate of any conversion rather than having it bundled into each transaction.
What about taxes and compliance across multiple countries?
Cross-border tax compliance is the merchant's responsibility regardless of payment infrastructure — VAT, sales tax, import duties, and similar obligations exist independently of how payments are routed. Spondula's gateway provides the payment layer; tax compliance still requires the merchant's own accounting setup or local advisor in the markets they serve.
Spondula is a global payments network. It is not a bank, exchange, investment platform, or broker. Availability, pricing, and Operator coverage vary by country. Bitcoin rewards depend on real network activity and are not guaranteed. See our terms and conditions for full details.
