Emirates crypto payments are live — but they're a closed loop

What happened: Emirates crypto payments went live on July 28, 2026

Emirates began accepting cryptocurrency for flight bookings on July 28, 2026, becoming the first major Gulf carrier to do so. The option appears at checkout on emirates.com and inside the Emirates app, powered by Crypto.com Pay.

The mechanics are straightforward. On mobile, a traveller booking in the Emirates app is handed off to the Crypto.com app to approve the payment from their wallet, then returned to Emirates for the booking confirmation and e-ticket. On desktop, the checkout displays a QR code; the customer scans it, approves in the app, and Emirates issues the ticket after approval.

Three details matter more than the headline:

• Eligibility. The option is open to eligible UAE residents with an active Crypto.com account, on bookings priced and settled in AED.
• Emirates never holds crypto. The airline settles in dirhams; the provider handles the conversion. Emirates carries no digital-asset price exposure between booking and settlement.
• It runs on a licence, in one jurisdiction. The integration operates through Foris DAX Middle East FZE, which holds a Stored Value Facilities licence from the Central Bank of the UAE granted in May 2026 — the same licence that lets UAE residents pay some government fees with digital assets. It fits squarely inside the Dubai Cashless Strategy under the D33 agenda.

Adnan Kazim, Emirates' Deputy President and Chief Commercial Officer, framed the launch around traveller expectations — a younger, digitally fluent generation that expects airlines to keep pace. Crypto.com's President and COO, Eric Anziani, called it a milestone for the company's Pay product and a nod to the UAE's regulatory posture.

Worth noting what wasn't published: which digital assets are accepted, what the payment costs, how the exchange rate is struck, and what happens to a failed, delayed or refunded booking. For a merchant evaluating the model, those four gaps are the entire commercial question.

This didn't happen quickly, either. The partnership started as a memorandum of understanding signed in July 2025. Going live took a year, a central-bank licence, and one of the largest airline brands in the world. It also isn't the UAE's first: Air Arabia began accepting the dirham-backed AE Coin stablecoin for bookings back in May 2025.

Two days later: Korea's KSNET signed a Solana Pay and x402 pilot

On July 30, 2026, in Seoul, the payments infrastructure company KSNET signed a memorandum of understanding with the Solana Foundation. KSNET connects 330,000+ Korean merchants, processes roughly 130 million transactions a month and around $4 billion in monthly volume.

The MOU covers two proof-of-concept projects, in sequence: a Solana Pay integration tuned to the domestic Korean payment environment, and an AI payment model based on x402 — the open HTTP standard that lets software agents pay per request. KSNET was explicit that the goal isn't to replace existing rails but to slot blockchain payments into a merchant network it has spent 26 years building, with AML controls and settlement continuing through the won system.

Read the two announcements together and the pattern is hard to miss. In the same week, crypto acceptance arrived at a flagship airline and was agreed to be piloted across a third of a million merchants. Both are genuine validation. Neither is something a normal business can copy.

The pattern: 2026's acceptance headlines are distribution deals, not open acceptance

Strip the branding from both stories and the same architecture appears. A large merchant (or a merchant network) signs with a licensed intermediary. The intermediary holds a wallet on the buyer's side, converts on the merchant's side, and settles fiat. The customer pays "in crypto" only in the sense that their balance at that company goes down.

That design has one consequence that decides whether it's useful to you: the customer has to have an account with your provider. Not a wallet — an account, with KYC, in a supported country, funded with a supported asset.

So the addressable buyer set for Emirates crypto payments isn't "people who hold crypto." It's the intersection of three sets: customers of one provider, and residents of one country, and holders of whichever assets that provider supports for this flow. A traveller in Bogotá or Buenos Aires holding USDT in a self-custody wallet — precisely the person who books long-haul flights and has a hard time paying for them with a local card — is outside that intersection by design.

For Emirates, that's a rational trade. The airline wanted dirhams in its books, a licensed counterparty, and no price exposure. It has the scale to negotiate terms and the brand to make a year-long integration worth it.

For everyone else, the same architecture arrives without the negotiating power.

What a closed loop actually costs a smaller merchant

