Bangladesh Payments (SSLCommerz — bKash / Nagad)

Official4 toolsLive

by junter1989k-ai · JavaScript

Bangladesh payments for AI agents — bKash / Nagad via SSLCommerz. Never holds funds.

Topics

ai-agentbangladeshclaudemcpmcp-serverpaymentswishpool

Captured live from the server via tools/list.

create_payment_link

Create a payment link in BDT for Bangladesh via SSLCommerz. Buyer pays with bKash, Nagad, Rocket mobile banking, cards, internet banking via SSLCommerz. Returns a hosted checkout URL the buyer opens to pay — payment completes automatically, no confirm step. Bring your own credentials via HTTP header (x-sslcommerz-store-id; free test credentials from developer.sslcommerz.com never move real money). Money always flows buyer→SSLCommerz→merchant; this service never touches funds.

Parameters5

amount_bdt	number	required	Amount in BDT (decimals allowed), e.g. 100. Minimum 10.
description	string	required	What this payment is for (shown to the buyer, ≤200 chars)
customer_email	string	optional	Optional buyer email.
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_bdt": {
      "type": "number",
      "minimum": 10,
      "maximum": 50000000,
      "description": "Amount in BDT (decimals allowed), e.g. 100. Minimum 10."
    },
    "description": {
      "type": "string",
      "description": "What this payment is for (shown to the buyer, ≤200 chars)"
    },
    "customer_email": {
      "type": "string",
      "description": "Optional buyer email."
    },
    "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_bdt",
    "description"
  ]
}

query_payment_status

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

Parameters1

tran_id

string

required

The tran_id returned by create_payment_link

Raw schema

{
  "type": "object",
  "properties": {
    "tran_id": {
      "type": "string",
      "description": "The tran_id returned by create_payment_link"
    }
  },
  "required": [
    "tran_id"
  ]
}

refund_payment

Refund a paid Bangladesh payment (created by create_payment_link) via SSLCommerz. Identify the payment by tran_id (the reference returned by create_payment_link — the tool looks it up to find the bank_tran_id and paid amount) OR pass bank_tran_id directly. Full refund by default; pass refund_amount_bdt for a partial refund (required when refunding by bank_tran_id, since the paid amount cannot be derived). Returns refund_ref_id (keep it to poll query_refund_status) and a first status read. Refunds respect the same owner policy guardrails (x-agentpay-max-amount) as payments — the refund amount is checked before anything is sent to SSLCommerz. The buyer must have PAID (query_payment_status = PAID) and the transaction be bank-settled before a refund can be initiated.

Parameters5

tran_id	string	optional	The tran_id from create_payment_link. Looked up to find the bank_tran_id and paid amount. Provide this OR bank_tran_id.
bank_tran_id	string	optional	The SSLCommerz bank_tran_id (from query_payment_status once PAID). Provide this OR tran_id. If used, refund_amount_bdt is required.
refund_amount_bdt	number	optional	Optional partial-refund amount in BDT (decimals allowed). Omit for a full refund of the paid amount (only possible when refunding by tran_id).
refund_remarks	string	optional	Reason for the refund shown on the SSLCommerz record (≤255 chars). Defaults to "Refund".
refund_trans_id	string	optional	Optional your-side unique refund transaction id (≤30 chars) for reconciliation.

Raw schema

{
  "type": "object",
  "properties": {
    "tran_id": {
      "type": "string",
      "description": "The tran_id from create_payment_link. Looked up to find the bank_tran_id and paid amount. Provide this OR bank_tran_id."
    },
    "bank_tran_id": {
      "type": "string",
      "description": "The SSLCommerz bank_tran_id (from query_payment_status once PAID). Provide this OR tran_id. If used, refund_amount_bdt is required."
    },
    "refund_amount_bdt": {
      "type": "number",
      "minimum": 1,
      "description": "Optional partial-refund amount in BDT (decimals allowed). Omit for a full refund of the paid amount (only possible when refunding by tran_id)."
    },
    "refund_remarks": {
      "type": "string",
      "description": "Reason for the refund shown on the SSLCommerz record (≤255 chars). Defaults to \"Refund\"."
    },
    "refund_trans_id": {
      "type": "string",
      "description": "Optional your-side unique refund transaction id (≤30 chars) for reconciliation."
    }
  }
}

query_refund_status

Check the status of a refund initiated by refund_payment. Queries SSLCommerz directly using the refund_ref_id returned by refund_payment. refund_status is one of: refunded (done), processing (in progress), cancelled.

Parameters1

refund_ref_id

string

required

The refund_ref_id returned by refund_payment

Raw schema

{
  "type": "object",
  "properties": {
    "refund_ref_id": {
      "type": "string",
      "description": "The refund_ref_id returned by refund_payment"
    }
  },
  "required": [
    "refund_ref_id"
  ]
}

README.md3 KBView on GitHub

Bangladesh Payments MCP — let AI agents accept payments in Bangladesh

Use it in 60 seconds

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

json

{
  "mcpServers": {
    "bangladesh-payments": {
      "type": "http",
      "url": "https://mcp-bd.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/bangladesh-payments-mcp && cd bangladesh-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-bd.wishpool.app/mcp · Listed on the official MCP Registry as app.wishpool/bangladesh-payments-mcp · Part of a 50-country family — hub: mcp.wishpool.app

A remote MCP server that lets any AI agent (Claude, ChatGPT, Cursor…) accept payments in Bangladesh: bKash, Nagad, Rocket mobile banking, cards, internet banking via SSLCommerz — via SSLCommerz's hosted checkout.

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

Quick start

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

Header	Value
`x-sslcommerz-store-id`	your SSLCommerz store credentials (free sandbox stores from developer.sslcommerz.com — also send x-sslcommerz-mode: sandbox; default production)

Tools

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

Develop

bash

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

Zero runtime dependencies; Node ≥ 18. MIT license.

Install

Tools (4)

create_payment_linkquery_payment_statusrefund_paymentquery_refund_status

Remote endpoint

Streamable HTTP

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

url

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

Add to VS Code Add to Cursor

claude_desktop_config.json

json

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

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