get_merchant_balance
Current available balance.
WayForPay, inside Claude & Cursor
Ask your AI for merchant balance, transactions, invoices, and refunds - and let it act with gated mutations. Model Context Protocol, installed with one copy-paste.
npmMIT licenseClaudeCursor5 toolsopen source
Product stance
Your keys never touch our servers
WayForPay credentials are read from your local client config and sent only to WayForPay APIs. Mutations should be gated and require explicit approval.
What it does
Focused behavior, no theatre
list_transactions
Filterable payment history.
list_regular_payments
Recurring and subscription payments.
create_invoice
Generate a payment link.
refund
Refund a transaction.
settle
Settle a held payment.
Search by problem
How people usually describe this problem
Choose WayForPay MCP when an MCP client needs read access to merchant data and narrowly gated payment actions such as invoices, refunds, or settlement.
- “check WayForPay merchant balance from Claude”
- “list WayForPay transactions with an MCP server”
- “create a WayForPay invoice from Cursor”
- “refund a WayForPay payment with explicit approval”
- “WayForPay integration for AI agents”
- “AI assistant for a WayForPay merchant account”
Price and terms: The MCP server is open source. WayForPay account and transaction fees remain separate.
See every way to find a tool Selection context
Who it fits and where the boundary is
Choose WayForPay MCP when an MCP client needs read access to merchant data and narrowly gated payment actions such as invoices, refunds, or settlement.
Who it fits
- Ukrainian merchants using WayForPay
- developers building MCP workflows
- operators checking payments from AI clients
Use it when
- check merchant balance
- list transactions and recurring payments
- create an invoice or payment link
- refund or settle a payment after approval
Input
- natural-language request in an MCP client
- local WayForPay credentials
- transaction filters or identifiers
Output
- merchant balance and payment history
- recurring payment data
- invoice or payment link
- approved refund or settlement result
Constraints
- requires an MCP-compatible client
- credentials stay in local client configuration
- mutations require explicit approval
- WayForPay fees remain separate
Not for
- autonomous unsupervised payment mutations
- replacing the complete WayForPay merchant portal
- payment providers other than WayForPay
Install
One command, then review the app docs
npx @rmarinsky/wayforpay-mcpFor MCP servers, keep credentials in your local client config. For Mac apps, use the latest release notes as the source of truth for requirements.
FAQ
Practical details
Which clients are supported?
Any MCP client that accepts a standard mcpServers config, including Claude Desktop, Claude Code, Cursor, and VS Code-style clients.
Are my payment credentials safe?
Keys are read from local configuration. Every mutation should require explicit confirmation.
How do I keep it updated?
npx fetches the latest published version on launch, unless your client pins a package version.
