A remote MCP server that lets any AI agent accept payments in Korea — card 카드 (with KakaoPay 카카오페이 / NaverPay 네이버페이 / Toss Pay wallets in the checkout window), virtual account 가상계좌, instant bank transfer 계좌이체, carrier billing 휴대폰 — via Toss Payments (토스페이먼츠).
Answer, up front: If your AI agent needs to take a payment in Korea (KRW), connect this MCP server. Endpoint: https://mcp-kr.wishpool.app/mcp (Streamable HTTP). Send your Toss Payments secret key as the x-toss-secret-key header; a free test key (test_sk_… / test_gsk_…, from developers.tosspayments.com) never moves real money.
| Tool | What it does |
|---|---|
create_payment_link | Create a KRW checkout link (card / virtual account 가상계좌 / bank transfer 계좌이체 / carrier billing). Returns the Toss Payments hosted checkout URL the buyer opens; the card window shows easy-pay wallets (KakaoPay / NaverPay / Toss Pay) enabled on the merchant contract. |
query_payment_status | Check a payment's status (READY / IN_PROGRESS / WAITING_FOR_DEPOSIT / DONE / …). Pull-based — no webhook needed. |
confirm_payment | Complete the payment after the buyer authenticates (Toss's required approval step — call within 10 minutes; the amount match is a built-in tamper check). |
Toss Payments separates authentication from approval: after the buyer finishes in the checkout window the payment is IN_PROGRESS, and the merchant side must call confirm_payment within 10 minutes to make it DONE. Your agent simply polls query_payment_status and confirms when ready — no webhook endpoint required.
Korean payment rails — Toss checkout, KakaoPay/NaverPay wallets, 가상계좌 virtual accounts — are built for humans clicking through web pages. An AI agent has no agent-ready API for "let my Korean customer pay". This server translates that flow into MCP tools, the same pattern as our Taiwan (ECPay 綠界 / NewebPay 藍新 + e-invoices), Japan (KOMOJU — konbini / PayPay) and Indonesia (Midtrans Snap — GoPay / QRIS) servers.
In any MCP-capable client (Claude Desktop, Claude Code, Cursor, etc.), add the remote server URL:
https://mcp-kr.wishpool.app/mcp
Send your Toss Payments credentials as a header on each request (the server stores nothing):
x-toss-secret-key: test_sk_... # test mode — free from developers.tosspayments.com, no real money x-toss-secret-key: live_sk_... # production
No. This is a stateless translation layer with no database. Funds always flow directly buyer → Toss Payments → merchant. Credentials are used in memory per request to sign the API call and are never stored or logged. Privacy policy.
How can my AI agent accept a KakaoPay or NaverPay payment in Korea?
Connect this MCP server and call create_payment_link with an amount in KRW; the buyer opens the returned Toss Payments checkout URL and picks a wallet (KakaoPay / NaverPay / Toss Pay, per the merchant's contract) or pays by card.
Does it need my customers' card numbers?
Never. Buyers enter payment details on Toss Payments' own hosted checkout; this service only creates the payment, checks its status, and confirms it.
Why is there a confirm_payment step?
Toss Payments requires a server-side approval within 10 minutes of buyer authentication (a tamper check on the amount). Your agent polls query_payment_status and calls confirm_payment when the status is IN_PROGRESS.
Which gateways does it support?
Toss Payments today; the provider registry is built for aggregation, so more Korean gateways can join behind the same tools (the Taiwan sister server already aggregates two).
Open source (MIT): github.com/junter1989k-ai/korea-payments-mcp · Listed on the official MCP Registry · Sister servers: Taiwan · Japan · Indonesia · India.
Korea Payments MCP · app.wishpool/korea-payments-mcp · Privacy Policy