Pin Payments MCP by usefulapi

io.usefulapiPublished by usefulapi.ioOfficial publisherv1.7.4Updated Nov 7, 2026

Read Pin Payments charges, refunds, balances, transfers and subscriptions without moving money.

The publisher's own server: Ably MCP by usefulapi

VerifiedStreamable HTTPWeb executableFinanceBusiness & Commerce

Overview

AI-generated overview

Read-only access to Pin Payments records — balances, charges, refunds, transfers, disputes and subscriptions — for an AI assistant.

What you can do
  • Check account balance, deposits and the event log
  • List, search and inspect charges, refunds and card authorisations
  • Browse customers, their stored cards, charges and subscriptions
  • List, search and inspect transfers, recipients and transfer line items
  • Review chargeback disputes, their activity and subscription plans and ledgers
  • Report usage, request a feature, or upgrade and cancel the paid plan
When to use it
Useful when you want an assistant to answer questions about Pin Payments activity — failed charges, available versus pending balance, recent deposits, payouts, disputes or subscription status — without opening the dashboard.
Requirements
A remote MCP endpoint added by URL only; no API key or Authorization header in the client config. Sign-in happens through OAuth, where you enter your Pin Payments secret API key and choose the live or test environment. Network access to the hosted endpoint is required.
Before you install
Pin Payments has no read-only API key, so the secret key you enter could create charges, refunds and bank transfers if misused, even though this server only sends GET requests. Requested payment and customer records are passed to your AI client and its LLM provider. The free tier allows 50 tool calls a month; paid plans are billed through a checkout link, and cancelling gives no refund for the current period. Rotating the key starts a new usage and billing identity.

Installation

In SourceWeft

  1. Open Pin Payments MCP by usefulapi 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/io.usefulapi%2Fpin-payments/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": {
    "pin-payments-by-usefulapi": {
      "type": "http",
      "url": "https://pin-payments.usefulapi.io/mcp"
    }
  }
}

README

Pin Payments MCP by usefulapi

Read payment records at https://pin-payments.usefulapi.io/mcp.

Connect

  • Claude (claude.ai, Desktop): open Customize → Connectors, click + Add → Add custom connector, and paste https://pin-payments.usefulapi.io/mcp.
  • Claude Code: claude mcp add --transport http pin-payments https://pin-payments.usefulapi.io/mcp, then run /mcp to log in.
  • VS Code: Add to VS Code.
  • Cursor and other clients: add the URL as a remote MCP server:
json
{  "mcpServers": {    "pin-payments": {      "url": "https://pin-payments.usefulapi.io/mcp"    }  }}

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, and the login page asks for your Pin Payments credentials.

Step-by-step setup, where to find your credentials, and FAQ: https://usefulapi.io/pin-payments/

Use your Pin Payments secret API key and select its live or test environment. Pin Payments has no read-only API key: the secret can create charges, refunds and bank transfers if misused. This server only sends GET requests and exposes no money-moving tools. Requested payment and customer records pass to your chosen AI client and its LLM provider. Revoke or replace the key in Pin Payments to stop vendor access. Rotating the key starts a new usage and billing identity.

Tools

ToolTypeWhat it does
pinpayments_get_balancereadGet balance
pinpayments_list_chargesreadList charges
pinpayments_search_chargesreadSearch charges
pinpayments_get_chargereadGet charge
pinpayments_list_charge_refundsreadList refunds of a charge
pinpayments_list_refundsreadList refunds
pinpayments_get_refundreadGet refund
pinpayments_list_authorisationsreadList authorisations
pinpayments_get_authorisationreadGet authorisation
pinpayments_list_customersreadList customers
pinpayments_get_customerreadGet customer
pinpayments_list_customer_chargesreadList a customer's charges
pinpayments_list_customer_cardsreadList a customer's cards
pinpayments_list_customer_subscriptionsreadList a customer's subscriptions
pinpayments_list_depositsreadList deposits
pinpayments_get_depositreadGet deposit
pinpayments_list_transfersreadList transfers
pinpayments_search_transfersreadSearch transfers
pinpayments_get_transferreadGet transfer
pinpayments_list_transfer_line_itemsreadList transfer line items
pinpayments_list_recipientsreadList recipients
pinpayments_get_recipientreadGet recipient
pinpayments_list_recipient_transfersreadList a recipient's transfers
pinpayments_list_disputesreadList disputes
pinpayments_search_disputesreadSearch disputes
pinpayments_get_disputereadGet dispute
pinpayments_get_dispute_activityreadGet dispute activity
pinpayments_list_plansreadList plans
pinpayments_get_planreadGet plan
pinpayments_list_plan_subscriptionsreadList a plan's subscriptions
pinpayments_list_subscriptionsreadList subscriptions
pinpayments_get_subscriptionreadGet subscription
pinpayments_get_subscription_ledgerreadGet subscription ledger
pinpayments_list_eventsreadList events
pinpayments_get_eventreadGet event
pinpayments_usage_statusmetaUsage status (free-tier meter)
pinpayments_request_featuremetaRequest a missing feature
pinpayments_upgrademetaUpgrade to Pro or Pro+
pinpayments_cancel_subscriptionmetaCancel the Pro subscription

read tools are read-only; write tools mutate data (clients should confirm them); meta tools report usage, manage your subscription or send a feature request.

Pricing

PlanPriceLimit
Free$050 tool calls / month
Pro (per API key and environment)$9/mo or $90/yr (2 months free)Unlimited*

*Pro has a fair use limit of 10,000 tool calls a month on this server. For more, write to [email protected].

Pro covers this 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].

License

Independent integration by usefulapi. See Terms and Privacy.

Source: servers/pin-payments/README.md at commit 4046075

