A foreign customer taps their card.
The rate is locked at that moment.

KRW price tags stay. The customer pays a fixed USD amount. Acquirers and merchants keep their current setup,
and every payment adds new revenue.

Partner inquiries
Built on the SNAP pricing engine · Rates published in advance, 2-minute rounds · No acquirer development to start · Every step recorded
One payment, start to finish · A restaurant in Myeongdong, ₩49,000
1
Amount due
₩ 49,000Pay in KRW
USD 34.65Pay in USD
Applied rate 1 USD = 1,414.000 · 2-minute round
Both amounts appear before the tap
They see the USD amount up front and decide
→
2
USD 34.65
USD 34.65USD payment selected
They choose USD and tap their card
The rate locks at that moment
→
3
Traveler
USD 34.65 locked
The bill never moves, whatever the rate does
Merchant
₩ 49,000 locked
Price tags and settlement stay in KRW
Both sides finish on locked amounts
Neither side worries about the rate
From the same paymentAcquirer +revenueVAN · PG +revenueMerchant +revenueFX exposure 0 · KustodyFi locks the rate

AI knows the exchange rate.
It doesn't know the one you can trade.

The web only has retail reference rates and global averages. SNAP delivers local prices tagged with market, product, time and side over MCP, so AI and clients can actually execute.

Request early access
Opening early September · MCP standard (Claude · ChatGPT · Codex) · A price needs an address
AI Assistant · SNAP MCP connected
Q
What's the tradable range for USD/KRW in the Seoul market right now?
→ tool call snap.get_market_rate ( pair: "USDKRW", market: "KR_SEOUL" )
Market Seoul spotObserved 10:31:57 KSTProduct SPOTSide Bid / Offer
BID · you sell
1,412.300
OFFER · you buy
1,412.700
✕Web search can't reach this answer.
It only finds retail reference rates and global averages (measured 2026-08-17)
BUILT ON SNAPReverseFX

The first place SNAP prices go to work. When a foreign customer taps their card, the amount is locked at a rate SNAP computed.

Partner inquiries