update_payment_method
Update an existing payment method. Use list_payment_methods first to get the method ID.
What update_payment_method does
Updates an existing payment method. Pass only the fields you want to change — every other field is preserved.
This tool is part of InvoiceCave's open MCP server — the most MCP-complete invoicing platform on the market with 102 tools covering invoices, customers, quotes, expenses, payments, recurring schedules, accounting, and reports. Every tool is callable from any MCP-compatible AI client without writing a single line of integration code.
How an AI uses update_payment_method
Use this for partial edits — "change the due date to Net 30", "fix the customer's billing address", "update the line item description". The AI can read the current state with the matching get_* tool first if it needs to confirm what it's editing.
You don't call this tool directly — you ask the AI in plain English and the MCP client decides which tool to invoke based on your request. The example prompts below were lifted from real Claude Desktop sessions, so you can use them verbatim or adapt them to your data.
Parameters
update_payment_method accepts 4 parameters — 1 required, 3 optional. The AI fills these in from your natural-language prompt; you never write them by hand.
| Parameter | Type | Required | Description |
|---|---|---|---|
| methodId | string | required | Payment method ID |
| type | enum | optional | New typebankwisepayoneerpaypalcryptoother |
| label | string | optional | New label |
| details | string | optional | New details text |
Request example
Under the hood, your AI client sends a JSON-RPC 2.0 tools/call request to InvoiceCave's MCP endpoint at https://www.invoicecave.com/api/mcp/mcp. Here's what a update_payment_method call looks like:
{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": {
"name": "update_payment_method",
"arguments": {
"methodId": "met_a1b2c3d4",
"type": "bank",
"label": "example",
"details": "example"
}
}
}You won't write this yourself — it's shown so developers can see exactly what the MCP client generates. The arguments object maps 1:1 to the parameters above. Authentication is handled by the Authorization: Bearer header with your API key.
Example AI prompts
Type any of these into Claude Desktop, Claude Code, or Cursor — InvoiceCave's MCP server will route them to update_payment_method automatically.
“Update this payment method — change the …”
“Fix the details on that payment method.”
Use it in 30 seconds
Related tools
More from the Payment Methods category.
list_payment_methodsList all payment methods (bank accounts, Wise, Payoneer, PayPal, crypto) configured for the organization.
add_payment_methodAdd a new payment method (bank account, Wise, Payoneer, PayPal, crypto, other). Displayed on invoices so clients know where to pay.
delete_payment_methodDelete a payment method. Use list_payment_methods first to get the method ID.
FAQ — update_payment_method
What is update_payment_method?▾
update_payment_method is one of 102 tools in InvoiceCave's MCP server. Updates an existing payment method. Pass only the fields you want to change — every other field is preserved. It's invoked automatically when an AI client like Claude or Cursor decides the user's request maps to this action.
Which AI clients can call update_payment_method?▾
Any MCP-compatible client. We've tested it with Claude Desktop, Claude Code, Cursor, Windsurf, and Codex. The MCP protocol is open, so any AI tool that speaks MCP can call this endpoint with a valid InvoiceCave API key.
Is calling update_payment_method secure?▾
Yes. Every call is authenticated by the API key you mint in the dashboard, scoped to a single organization, rate-limited per key, and recorded in the audit log with source='mcp'. Sensitive fields (SMTP passwords, encryption keys) are never returned to the AI client.
What parameters does update_payment_method take?▾
update_payment_method accepts 4 parameters — 1 required (methodId) and 3 optional. The AI populates these from your plain-English prompt — see the parameter table and request example above.
Does update_payment_method count against any quota?▾
MCP tool calls are unmetered on the free plan up to a generous monthly limit. Once you connect Stripe and start charging your customers, every call still counts against the same per-key rate limit but doesn't add to your bill.
Ready to wire this up?
Free plan — no credit card. 102 tools at your AI's disposal.