Tools

35

pinpayments_get_balance

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.

Takes no parameters.

pinpayments_list_charges

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.

Parameterspage

pinpayments_search_charges

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.

Parameterspagesortqueryend_datedirectionstart_date

pinpayments_get_charge

Get charge

One charge by token (ch_...), with fees, refunds total, settlement transfer state and chargeback flag. GET /charges/{token}.

Parameterscharge_tokenrequired

pinpayments_list_charge_refunds

List refunds of a charge

All refunds issued against one charge. GET /charges/{token}/refunds.

Parameterspagecharge_tokenrequired

pinpayments_list_refunds

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.

Parameterspage

pinpayments_get_refund

Get refund

One refund by token (rf_...). GET /refunds/{token}.

Parametersrefund_tokenrequired

pinpayments_list_authorisations

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.

Parameterspage

pinpayments_get_authorisation

Get authorisation

One authorisation by token (auth_...). GET /authorisations/{token}.

Parametersauthorisation_tokenrequired

pinpayments_list_customers

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.

Parameterspage

pinpayments_get_customer

Get customer

One customer by token (cus_...). GET /customers/{token}.

Parameterscustomer_tokenrequired

pinpayments_list_customer_charges

List a customer's charges

Charges made by one customer. GET /customers/{token}/charges.

Parameterspagecustomer_tokenrequired

pinpayments_list_customer_cards

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.

Parameterspagecustomer_tokenrequired

pinpayments_list_customer_subscriptions

List a customer's subscriptions

Subscriptions of one customer: state, plan, next billing date, active interval, cancellation time. GET /customers/{token}/subscriptions.

Parameterspagecustomer_tokenrequired

pinpayments_list_deposits

List deposits

List deposits made to the account (amount, currency, bank narration, available_at). GET /deposits.

Parameterspage

pinpayments_get_deposit

Get deposit

One deposit by token (dpo_...). GET /deposits/{token}.

Parametersdeposit_tokenrequired

pinpayments_list_transfers

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.

Parameterspage

pinpayments_search_transfers

Search transfers

Search transfers by token, description, amount or recipient details and/or a created-date range. GET /transfers/search.

Parameterspagesortqueryend_datedirectionstart_date

pinpayments_get_transfer

Get transfer

One transfer by token (tfer_...). GET /transfers/{token}.

Parameterstransfer_tokenrequired

pinpayments_list_transfer_line_items

List transfer line items

The ledger line items that make up one transfer (charge entitlements, fees, refunds, chargebacks). GET /transfers/{token}/line_items.

Parameterspagetransfer_tokenrequired

pinpayments_list_recipients

List recipients

List transfer recipients (name, email, masked bank account). GET /recipients.

Parameterspage

pinpayments_get_recipient

Get recipient

One recipient by token (rp_...). GET /recipients/{token}.

Parametersrecipient_tokenrequired

pinpayments_list_recipient_transfers

List a recipient's transfers

Transfers paid to one recipient. GET /recipients/{token}/transfers.

Parameterspagerecipient_tokenrequired

pinpayments_list_disputes

List disputes

List chargeback disputes: category, status, amount, the disputed charge, evidence_required_by and the relevant evidence types. GET /disputes.

Parameterspagesortdirection

pinpayments_search_disputes

Search disputes

Search disputes by status or exact charge token, optionally filtered by status. GET /disputes/search.

Parameterspagesortquerystatusdirection

pinpayments_get_dispute

Get dispute

One dispute by token (dis_...). GET /disputes/{token}.

Parametersdispute_tokenrequired

pinpayments_get_dispute_activity

Get dispute activity

The activity feed of one dispute (status changes, ledger entries such as chargeback fees and recoveries). GET /disputes/{token}/activity.

Parametersdispute_tokenrequired

pinpayments_list_plans

List plans

List subscription plans: name, amount, currency, interval, trial and setup amounts, subscription counts by state. GET /plans.

Parameterspage

pinpayments_get_plan

Get plan

One plan by token (plan_...). GET /plans/{token}.

Parametersplan_tokenrequired

pinpayments_list_plan_subscriptions

List a plan's subscriptions

Subscriptions to one plan. GET /plans/{token}/subscriptions.

Parameterspageplan_tokenrequired

pinpayments_list_subscriptions

List subscriptions

List all subscriptions: state (trial, active, cancelling, cancelled), plan, customer, next_billing_date, active interval, cancelled_at. GET /subscriptions.

Parameterspage

pinpayments_get_subscription

Get subscription

One subscription by token (sub_...). GET /subscriptions/{token}.

Parameterssubscription_tokenrequired

pinpayments_get_subscription_ledger

Get subscription ledger

The ledger entries (credits and debits) of one subscription. GET /subscriptions/{token}/ledger.

Parameterspagesubscription_tokenrequired

pinpayments_list_events

List events

The account's event log (charge.captured, refund.created, dispute.updated, ...), each with the affected record (cards masked). GET /events.

Parameterspage

pinpayments_get_event

Get event

One event by token (evt_...). GET /events/{token}.

Parametersevent_tokenrequired

Version history

10
  1. v1.7.4LatestNov 7, 2026
  2. v1.6.3Nov 5, 2026
  3. v1.6.2Nov 5, 2026
  4. v1.6.1Nov 4, 2026
  5. v1.6.0Nov 3, 2026
  6. v1.5.1Nov 3, 2026
  7. v1.4.0Nov 1, 2026
  8. v1.2.0Oct 31, 2026
  9. v1.1.0Oct 31, 2026
  10. v1.0.2Oct 30, 2026

Score

100% 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
  • Documentation15 pts
  • License10 pts

Other Usefulapi integrations