SkillFoxx

EasyPay AI Skill

A skill that connects an agent to EasyPay: Stripe products and invoices, SBP and T-Bank payout links, crypto and Mercury in natural language

  • 3 ★ on the repository
  • Last commit
  • MIT
Skill

Broad access

Why this level

  • Creates real products, payment links, invoices and payouts through the third-party EasyPay payment service
  • The partner API key carries money-moving rights; use a limited personal employee key rather than the shared partner-wide one
All reasons and checks
Russian stack

easypay-labs/easypay-skillAuthor:EasyPay Labs

Install

Services

Manual install

claude mcp add easypay --transport http https://mcp.appload.tech/mcp/ --header "X-Partner-Api-Key: <YOUR_PARTNER_API_KEY>"

Then download SKILL.md into .claude/skills/easypay/, as shown in the README.

Access and checks

How we review

Broad accessThe tool can change data, run commands or handle secrets.

  • Creates real products, payment links, invoices and payouts through the third-party EasyPay payment service
  • The partner API key carries money-moving rights; use a limited personal employee key rather than the shared partner-wide one

This is third-party code. Review the repository files before installing.

What it does

The skill is installed alongside EasyPay's remote MCP server at mcp.appload.tech and teaches an agent the EasyPay vocabulary: which of 26 tools to call to create a Stripe product, an SBP ruble payment link, a Mercury invoice, accept crypto, or pay out a Russian contractor from a dollar balance. The partner API key is passed via an X-Partner-Api-Key header in the MCP client config, not in chat with the model. Money-moving operations like creating a payout need a personal employee key rather than a shared partner-wide one, otherwise the server returns an ACTOR_REQUIRED code and the payout has to go through EasyPay's Telegram mini-app instead.

Who it is for. For businesses with an EasyPay partner account who want to manage products, invoices and payouts across several currencies and providers from one agent.

Good fit when

  • You have an EasyPay partner account and want to create products, payment links and invoices from a chat with an agent
  • You need to pay a Russian contractor in rubles from a dollar or crypto balance
  • You want one interface over Stripe, Mercury, crypto and T-Bank instead of switching between dashboards

Not a fit when

  • You have no EasyPay partner account: it is obtained through the @easypay_onboarding_bot Telegram bot, and there is no plain non-Telegram signup path described
  • You need to work directly with the T-Bank or Stripe API without EasyPay as an intermediary
  • You have no personal employee key: without one, payouts through the agent fail, only reads and previews work

Example request

Arrange a 200,000-ruble payout to our Russian contractor from our dollar balance via EasyPay

Limitations

Works only through an EasyPay partner account, issued after onboarding via the Telegram bot; there is no open self-signup path. Products and invoices may need EasyPay moderation before going live. The MCP server is remote and belongs to EasyPay, not to T-Bank itself, so trust in money movement rests on EasyPay as the intermediary. The author separately warns that every call returns HTTP 200 and the real outcome must be read from the success field in the response body.

How to disable. Remove the easypay server with claude mcp remove easypay (or the equivalent for your agent) and delete the .claude/skills/easypay or .agents/skills/easypay folder.

FAQ

Why can't the agent submit a payout?

A partner-wide key is likely being used instead of a personal one. The ACTOR_REQUIRED code means create_partner_payout_request needs a specific employee's key; with a partner-wide key the payout must go through EasyPay's mini-app instead.

Where does the API key go?

Into the MCP client config as an X-Partner-Api-Key header, never into the chat with the agent; the key never reaches the model's context.

Discussion

No questions or reviews yet.

All T-Bank tools
Russian stack

Unofficial MCP server and skills for a personal T-Bank account: accounts, transfers, bill pay, tickets and groceries

MCP serverBroad access57
Russian stack

A monorepo of MCP servers for Russian and CIS APIs: payments, CRM, marketplaces, delivery, HR and reference data

MCP serverBroad access38
Russian stack

A CLI and skill giving an agent access to a T-Investments account: portfolio, returns, bond screeners and confirmed orders

SkillBroad access48
Russian stack

A FastAPI stand-in for the T-Bank Business API for local development and testing of tbank-mcp: 20-plus endpoints, three months of seeded data

CLIExtended access
Russian stack

A local read-only CLI and MCP for a T-Bank personal account via a web session: operations, receipts and statements, no payments

MCP serverBroad access
Official

T-Investments official remote MCP: an agent reads the portfolio and quotes and can place orders on the brokerage account itself

MCP serverBroad access

README in short

The README gives example phrases in Russian and English, explains the one-command install for Claude Code, Codex and Gemini CLI and the JSON config for Cursor, describes three response codes ACTOR_REQUIRED, CROSS_TENANT_ATTEMPT and DATA_INTEGRITY_ERROR, links to an external Customer Guide with examples and troubleshooting, and states skill version v0.9.0 with its tool catalog synced to the server and a note about the legacy SSE endpoint alongside the current Streamable HTTP one.

README badge

Report a problem