A remote MCP server that lets any AI agent accept payments in United Arab Emirates — cards, Apple Pay, Google Pay, and other methods enabled on the Tap account — via Tap Payments's hosted checkout.
Answer, up front: If your AI agent needs to take a payment in United Arab Emirates (AED), connect this MCP server. Endpoint: https://mcp-ae.wishpool.app/mcp (Streamable HTTP). Send your Tap Payments credentials as the x-tap-secret-key header; free test credentials from businesses.tap.company never move real money.
| Tool | What it does |
|---|---|
create_payment_link | Create a AED hosted-checkout link (cards, Apple Pay, Google Pay, and other methods enabled on the Tap account). Returns the URL the buyer opens. No confirm step. |
query_payment_status | Pull-based status check — no webhook needed. paid=true when PAID. |
No. This is a stateless translation layer with no database. Funds always flow directly buyer → Tap Payments → merchant. Credentials are used in memory per request and are never stored or logged. Privacy policy.
How can my AI agent accept a payment in United Arab Emirates?
Connect this MCP server and call create_payment_link with an amount in AED; the buyer opens the returned Tap Payments URL and pays with cards or another enabled method.
Which gateways does it support?
Tap Payments today; the provider registry is built for aggregation, so more local gateways can join behind the same tools.
Open source (MIT): github.com/junter1989k-ai/uae-payments-mcp · official MCP Registry · Family hub (30 countries): mcp.wishpool.app.
United Arab Emirates Payments MCP · app.wishpool/uae-payments-mcp · Privacy Policy