MCP servers that can list payments
4 verified servers expose a tool that can list payments and transactions
Every charge leaves a record, and an agent reconciling revenue, investigating a dispute, or reporting on sales reads those records. Listing payments returns the transactions on the account, so the agent works from what actually moved rather than what was supposed to.
These verified servers let an agent list the payments or transactions on a billing platform.
Stripe
Stripe
Stripe's official MCP server lets agents create customers, payment links, invoices, and read balances.
list_payment_intents
Stripe's list_payment_intents returns the PaymentIntents on the account, the transaction record behind reconciliation or investigating a charge.
Polar
Polar
Polar's official remote server lets agents manage products, subscriptions, orders, customers, and revenue metrics on the merchant-of-record platform.
polar_payments_list
On Polar, polar_payments_list returns the payments collected, for businesses billing through its merchant-of-record platform.
Paddle
Paddle
Paddle's official MCP server lets agents manage the product catalog, billing, subscriptions, and reports through the Paddle Billing API.
list_transactions
Paddle's list_transactions returns the account's transactions, the ledger an agent reconciles SaaS revenue against.
PayPal
PayPal
PayPal's official remote MCP server brings invoicing, orders, and payments into agentic commerce.
list_transaction
For payments collected through PayPal, list_transaction returns transactions with pagination and filtering.
What to know
A payment list is the ledger an agent reads to reconcile. Which charges succeeded, which failed, what came in this week, all of it is in the transaction record, usually filterable by status or date. The processors name it differently, Stripe lists PaymentIntents, Polar lists payments, Paddle and PayPal list transactions, but the read is the same: the record of money that moved. From the list an agent totals revenue, finds a specific charge by id, or pulls the failures to investigate.
Payment records accumulate and settle over time, so the list is worth re-reading for the latest state. What an agent benefits from holding is its working set, the charges it already reconciled or flagged, so a follow-up picks up the unresolved ones instead of re-scanning the whole ledger.
Questions
- Payments, transactions, or PaymentIntents?
- Different names for the same record across processors. Stripe calls them PaymentIntents, Paddle and PayPal call them transactions, Polar calls them payments. All are the ledger of money that moved on the account. An agent lists them to reconcile, total revenue, or find a specific charge.
- Can an agent filter to failed payments?
- Usually, yes. The list tools take filters for status and date, so an agent can pull just the failed or pending charges, or everything in a window. That is the common starting point for reconciliation or chasing down a payment problem.