Oman Payments (Tap Payments — cards / Apple Pay)

Official3 tools

by junter1989k-ai · JavaScript

Oman payments for AI agents — cards / Apple Pay via Tap Payments. Never holds funds.

Oman Payments for AI agents via the Model Context Protocol (MCP). The server provides payment support for cards and Apple Pay through Tap Payments and does not hold funds. Tooling exposed by the server is counted as 3, and it is configured to be used over HTTP.

🛠️ Key Features

MCP server for “Oman payments for AI agents”
Supports cards and Apple Pay via Tap Payments
“Never holds funds”
Operates via an HTTP MCP endpoint

🚀 Use Cases

Enabling AI agents to accept payments in Oman
Integrating with MCP-capable clients (e.g., Claude Desktop, Cursor, Windsurf)

⚡ Developer Benefits

No installation required for client use
Credentials, when needed, “travel as HTTP headers on each request”
Credentials “are never stored” (see linked threat model)

⚠️ Limitations

The server description does not specify supported payment flows beyond cards and Apple Pay via Tap Payments.

Topics

ai-agentclaudemcpmcp-serveromanpaymentstapwishpool

Captured live from the server via tools/list.

create_payment_link

Create a payment link in OMR for Oman via Tap Payments. Buyer pays with cards, Apple Pay — whatever is enabled on the Tap account. Returns a hosted checkout URL the buyer opens to pay — payment completes automatically, no confirm step. Bring your own credentials via HTTP header (x-tap-secret-key; free test credentials from businesses.tap.company never move real money). Money always flows buyer→Tap Payments→merchant; this service never touches funds.

Parameters5

amount_omr	number	required	Amount in OMR (decimals allowed), e.g. 5.0. Minimum 0.5.
description	string	required	What this payment is for (shown to the buyer, ≤200 chars)
customer_email	string	required	Buyer email (required by Tap Payments; the receipt goes there).
reference_id	string	optional	Your unique order reference (≤40 chars). Auto-generated if omitted.
success_url	string	optional	Optional https URL to send the buyer to after payment.

Raw schema

{
  "type": "object",
  "properties": {
    "amount_omr": {
      "type": "number",
      "minimum": 0.5,
      "maximum": 1000000,
      "description": "Amount in OMR (decimals allowed), e.g. 5.0. Minimum 0.5."
    },
    "description": {
      "type": "string",
      "description": "What this payment is for (shown to the buyer, ≤200 chars)"
    },
    "customer_email": {
      "type": "string",
      "description": "Buyer email (required by Tap Payments; the receipt goes there)."
    },
    "reference_id": {
      "type": "string",
      "description": "Your unique order reference (≤40 chars). Auto-generated if omitted."
    },
    "success_url": {
      "type": "string",
      "description": "Optional https URL to send the buyer to after payment."
    }
  },
  "required": [
    "amount_omr",
    "description",
    "customer_email"
  ]
}

query_payment_status

Check whether a Oman payment (created by create_payment_link) has been paid. Queries Tap Payments directly — pull-based, no webhook needed. paid=true when status is PAID.

Parameters1

charge_id

string

required

The charge_id (chg_...) returned by create_payment_link

Raw schema

{
  "type": "object",
  "properties": {
    "charge_id": {
      "type": "string",
      "description": "The charge_id (chg_...) returned by create_payment_link"
    }
  },
  "required": [
    "charge_id"
  ]
}

refund_payment

Refund a paid payment (created by create_payment_link). Full refund by default; pass amount for a partial refund where supported. Refunds respect the same owner policy guardrails (x-agentpay-max-amount) as payments — the amount is checked before anything is sent to the gateway.

Parameters2

charge_id	string	required	The charge_id of the paid payment (same id used by query_payment_status)
amount	number	optional	Optional partial-refund amount in the local currency major unit. Omit for a full refund.

Raw schema

{
  "type": "object",
  "properties": {
    "charge_id": {
      "type": "string",
      "description": "The charge_id of the paid payment (same id used by query_payment_status)"
    },
    "amount": {
      "type": "number",
      "description": "Optional partial-refund amount in the local currency major unit. Omit for a full refund."
    }
  },
  "required": [
    "charge_id"
  ]
}

README.md2 KBView on GitHub

Oman Payments MCP — let AI agents accept payments in Oman

Use it in 60 seconds

Paste this into your MCP client config (Claude Desktop, Cursor, Windsurf, or any MCP-capable agent):

json

{
  "mcpServers": {
    "oman-payments": {
      "type": "http",
      "url": "https://mcp-om.wishpool.app/mcp"
    }
  }
}

Nothing to install. Credentials, when you need them, travel as HTTP headers on each request and are never stored — see the threat model.

Or run it yourself

Would you rather not send production credentials to a server you do not control? Deploy this identical code to your own account and point your agent at your own URL:

bash

git clone https://github.com/junter1989k-ai/oman-payments-mcp && cd oman-payments-mcp && npx vercel --prod

MIT-licensed. Self-hosting removes us from the picture entirely, at no cost and with no loss of function.

Live · MCP endpoint: https://mcp-om.wishpool.app/mcp · Listed on the official MCP Registry as app.wishpool/oman-payments-mcp · Part of a 71-country family — hub: mcp.wishpool.app

A remote MCP server that lets any AI agent (Claude, ChatGPT, Cursor…) accept payments in Oman: cards, Apple Pay — whatever is enabled on the Tap account — via Tap Payments's hosted checkout.

⚖️ Stateless translation layer: funds always flow buyer → Tap Payments → merchant directly. Never holds funds or stores credentials — no database at all.

Quick start

MCP endpoint: https://mcp-om.wishpool.app/mcp (Streamable HTTP, stateless JSON-RPC)

Header	Value
`x-tap-secret-key`	your Tap Payments secret key (free sk_test_ keys from businesses.tap.company; sk_live_ keys are production)

Tools

Tool	What it does
`create_payment_link`	Create a OMR hosted-checkout link.
`query_payment_status`	Pull-based status check; `paid=true` when PAID.

Develop

bash

node test/serve.js      # local server (http://localhost:3274/mcp)
node test/e2e.js        # protocol + validation suite (probes real Tap Payments auth errors)

Zero runtime dependencies; Node ≥ 18. MIT license.

Install

Tools (3)

create_payment_linkquery_payment_statusrefund_payment

Remote endpoint

Streamable HTTP

Hosted server - connect over the network, no local install.

url

https://mcp-om.wishpool.app/mcp

Add to VS Code Add to Cursor

claude_desktop_config.json

json

{
  "mcpServers": {
    "oman-payments-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://mcp-om.wishpool.app/mcp"
      ]
    }
  }
}

Desktop config is stdio-only; this bridges via mcp-remote. Native remote: Settings > Connectors.

🛠️ Key Features

🚀 Use Cases

⚡ Developer Benefits

⚠️ Limitations

Topics

create_payment_link

query_payment_status

refund_payment

Oman Payments MCP — let AI agents accept payments in Oman

Use it in 60 seconds

Or run it yourself

Quick start

Tools

Develop

Install

Remote endpoint

Related servers