Read Pin Payments charges, refunds, balances, transfers and subscriptions without moving money. For businesses that use Pin Payments to collect payments and manage subscriptions. Hosted by usefulapi — connect from Claude, ChatGPT, Cursor, or any MCP client.
Team and Enterprise: an Owner adds the connector for the organization first.
Run this command, then run /mcp in Claude Code to log in:
Add to Cursor or add this to ~/.cursor/mcp.json:
{
"mcpServers": {
"pin-payments": {
"url": "https://pin-payments.usefulapi.io/mcp"
}
}
}Add to VS Code or add this to .vscode/mcp.json:
{
"servers": {
"pin-payments": {
"type": "http",
"url": "https://pin-payments.usefulapi.io/mcp"
}
}
}No Add custom MCP server option? It depends on your account or workspace settings: see OpenAI's guide.
Run these commands. The second one opens the login page:
Other MCP clients (Windsurf, Cline, Zed and more): add the URL as a remote MCP server (Streamable HTTP). The client then opens the login page in your browser. Do not add an Authorization header: see Before you connect.
Find recent charges, inspect a payment and review refunds already issued against it. The server does not charge or refund customers.
pinpayments_list_charges pinpayments_get_charge pinpayments_list_charge_refunds
Read the account’s available and pending balances by currency, with amounts reported in the currency’s base unit.
pinpayments_get_balance
Find a bank transfer and inspect the charges, fees, refunds and chargebacks that make up its ledger line items.
pinpayments_list_transfers pinpayments_get_transfer pinpayments_list_transfer_line_items
Find disputes, inspect their status and deadlines, and review recorded activity before deciding what to handle in Pin Payments.
pinpayments_list_disputes pinpayments_get_dispute pinpayments_get_dispute_activity
Find a subscription, review its plan and next billing date, and inspect existing ledger credits and debits without changing the subscription.
pinpayments_list_subscriptions pinpayments_get_subscription pinpayments_get_subscription_ledger
The login page asks for your Environment and Pin Payments secret API key.
Find the key in the Pin Payments dashboard under Settings → API Keys. Live and test each have their own keys: choose the matching environment. Pin Payments has no read-only API key: the secret key can create charges, refunds and bank transfers if misused, although this server only sends GET requests. Payment and customer records you request pass to your chosen AI client and its LLM provider. Revoke or replace the key in Pin Payments to stop vendor access. Billing is per secret key and environment; rotating the key starts a new usage and billing identity.
Add only the URL. Do not add an Authorization header or an API key to the client config. The server signs you in with OAuth: the login page asks for your Environment and Pin Payments secret API key. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.
Turn on the Pin Payments connector, then ask in plain words. The AI picks the tools.
| Tool | Type | What it does |
|---|---|---|
pinpayments_get_balance | read | Get balance The current Pin Payments account balance: available (ready to transfer) and pending (available plus estimated funds from charges that have not settled yet), per currency, in the currency's base unit (cents for AUD). GET /balance. |
pinpayments_list_charges | read | List charges List charges (card payments), 25 per page: amount (in the currency's base unit, e.g. cents for AUD), currency, description, payer email, status_message/success, total_fees, merchant_entitlement, amount_refunded, captured, settlement transfers, chargebacks flag, metadata. The card is shown only as scheme and last four digits. GET /charges. |
pinpayments_search_charges | read | Search charges Search charges by free text (description, email, metadata, cardholder name, currency, exact amount in the currency's base unit, exact charge/card/refund/customer token) and/or a created-date range. GET /charges/search. |
pinpayments_get_charge | read | Get charge One charge by token (ch_...), with fees, refunds total, settlement transfer state and chargeback flag. GET /charges/{token}. |
pinpayments_list_charge_refunds | read | List refunds of a charge All refunds issued against one charge. GET /charges/{token}/refunds. |
pinpayments_list_refunds | read | List refunds List all refunds, 25 per page: amount (in the currency's base unit), currency, charge token, status_message, error_message, created_at. GET /refunds. |
pinpayments_get_refund | read | Get refund One refund by token (rf_...). GET /refunds/{token}. |
pinpayments_list_authorisations | read | List authorisations List card authorisations (held funds, not yet captured; they expire after seven days) with amount, amount_captured, amount_remaining and expired flags. GET /authorisations. |
pinpayments_get_authorisation | read | Get authorisation One authorisation by token (auth_...). GET /authorisations/{token}. |
pinpayments_list_customers | read | List customers List stored customers, 25 per page: token, email, first_name, last_name, phone_number, company, notes and the primary card as scheme and last four digits. GET /customers. |
pinpayments_get_customer | read | Get customer One customer by token (cus_...). GET /customers/{token}. |
pinpayments_list_customer_charges | read | List a customer's charges Charges made by one customer. GET /customers/{token}/charges. |
pinpayments_list_customer_cards | read | List a customer's cards Cards stored for one customer, each shown only as scheme, last four digits and issuing country (no token, expiry or address). GET /customers/{token}/cards. |
pinpayments_list_customer_subscriptions | read | List a customer's subscriptions Subscriptions of one customer: state, plan, next billing date, active interval, cancellation time. GET /customers/{token}/subscriptions. |
pinpayments_list_deposits | read | List deposits List deposits made to the account (amount, currency, bank narration, available_at). GET /deposits. |
pinpayments_get_deposit | read | Get deposit One deposit by token (dpo_...). GET /deposits/{token}. |
pinpayments_list_transfers | read | List transfers List transfers (payouts to bank accounts), 25 per page: status, amount, debits/credits, paid_at, reference, line item count, bank account (masked) and recipient. GET /transfers. |
pinpayments_search_transfers | read | Search transfers Search transfers by token, description, amount or recipient details and/or a created-date range. GET /transfers/search. |
pinpayments_get_transfer | read | Get transfer One transfer by token (tfer_...). GET /transfers/{token}. |
pinpayments_list_transfer_line_items | read | List transfer line items The ledger line items that make up one transfer (charge entitlements, fees, refunds, chargebacks). GET /transfers/{token}/line_items. |
pinpayments_list_recipients | read | List recipients List transfer recipients (name, email, masked bank account). GET /recipients. |
pinpayments_get_recipient | read | Get recipient One recipient by token (rp_...). GET /recipients/{token}. |
pinpayments_list_recipient_transfers | read | List a recipient's transfers Transfers paid to one recipient. GET /recipients/{token}/transfers. |
pinpayments_list_disputes | read | List disputes List chargeback disputes: category, status, amount, the disputed charge, evidence_required_by and the relevant evidence types. GET /disputes. |
pinpayments_search_disputes | read | Search disputes Search disputes by status or exact charge token, optionally filtered by status. GET /disputes/search. |
pinpayments_get_dispute | read | Get dispute One dispute by token (dis_...). GET /disputes/{token}. |
pinpayments_get_dispute_activity | read | Get dispute activity The activity feed of one dispute (status changes, ledger entries such as chargeback fees and recoveries). GET /disputes/{token}/activity. |
pinpayments_list_plans | read | List plans List subscription plans: name, amount, currency, interval, trial and setup amounts, subscription counts by state. GET /plans. |
pinpayments_get_plan | read | Get plan One plan by token (plan_...). GET /plans/{token}. |
pinpayments_list_plan_subscriptions | read | List a plan's subscriptions Subscriptions to one plan. GET /plans/{token}/subscriptions. |
pinpayments_list_subscriptions | read | List subscriptions List all subscriptions: state (trial, active, cancelling, cancelled), plan, customer, next_billing_date, active interval, cancelled_at. GET /subscriptions. |
pinpayments_get_subscription | read | Get subscription One subscription by token (sub_...). GET /subscriptions/{token}. |
pinpayments_get_subscription_ledger | read | Get subscription ledger The ledger entries (credits and debits) of one subscription. GET /subscriptions/{token}/ledger. |
pinpayments_list_events | read | List events The account's event log (charge.captured, refund.created, dispute.updated, ...), each with the affected record (cards masked). GET /events. |
pinpayments_get_event | read | Get event One event by token (evt_...). GET /events/{token}. |
pinpayments_usage_status | Usage status (free-tier meter) Report the caller's current usage: the plan, calls used this month, the limit of the plan (the free monthly cap or the Pro fair use limit), remaining, and whether the limit is reached. Read-only; does not count against the meter. | |
pinpayments_request_feature | Request a missing feature Tell usefulapi that the user needs something the Pin Payments tools cannot do yet (a missing tool, field or filter). Call it only when the user asks for something none of the tools can do, and tell the user that you send the request. Do not call it for errors or for normal requests. Do not include personal data, credentials or customer records. Stored with the product name and the client type (for example Claude or Cursor), without the user's account. At most 5 requests per day. Does not count against the meter. | |
pinpayments_upgrade | Upgrade to Pro (unlimited*) Get Pro: unlimited tool calls (fair use limit: 10,000 a month) on Pin Payments (the free tier caps monthly usage). Plans: "monthly" — $9/month; "yearly" — $90/year (2 months free). Cancel any time: Pro then runs to the end of the paid period, so it also suits a one-time job. *A fair use limit applies. For heavy use (near Pro's limit): "plus" or "plus_yearly" — Pro+, $39/month or $390/year, unlimited tool calls (fair use limit: 100,000 a month); an existing Pro subscription changes to Pro+ in place (needs confirm: true; the price difference for the rest of the period is charged at once). Otherwise returns a short link to open in your browser (it opens Stripe Checkout); after payment the account upgrades automatically. Does not count against the meter. | |
pinpayments_cancel_subscription | Cancel the Pro subscription Cancel the caller's Pin Payments Pro subscription at the end of the paid period (no refund for the current period; Pro continues until then, then the free tier applies). Requires confirm: true. Run pinpayments_upgrade later to undo the cancel before the period ends. Does not count against the meter. |
| Plan | Price | Limit |
|---|---|---|
| Free | $0 | 50 tool calls / month |
| Proper API key and environment | $9/mo · $90/yr | Unlimited* |
*Pro fair use limit: 10,000 tool calls a month on this server. For more, write to [email protected].
Pro covers this Pin Payments server only. Subscribe with pinpayments_upgrade (it returns a Stripe Checkout link). Cancel any time with pinpayments_cancel_subscription: Pro continues to the end of the paid period, with no refund for the current period, and running pinpayments_upgrade before then undoes the cancel. Or write to [email protected].
Review charges and their refunds. Check available and pending balances. Reconcile a transfer with its ledger entries. Review disputes and their activity. Inspect a subscription and its ledger. See what you can do for the details.
No. usefulapi is an independent service. It is not affiliated with or endorsed by Pin Payments. The server calls the Pin Payments API with your own Pin Payments access, so it sees only the data that your account can see.
Yes. In Claude, add this server's URL as a custom connector. In ChatGPT, add it as a custom MCP server in Plugins. Then log in once. Cursor, VS Code, Claude Code and Codex work too. See the setup steps.
The login page asks for your Environment and Pin Payments secret API key. See Before you connect for where to find them.
No. Add only the URL. Do not add an Authorization header or an API key to the client config. The server signs you in with OAuth: the login page asks for your Environment and Pin Payments secret API key. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.
The login stores them encrypted in the authorization grant of your connection. The server uses them to call the Pin Payments API for you and to derive a private account id for usage metering. usefulapi does not show them on any page or in any reply. To stop all access, remove the connector and change or delete these credentials in Pin Payments.
All 35 Pin Payments tools are marked read-only.
The Free plan gives 50 tool calls / month. Pro costs $9/mo or $90/yr, with unlimited tool calls (fair use limit: 10,000 tool calls a month), for this Pin Payments server only. Cancel any time: Pro then runs to the end of the paid period. Run pinpayments_usage_status to see how many calls you used.
Ask the AI to run pinpayments_upgrade: it returns a Stripe Checkout link. To cancel, run pinpayments_cancel_subscription. Pro continues to the end of the paid period.
Tell the AI what you wanted to do. It can send the request with pinpayments_request_feature. We store the text with the server name, the type of AI client and the tool you tried, not with your account, and read every request when we plan new tools. You can send up to 5 requests per day.
Any client that supports remote MCP servers (Streamable HTTP) with OAuth login: Claude (web and desktop), Claude Code, ChatGPT, Codex, Cursor, VS Code, Windsurf and others.
This is a Model Context Protocol endpoint — meant to be connected from an AI client, not opened in a browser. An invalid_token response at the URL is the auth gate working as designed; clients authenticate automatically.
Need a tool this server does not have, or a connection to another system? We build custom integrations and MCP servers.