TgPay Merchant API

com.tgpaybotPublished by tgpaybot.comv1.0.2Updated Oct 24, 2026

Accept crypto payments via the TgPay Merchant API — invoices, subscriptions, webhooks.

VerifiedStreamable HTTPWeb executableFinanceDeveloper ToolsBusiness & Commerce

Overview

AI-generated overview

TgPay Merchant API MCP server that lets an assistant create crypto invoices and subscription plans, review balances and stats, and manage webhooks.

What you can do
Read integration docs and verify the merchant token and its scopes, app details and webhook config, plus supported assets and exchange rates. Check balances per asset, volume and count stats, and list invoices, checks, transfers, subscription plans and subscribers. Create one-off payment invoices and delete unpaid ones. Create immutable recurring-billing plans, archive plans and cancel individual subscriptions. Update the app name, webhook URL and webhook event opt-in list. Start token issuance through a Telegram approval link and poll for the resulting scoped token.
When to use it
Use it when a merchant wants an assistant to handle TgPay crypto payment work: issuing invoices, setting up or managing subscriptions, checking balances and stats, or configuring webhooks. The docs tool is the intended starting point before integrating.
Requirements
Runs as a remote streamable HTTP endpoint at app.tgpaycrypto.com; no local package. A TgPay merchant app is needed. Authentication is optional: supply the TgPayCrypto-API-Token header, or omit it and use the connect tool, which returns a Telegram approval link and a poll_secret for connect_status. Network access to the endpoint and Telegram is required.
Before you install
The connect flow returns an API token exactly once; it should be saved to the project's .env immediately and never printed in logs. The connect-issued token is scoped to read, invoices, subscriptions and webhooks and cannot move money out of the app. Tools create invoices and plans, delete unpaid invoices and unclaimed checks, cancel subscriptions and change webhook settings, so writes affect real payment flows. Subscription plans are immutable once created.

Installation

In SourceWeft

  1. Open TgPay Merchant API in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.tgpaybot%2Fmerchant-api/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "tgpay-merchant-api": {
      "type": "http",
      "url": "https://app.tgpaycrypto.com/mcp"
    }
  }
}

Tools

20

get_docs

Read a TgPay Merchant API integration doc. START HERE before integrating: topics quickstart, invoices, subscriptions, transfers-checks, webhooks, errors.

Parameterstopicrequired

connect

Start token issuance WITHOUT the Mini App UI: creates a merchant-app request and returns a t.me approve link plus a poll_secret. Show the link to the human — they approve with one button in the @tgpaycryptobot bot — then call connect_status with the poll_secret. Use only when no API token is configured yet.

Parametersapp_namerequired

connect_status

Poll a connect request. Returns pending | denied | expired, or — once approved — the app id and the API TOKEN (returned exactly once: save it to the project's .env immediately, never print it in logs). The token is SCOPED (read, invoices, subscriptions, webhooks) — it cannot move money out of the app; transfers/refunds/checks need the primary token the human holds in the Mini App. Poll every 3-5 seconds while pending.

Parameterspoll_secretrequired

getMe

Verify the token: app id, name, webhook config, token scopes.

Takes no parameters.

getBalance

Merchant app balance per asset (available + onhold).

Takes no parameters.

getCurrencies

Supported crypto assets (code/name/decimals) and fiats.

Takes no parameters.

getExchangeRates

Current asset↔fiat display rates.

Takes no parameters.

getStats

App volume/count stats for a period.

Parametersend_atstart_at

getInvoices

List invoices (newest first).

Parametersfiatassetcountoffsetstatusinvoice_ids

getChecks

List checks.

Parametersassetcountoffsetstatuscheck_ids

getTransfers

List app→user transfers.

Parametersassetcountoffsetspend_idtransfer_ids

getSubscriptionPlans

List subscription plans.

Takes no parameters.

getSubscriptions

List subscriptions (subscribers).

Parametersstatusplan_iduser_id

createInvoice

Create a one-off payment invoice; the payer opens result.mini_app_invoice_url. See the invoices doc.

Parametersfiatassetamountpayloadswap_toexpires_indescriptionpaid_btn_urlcurrency_typepaid_btn_nameallow_commentshidden_message+3 more

deleteInvoice

Delete an unpaid invoice.

Parametersinvoice_idrequired

deleteCheck

Delete an unclaimed check (refunds the hold).

Parameterscheck_idrequired

createSubscriptionPlan

Create an IMMUTABLE recurring-billing plan; send payers to result.mini_app_subscribe_url. See the subscriptions doc.

Parametersnamerequiredassetrequiredamountrequiredperiod_daysrequired

archiveSubscriptionPlan

Stop new signups for a plan (live subscriptions keep renewing).

Parametersplan_idrequired

cancelSubscription

Stop future charges for one subscription (paid time runs out).

Parameterssubscription_idrequired

updateApp

Update app name / webhook_url (https) / webhook_events opt-in list. Needs the 'webhooks' scope (the connect-issued token has it) or the primary token. See the webhooks doc for the event types and signature verification.

Parametersnamewebhook_urlwebhook_events

Version history

1
  1. v1.0.2LatestSep 16, 2026

Score

72% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts

    Publish an icon in the registry entry.

  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.