stripe-dispute

Collect Stripe dispute evidence and generate counter-dispute rebuttal packages.

13|3|Updated May 31, 2026
One-click install
npx skills add https://github.com/enowdev/enowX-Skill --skill stripe-dispute
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: stripe-dispute
Source: https://github.com/enowdev/enowX-Skill/tree/main/skill/skills/stripe-dispute
Command: npx skills add https://github.com/enowdev/enowX-Skill --skill stripe-dispute

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires python3, weasyprint, playwright.

What problem does it solve?

This skill solves the time-consuming and complex process of gathering evidence and submitting rebuttals for Stripe chargebacks, helping businesses recover revenue lost to fraudulent or incorrect disputes.

Core Features & Use Cases

  • Evidence Aggregation: Automatically pulls dispute details, customer history, and login logs from Stripe and your database.
  • Document Generation: Creates professional activity-log PDFs and captures terms-of-service snapshots to present a compelling case to Stripe reviewers.
  • Use Case: When a customer claims a product was not received, use this skill to generate a timeline of their actual product usage and login history to prove the claim is invalid.

Quick Start

Provide the Stripe dispute ID to the skill to begin the automated evidence gathering and rebuttal generation process.

Frequently Asked Questions about stripe-dispute

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate Stripe chargeback evidence collection?

Automate Stripe chargeback evidence collection by integrating Stripe API data with internal database logs to build comprehensive rebuttal packages. Provide the Stripe dispute ID to begin the automated evidence gathering and rebuttal generation process.

What is the best way to generate a chargeback rebuttal for a product not received claim?

The best way to generate a chargeback rebuttal for a product not received claim is to aggregate customer history and login logs from your database. This skill compiles an activity timeline to prove actual product usage and invalidate the dispute.

Do I need database access to submit counter-disputes through Stripe?

Yes, you need secure read-only database access to submit counter-disputes through Stripe effectively. The skill requires database logs to aggregate evidence and build a compelling case alongside your Stripe API credentials.

Can I generate PDF activity logs for Stripe dispute evidence?

Yes, you can generate PDF activity logs for Stripe dispute evidence. The skill uses WeasyPrint and Playwright to create professional activity-log PDFs and capture terms-of-service snapshots for Stripe reviewers.

How does gathering evidence for a Stripe dispute work?

Gathering evidence for a Stripe dispute works by pulling dispute details, customer history, and login logs from Stripe and your internal database. The skill then aggregates this data to build a comprehensive rebuttal package.

What are the limitations of automating Stripe chargeback rebuttals?

Limitations of automating Stripe chargeback rebuttals include the strict requirement for secure read-only database access and valid Stripe API credentials. Without these connections, the skill cannot aggregate logs or generate the necessary PDF evidence.