The Spanish payment landscape, and where it strains
Spain has a large, growing e-commerce market and an economy where a real share of spending comes from outside the country — through inbound tourism and through stores that sell well beyond Spain's borders. Domestic euro payments are well served: SEPA moves money between Spanish and EU accounts cheaply and quickly, and a finance team rarely needs anything else for a local sale paid by a local customer.
The strain appears at the edges of that domestic picture, and for a lot of Spanish businesses those edges are where the money is. A visiting customer paying on a card issued in another country is more likely to see a decline, a cross-border fee, or a currency conversion they did not expect. A store selling across the EU and across the Atlantic faces the same friction at scale, plus chargebacks that can land weeks after the goods have shipped. SEPA does not help here — it is a euro rail, and it does the wrong job, or no job, the moment the counterparty sits outside the SEPA area or holds a different currency.
There is also a segment problem common to many markets: some perfectly legitimate verticals find card acquirers cautious, regardless of the business's own controls. For those merchants the question is less 'is SEPA cheap' and more 'can I get paid at all without depending on an acquirer relationship I might lose.' That combination — tourism-driven foreign-card friction, cross-border export reach, and acquirer-shy segments — is why Spanish merchants commonly price in EUR but want to settle in stablecoins.
Which assets fit a euro-priced business
For a business that thinks in euros, the asset that fits best is the one whose value does not move between checkout and confirmation. Dollar-pegged stablecoins — USDT and USDC — are the common case: the customer pays a stable amount and the merchant receives a stable amount, with no exposure to a swinging market in the minutes a payment takes to confirm. halfin anchors each invoice to your fiat figure and locks the quote when the invoice activates, so a EUR-priced order owes a fixed crypto amount even if the asset's price drifts while the customer is paying.
Where the customer holds those stablecoins decides the network. USDT settles on Tron, Ethereum, or Solana; USDC on Ethereum, Base, or Solana. A Spanish merchant does not have to pick one — you enable the networks your customers actually use, and a visitor paying from a TRC-20 USDT wallet and a domestic shopper paying USDC on Base can both settle the same invoice. Bitcoin stays available for customers who prefer to pay in BTC, with the same fiat-anchored invoice and the same reorg-aware crediting before a payment counts as settled.
On your side, the spread of incoming assets does not have to stay scattered. Balance conversion consolidates what arrives — BTC, SOL, a mix of stablecoins — into the asset you want to hold as your reserve, automatically on a policy you set or manually when you decide to rebalance. A euro-priced business that would rather sit mostly in a dollar stablecoin can do that without managing each balance by hand.
- Price in EUR; the invoice locks a fixed crypto amount at activation, so the customer is not exposed to price movement mid-payment.
- USDT on Tron, Ethereum, or Solana; USDC on Ethereum, Base, or Solana — enable what your customers actually hold.
- Bitcoin for customers who pay in BTC, same fiat-anchored invoice and confirmation rules.
- Balance conversion consolidates a mixed inflow into the reserve asset you choose to hold.
Verticals that reach for this in Spain
The patterns that pull Spanish businesses toward a crypto rail are the ones where the existing system loses customers at the border or leaves a segment underserved. None of these are exotic — they are ordinary businesses hitting the foreign-card, cross-border, or acquirer-risk edges described above.
Tourism-facing commerce is a distinctively Spanish case: hospitality, travel services, and stores in visitor-heavy areas take a lot of payments from foreign-issued cards, where declines and cross-border fees cost real conversions. Online stores and marketplaces are the broadest case overall — a Spanish store selling across the EU and to Latin American customers wants to be paid without losing the sale to a declined international card, and a marketplace wants to settle sellers across several countries in one run. SaaS and digital-goods sellers want final settlement for something delivered instantly that cannot be shipped back when a card later reverses.
- Tourism and hospitality businesses taking payments from foreign-issued cards, where international decline rates and cross-border fees eat into otherwise-made sales.
- Online stores and marketplaces selling across the EU and to Latin America, where foreign-card friction and chargebacks cost conversions on already-shipped goods.
- SaaS and subscription businesses billing customers in and outside the EU, where machine-to-machine settlement moves value without a human-facing checkout in the loop.
- Digital goods, software, top-ups, and licences — instant, final settlement for things with nothing to ship back if a card payment later reverses.
- High-risk and underserved verticals that card acquirers treat cautiously but that still need a reliable way to get paid.
How halfin fits the existing setup
halfin sits alongside what a Spanish business already runs; it does not replace the euro accounting or the SEPA flows that work. You create an invoice anchored to your EUR price, redirect the customer to the hosted checkout page — which handles the wallet, the network choice, the QR code, and live status — and wait for one HMAC-signed webhook before you treat the order as paid. The on-chain detail stays on halfin's side; your order system keeps its existing shape.
For automated commerce — a subscription platform, a booking system, a service that bills another service — machine-to-machine settlement moves value programmatically without a checkout page in the loop. Static deposit addresses give you a persistent receive address when you would rather hand out one address than mint an invoice each time. On the outbound side, single payouts cover a one-off send with operator review, and mass payouts batch many destinations into one idempotent run — submitting the same batch twice does not pay twice — which is what a marketplace settling sellers across borders needs.
Treat the customer's redirect back to your success page as cosmetic and the signed webhook as authoritative: a customer can pay and close the tab before the redirect fires, but the webhook still arrives. Always verify the signature before acting on it. If you ever need to return funds, refunds run as a first-class flow against the original invoice rather than an ad-hoc manual send.
- Create an invoice anchored to your EUR price; the rate locks at activation and expiry is enforced.
- Hosted checkout handles wallet, network, QR, and live status — no on-chain code on your side.
- A signed webhook is the source of truth for marking an order paid; verify the HMAC first.
- Mass payouts settle many cross-border destinations in one idempotent batch; refunds run against the original invoice.
curl -X POST https://api.thehalfin.com/api/v1/invoices \
-H "X-API-Key: $HALFIN_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"amount_fiat": "75.00",
"fiat_currency": "EUR",
"idempotency_key": "order-ES-50817"
}'
# The EUR amount anchors the order; the customer settles in the
# crypto asset they pick on the hosted checkout page returned in
# the response. Redirect the customer there, then verify the
# signed invoice webhook before releasing the order. See the full
# request and response schema at docs.thehalfin.com.Compliance and availability — a rail, not a licence
A Spanish business taking crypto still owns its own obligations. halfin is payment infrastructure: it collects payments, executes payouts, keeps payment records, and exposes status through dashboard data and signed webhooks. It does not take over the merchant's customer onboarding, its bookkeeping, its tax handling, or any approval the goods or services themselves require under local rules. Nothing on this page is legal, tax, or financial advice, and halfin makes no claim to be registered or licensed in Spain or anywhere else.
Onboarding to halfin involves KYB — verifying the business behind the merchant account — and the platform operates with AML awareness as a process. The travel rule, which concerns information that travels with certain transfers, is a concept to understand as you design flows, not a certificate halfin issues. The practical pattern for a Spanish merchant is to keep your own customer checks, your own counterparty and wallet screening, and your own record of which order each invoice and payout belongs to; halfin gives you the payment primitives and the audit trail, and you keep the decisions about who you serve and what you sell.
Availability is subject to jurisdiction and sanctions screening, and some places are out of scope regardless of demand — see the restricted-countries note for where halfin cannot operate. If your business is based in Spain and serves customers across the EU, Latin America, and the stream of visitors that tourism brings, the relevant question is which networks and assets your customers actually use, and how you want incoming balances to settle.
- KYB onboarding verifies the business behind the merchant account.
- AML awareness is a process, not a status halfin grants — and halfin is not 'licensed' in any country.
- Keep your own customer checks, screening, and per-order records as the source of truth.
- Availability is subject to jurisdiction and sanctions screening; see the restricted-countries note.