Bahrain Payments (Tap Payments — Benefit)

Official3 tools

by junter1989k-ai · JavaScript

Bahrain payments for AI agents — Benefit via Tap Payments. Never holds funds.

This MCP server provides Bahrain payments for AI agents, enabling acceptance via Tap Payments. The server is described as not holding funds. It exposes 3 tools and is intended for MCP-capable clients (e.g., Claude Desktop, Cursor, Windsurf) that can connect through an HTTP endpoint.

🛠️ Key Features

Name: app.wishpool/bahrain-payments-mcp
Tool count: 3
Uses Tap Payments for Bahrain payments
“Never holds funds”

🚀 Use Cases

Allow AI agents to accept payments in Bahrain
Configure an MCP client to connect over HTTP

⚡ Developer Benefits

Simple configuration: HTTP url points to https://mcp-bh.wishpool.app/mcp
Credentials, when needed, travel as HTTP headers on each request
Credentials are never stored (see “threat model” link in excerpt)

⚠️ Limitations

No local installation details are provided in the excerpt
Specific tools’ capabilities are not listed here

Topics

ai-agentbahrainclaudemcpmcp-serverpaymentstapwishpool

Captured live from the server via tools/list.

create_payment_link

Create a payment link in BHD for Bahrain via Tap Payments. Buyer pays with Benefit (the Bahraini debit network), 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_bhd	number	required	Amount in BHD (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_bhd": {
      "type": "number",
      "minimum": 0.5,
      "maximum": 1000000,
      "description": "Amount in BHD (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_bhd",
    "description",
    "customer_email"
  ]
}

query_payment_status

Check whether a Bahrain 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.md3 KBView on GitHub

Bahrain Payments MCP — let AI agents accept payments in Bahrain

Use it in 60 seconds

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

json

{
  "mcpServers": {
    "bahrain-payments": {
      "type": "http",
      "url": "https://mcp-bh.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/bahrain-payments-mcp && cd bahrain-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-bh.wishpool.app/mcp · Listed on the official MCP Registry as app.wishpool/bahrain-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 Bahrain: Benefit (the Bahraini debit network), 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-bh.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 BHD hosted-checkout link.
`query_payment_status`	Pull-based status check; `paid=true` when PAID.

Develop

bash

node test/serve.js      # local server (http://localhost:3272/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-bh.wishpool.app/mcp

Add to VS Code Add to Cursor

claude_desktop_config.json

json

{
  "mcpServers": {
    "bahrain-payments-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://mcp-bh.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

Bahrain Payments MCP — let AI agents accept payments in Bahrain

Use it in 60 seconds

Or run it yourself

Quick start

Tools

Develop

Install

Remote endpoint

Related servers