revclamp_stage_stripe_dispute_ce3

The revclamp_stage_stripe_dispute_ce3 tool is provided by RevClamp MCP Server. Install that server in your AI client and the assistant can call it directly.

Servers exposing revclamp_stage_stripe_dispute_ce3

• RevClamp MCP ServerB · 74HTTP

  From the publisher:Evaluate Visa Compelling Evidence 3.0 (CE 3.0) qualification across 120-to-365-day historical charges (requiring at least 2 settled, non-refunded, non-disputed prior transactions sharing IP address, device fingerprint, or billing email) and assemble a non-destructive Stripe dispute evidence draft with submit hardcoded to false. Executes as a pure read-only staging computation that never auto-submi

  Parameter	Type	Description
  disputeId	string	Stripe dispute identifier being staged (format example: 'du_1QxyzEnterpriseDispute01', default: 'du_mcp_staged_01', max 64 chars).
  customerId	string	Stripe customer identifier associated with the disputed charge (format example: 'cus_enterprise_88', default: 'cus_mcp_enterprise_01', max 64 chars).
  disputeReason	string	Stripe dispute reason code (e.g. 'fraudulent', 'unrecognized', 'subscription_canceled', 'product_unacceptable', 'general'; default: 'fraudulent'; Visa CE 3.0 applies to 'fraudulent' disputes).
  existingUncategorizedText	string	Optional existing merchant evidence notes in Stripe evidence.uncategorized_text or access_activity_log (up to 18,000 chars) to preserve via append-only merge without overwriting.
  existingAccessActivityLog	string	Optional alias for existingUncategorizedText: existing merchant evidence notes in Stripe evidence.access_activity_log (up to 18,000 chars) to preserve via append-only merge.
  disputedTransaction	object	Optional disputed charge snapshot object containing id (e.g. 'ch_disputed_01'), occurredAtSec (Unix seconds), customer_id, email, ip_address, and device_id.
  priorTransactions	array	Optional array of up to 1000 historical Stripe charge objects (each with id, status: 'succeeded', disputed: false, refunded: false, occurredAtSec 120-365 days prior to disputedTransaction, email, ip_a
  usageEvents	array	Optional array of up to 200 customer product/API usage telemetry events (each with occurredAtSec Unix seconds, stripe_customer_id, and event_name) for append-only access_activity_log staging.
  demo	boolean	Optional simulation flag (boolean) to stage a labeled sample dispute preview.

  Install RevClamp MCP Server →

Tool lists are read from the live servers (or, for packaged servers, from their documentation) each morning, so this reflects what they exposed at the last refresh. Search all tools.