If you run a hotel, a tour desk, a clinic, an agency or an online store, waiting for a closed-loop deal means inheriting someone else's decisions on every variable that matters:

• Their coin list. You accept what the intermediary supports. Real-world stablecoin commerce is still dominated by USDT — roughly $95B versus USDC's $14B in first-half 2026 by Dune's measurement — so a flow that quietly supports only one coin loses the coin your customers actually hold.
• Their countries. Acceptance stops where the licence stops. Cross-border customers, who are the whole reason many merchants want crypto in the first place, are the first ones excluded.
• Their custody. Between your customer's payment and your money there is now a third-party balance. Balances have terms, and terms change: European businesses spent July watching a neobank stop USDT deposits and schedule an automatic conversion of every remaining balance — a lesson we covered in the USDT delisting in Europe.
• Their timeline. Emirates' MOU-to-launch cycle took twelve months. KSNET's is still a proof of concept with no announced date. If your plan for taking crypto is "when my processor adds it," your plan has no date on it.

Meanwhile the demand isn't hypothetical. Inbound tourism to the Gulf, LATAM freelancers paid in stablecoins by overseas clients, importers settling with suppliers, patients travelling for treatment — these customers already hold the money. What they lack is somewhere to spend it that doesn't require signing up for another financial institution first.

Why intermediated rails fail the customers you most want

The structural cause is easy to state. A closed loop needs a licensed custodian in the middle because it promises the merchant fiat. To convert crypto into dirhams (or won, or euros) and settle it, someone must be regulated to hold customer funds, run KYC, and take FX risk. That obligation generates every restriction downstream: a licence per jurisdiction, an approved-asset list, an account requirement on the buyer, and a balance parked with a third party between the payer and the payee.

It's the acquirer model with a different asset class. The settlement lag is shorter and the chargeback risk is gone, but the shape is the same: your money passes through a company that isn't you, under terms it sets and can revise.

On-chain payments don't inherently require any of that. A public blockchain transfer is a direct transaction between two wallets that reaches final settlement in seconds — around 0.4 seconds on Solana, about 2 seconds on Base and Polygon. There's no intermediary because there's nothing to intermediate. The only reason a middleman exists in the closed-loop model is the fiat promise at the end.

Drop the fiat promise and the entire restriction stack falls away with it.

The open alternative: any wallet, straight to a wallet you control

Payzum is a non-custodial, crypto-only payment processor. That single design choice inverts every constraint above.

Non-custodial means funds go directly to wallets you control. Payzum never holds, pools or controls the money — settlement is the payment. There is no Payzum balance sitting between your customer and you, which means there's no balance to freeze, delist, or force-convert on a date somebody else picks.

No account requirement on the buyer. Your customer pays from whatever self-custody wallet they already use. They don't sign up for anything, they don't need to be a customer of your provider, and they don't need to live in your country. They scan a QR or open a link and send.

Coin- and chain-agnostic. Bitcoin, Ethereum, Solana, Polygon, Base, Arbitrum, Optimism, BNB Chain and Avalanche — with optional auto-conversion to USDC or USDT so you carry no volatility between the sale and your books. You take what your customer holds instead of what an intermediary approved.

Every surface a real business needs. Hosted checkout (redirect, modal or inline), no-code payment links and buttons, invoices with expiration and overpayment detection, recurring subscriptions, donations and tip jars. For in-person sales, a POS that issues a new QR per sale, physical terminals, PIN-protected cashier accounts and per-cashier analytics. No acquirer, no card-network fees, no chargebacks — on-chain finality means a settled payment can't be reversed 120 days later.

