MCP.so
Sign In
T

Taiwan Payments MCP Server

@junter1989k-ai

Basic information

License

MIT

Transports

stdio

Author

junter1989k-ai

Submitted by

junter1989k-ai

About Taiwan Payments MCP Server

Accept payments in Taiwan (TWD) and issue Taiwan government e-invoices from any AI agent. Aggregates ECPay and NewebPay behind one tool set. Stateless BYO-credentials design - never holds funds. Zero-setup demo via ECPay's official sandbox. Remote endpoint: https://mcp.wishpool.a

Taiwan Payments MCP Server config

Add this server to your MCP-compatible client using the configuration below.

{
  "mcpServers": {
    "taiwan-payments": {
      "url": "https://mcp.wishpool.app/mcp"
    }
  }
}

Taiwan Payments MCP Server tools

Tool list not available yet

This listing does not currently have a tool list to display. This does not mean the server has no tools; check its documentation for supported capabilities.

Fetch the live tool list directly from this server's endpoint using the button above.

Overview

What is Taiwan Payments MCP?

A remote MCP server that lets any AI agent (Claude, ChatGPT, Cursor…) accept payments and issue Taiwanese government e-invoices. It aggregates multiple Taiwan gateways (ECPay default, NewebPay) behind a single tool and translates operations the agent can call directly.

How to use Taiwan Payments MCP?

Add the endpoint https://mcp.wishpool.app/mcp to a remote-MCP client (Claude Desktop, Claude Code, Cursor…). Without any credential headers, all tools run against ECPay's official public sandbox. For real use, pass your own merchant credentials via HTTP headers: x-ecpay-merchant-id, x-ecpay-hash-key, x-ecpay-hash-iv (plus x-ecpay-mode: production); for NewebPay use x-newebpay-* headers. E-invoice credentials use x-einvoice-* headers.

Key features of Taiwan Payments MCP

  • Aggregates multiple Taiwan payment gateways (ECPay, NewebPay) behind one tool
  • Create TWD payment links (credit card, ATM, convenience store, mobile pay)
  • Query payment status to check order payment completion
  • Issue and void Taiwan B2C government e-invoices (電子發票)
  • Zero-setup demo runs against ECPay public sandbox without credentials
  • Stateless translation layer: funds and credentials never held or stored

Use cases of Taiwan Payments MCP

  • AI agent accepting payments in Taiwan for an online store or service
  • Automatically issuing Taiwan e-invoices after payment confirmation
  • Checking if a customer’s order has been paid through ECPay or NewebPay
  • Voiding an incorrectly issued e-invoice programmatically

Frequently asked questions

1

Do I need to install anything to use Taiwan Payments MCP?

No local installation is needed for clients—just add the MCP endpoint. The server itself is remote; for local development you need Node ≥ 18 and zero runtime dependencies.

2

Is my payment data stored on the server?

No. Funds always flow buyer → gateway → merchant directly. The server never holds, touches, or stores any payments or merchant credentials.

3

Can I test without real credentials?

Yes. When no credential headers are supplied, all tools run against ECPay’s official public sandbox. NewebPay does not have a public sandbox, so you must provide your own test‑merchant credentials to test NewebPay.

4

How do I switch between ECPay and NewebPay?

Use the `provider` field in the `create_payment_link` tool. If not specified, the server auto‑selects the gateway based on which credential headers you provide (defaults to ECPay).

5

What transport and authentication does Taiwan Payments MCP use?

It uses Streamable HTTP (stateless JSON‑RPC). Authentication is done per request by passing merchant credentials in HTTP headers (`x-ecpay-*`, `x-newebpay-*`, `x-einvoice-*`).

Comments

More MCP servers