Thailand Payments Mcp

What is Thailand Payments Mcp?

It is a remote MCP server that enables AI agents (Claude, ChatGPT, Cursor, etc.) to accept Thai payments including PromptPay QR, credit/debit cards, TrueMoney wallet, and internet banking. It routes payments through Opn Payments (formerly Omise) Links, a major Thai payment gateway.

How to use Thailand Payments Mcp?

Configure your MCP client to use the endpoint https://mcp-th.wishpool.app/mcp with the header x-omise-secret-key set to your Opn (Omise) secret key. Use test keys (skey_test_...) for sandbox mode and live keys (skey_live_...) for production. The server implements Streamable HTTP with stateless JSON-RPC and provides two tools: create_payment_link and query_payment_status.

Key features of Thailand Payments Mcp

• Accept PromptPay QR payments
• Accept credit/debit cards and TrueMoney wallet
• Pull-based payment status check (no webhook)
• Stateless — never holds or stores funds
• Creates THB payment links (minimum ฿20)
• Checks payment status by link ID

Use cases of Thailand Payments Mcp

• AI assistants facilitating Thai e-commerce checkouts
• Chatbots generating PromptPay QR payment links
• Automated invoice creation with hosted payment pages
• Payment verification in AI workflows without webhooks

FAQ from Thailand Payments Mcp

What payment methods does it support?

PromptPay QR, credit/debit cards, TrueMoney wallet, and internet banking via Opn Payments.

Does this server store or handle my funds?

No. It is a stateless translation layer; funds flow directly from buyer to Opn to merchant. The server never holds, moves, or stores funds or credentials.

How can I test the server in sandbox mode?

Use an Opn (Omise) secret key starting with skey_test_..., which works in test mode with no real money. Test keys are free from the Opn dashboard.

What tools are available?

create_payment_link creates a THB payment link (min ฿20) and returns a hosted payment URL plus link ID. query_payment_status checks the status by link ID, returning UNPAID or PAID with failure reason.

What are the transport and authentication requirements?

The server uses Streamable HTTP with stateless JSON-RPC. Authentication is via the x-omise-secret-key header. For development, Node.js ≥ 18 is required to run the local server or test suite.