The Turkish payment landscape, and why stablecoins took hold
Most everyday money in Turkey still moves over local rails — domestic bank transfers and cards work, and for a store selling lira to lira there is often no reason to reach for anything else. What has changed is the unit of account. When prices climb fast and the lira loses value against the dollar, a figure quoted today does not mean the same thing a month from now, and both sides of a sale start thinking in dollars even when they settle in something else.
That is the widely reported pattern behind Turkey's heavy stablecoin use: dollar-pegged tokens like USDT have become a practical way to hold and move value without watching it erode. For a business, the appeal is the same as for an individual — a USDT balance is a dollar balance, and a USDT invoice owes a dollar amount, regardless of where the lira sits that day.
The friction sharpens at the borders of the local system. A customer paying from outside Turkey, a counterparty who holds dollars on-chain rather than in a bank, a vertical that card acquirers treat cautiously — these are the cases where local cards and transfers do the wrong job or no job. That is the gap a crypto rail fills, and it is why Turkish merchants commonly price in USD but want to settle in stablecoins.
Which assets fit a dollar-priced business
For a business that thinks in dollars, the asset that fits best is the one whose value does not move between checkout and confirmation. Dollar-pegged stablecoins — USDT first, USDC alongside it — are the common case in Turkey: 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 USD-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. In Turkey, Tron-based USDT is especially common because its transfer cost is low and predictable — but a merchant does not have to pick one rail. You enable the networks your customers actually use and let each customer pay on the chain they already hold funds on. Bitcoin remains the option 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, a mixed inflow does not have to stay scattered. Balance conversion consolidates what arrives — USDT on one chain, USDC on another, a little BTC or SOL — into the asset you want to hold as your reserve, automatically on a policy you set or manually when you decide to rebalance. A dollar-priced business that wants to sit mostly in one stablecoin can do that without managing each balance by hand.
- Price in USD; 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 — Tron USDT is the everyday rail in Turkey; USDC on Ethereum, Base, or Solana.
- Bitcoin for customers who pay in BTC, same fiat-anchored invoice and confirmation rules.
- Balance conversion consolidates a mixed inflow into the reserve stablecoin you choose to hold.
Verticals that reach for this in Turkey
The businesses that pull hardest toward a crypto rail in Turkey are the ones where dollars and cross-border flow are already the norm. None of these are exotic — they are ordinary online businesses hitting the inflation, currency, or acquirer-risk edges described above.
FX and trading sit at the centre of it. Brokers, prop firms, and trading platforms take deposits from clients who already hold dollars on-chain and want their balance denominated in dollars rather than lira; paying winnings or refunds back out in the same stablecoin closes the loop. Cross-border commerce is the other broad case: a Turkish store or service selling beyond the country wants to be paid in a stable unit by customers whose cards decline or carry conversion they notice, and exporters and freelancers want to collect from foreign clients without the drag of traditional remittance. Digital-goods and SaaS sellers want final settlement for something delivered instantly that cannot be shipped back when a card later reverses.
- FX brokers, prop firms, and trading platforms taking client deposits in dollar stablecoins and paying winnings or refunds back out the same way.
- Cross-border e-commerce and services selling beyond Turkey, where international card declines and conversion cost real conversions.
- Exporters, agencies, and freelancers collecting from foreign clients without slow or expensive remittance rails.
- Digital goods, software, top-ups, and subscriptions — instant, final settlement for things with nothing to ship back if a card payment later reverses.
- Higher-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 Turkish business already runs; it does not replace your accounting or the local flows that work. You create an invoice anchored to your USD 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 trading platform crediting deposits, a billing service, a system that pays another system — 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, which suits a broker assigning a deposit address per client. 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 platform settling many traders or affiliates at once 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 USD 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 traders or affiliates 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": "100.00",
"fiat_currency": "USD",
"idempotency_key": "order-TR-50817"
}'
# The USD 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 Turkish 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 Turkey 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 Turkish 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 Turkey and serves customers at home and abroad, the relevant question is which networks and stablecoins 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.