And the agentic layer KSNET is piloting is available now. Payzum's x402 support makes an existing API payable by AI agents in USDC on Base, per call, settled straight to the merchant's wallet. Payzum acts as the middleware/proxy in front of your endpoint — you configure your existing URL, your API key and a price, and Payzum publishes the x402 URL, returns the 402, settles through an external facilitator (Coinbase's today) and proxies the paid call to your real endpoint. No protocol to implement, no code to write. // confirmar pricing actual: roughly 1,000 transactions a month free, then about $0.001 per transaction plus gas.

One thing Payzum deliberately does not do: settle to a bank account. It is crypto-only. If your business needs dirhams in a bank — Emirates' actual requirement — you need a different tool. If you're happy receiving stablecoins in a wallet you own, you skip the intermediary entirely.

How open crypto acceptance works, step by step

1. Connect the wallets you already control. Add a receiving address per chain. Payzum never takes custody, so there's no balance to fund and nothing to withdraw later.
2. Pick your surface. Hosted checkout or a drop-in plugin for an online store, a payment link for email and WhatsApp, an invoice with an expiry for deposits and B2B, a subscription for recurring plans, or the POS QR for the counter.
3. Charge the customer. They scan the QR or open the link and pay from any wallet on any supported chain. Confirmation lands in seconds — about 0.4s on Solana, roughly 2s on Base and Polygon — so the guest is checked in or the ticket issued before they've put their phone away.
4. Receive and reconcile. Funds arrive in your wallet, optionally auto-converted to USDC or USDT. Signed webhooks fire into your booking engine, PMS, ERP or CRM through the REST API, with a full audit log and 2FA on the dashboard.

Use cases: what this looks like in travel and tourism

The Emirates launch is a travel story, so start there — but the mechanics apply to any business whose customers arrive from somewhere else.

• A Dubai excursion desk or DMC. A tourist walks up holding USDT in a phone wallet. The agent generates a fresh QR for that sale on any phone, the traveller scans it, and the funds land in the operator's wallet before the booking is written up. No terminal, no acquirer, and nothing for the traveller to sign up for. This is the same flow we detail for tour operators.
• A boutique hotel taking a deposit from an overseas guest. Send an invoice with an expiration and overpayment detection, or a payment link over WhatsApp. The guest pays from their own wallet in whatever coin they hold; you auto-convert to USDC and the deposit is final — no card authorisation to expire, no chargeback window on arrival day. More on that in our hotel guide.
• A travel agency paying suppliers and affiliates. The reverse direction matters just as much: mass payouts by CSV for BTC/LTC/DOGE plus EVM stablecoin payouts on Polygon, Arbitrum, Optimism, Base, BNB Chain and Avalanche. Pay a hundred partners in one batch instead of a hundred wires.
• A travel API provider selling to AI agents. Fare search, seat maps, availability feeds — the exact endpoints that agentic travel assistants call. With x402 they become payable per request in USDC on Base without an API key exchange or a contract, which is precisely the model KSNET's second proof of concept is designed to test.

Closed-loop wallet checkout vs open on-chain acceptance

Common objections

"If a licensed custodian is good enough for Emirates, isn't it safer than holding my own wallet?"

It's answering a different question. Emirates needed dirhams in its accounts and zero price exposure, so it bought exactly that from a regulated counterparty — a sound decision for a business of that size. But custody is a trade, not a free upgrade: you gain fiat conversion and you accept a third party between your customer's payment and your money, under terms that can change without your input. European merchants learned that in July when a licensed platform stopped supporting a stablecoin and scheduled automatic conversion of remaining balances. Non-custodial settlement doesn't make that risk smaller; it removes the question entirely, because there is no balance anywhere but yours.

"My customers don't hold crypto — isn't this all still theoretical?"

Less theoretical every month, and the buyer-side friction is what's disappearing fastest. Consumer wallets are moving into the devices and apps people already use — Samsung demonstrated native stablecoin support in Samsung Wallet on July 22, which we analysed here. The realistic position isn't that every customer pays in stablecoins tomorrow; it's that the segment which does — cross-border customers, freelancers paid from abroad, travellers, crypto-native buyers — currently has almost nowhere to spend. Being one of the few places that accepts them is the entire opportunity while acceptance is still under a couple of percent of on-chain activity.

"Won't price volatility eat the margin?"

Price the sale in your currency, let the customer pay in whatever they hold, and switch on auto-conversion to USDC or USDT. What lands in your wallet is dollar-denominated, and because on-chain settlement is final in seconds there's no multi-day window in which the rate can move against you.

Sources

• Emirates media centre — Emirates and Crypto.com give customers a new way to pay for flights
• The National — Dubai's Emirates airline starts accepting crypto payments for flights (July 28, 2026)
• Crypto Economy — Solana Pay expands into South Korea as KSNET connects 330,000+ merchants