Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIDeepSeekDeepSeekMuseMuse+22 more

    Stripe Chargeback Evidence Packet: Win-or-Accept Decision, Rebuttal & Visa CE 3.0 Check

    1

    Turns a Stripe dispute and your order records into a counter-or-accept decision, a reason-matched evidence map, a short rebuttal, a limit-checked file plan and a staged (submit=false) API payload.

    $1

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    Stripe Chargeback Evidence Packet: Win-or-Accept Decision, Rebuttal & Visa CE 3.0 Check

    Stripe Chargeback Evidence Packet: Win-or-Accept Decision, Rebuttal & Visa CE 3.0 Check

    Example session with this skill installed

    Stripe dispute du_test_bf26: reason fraudulent, Visa network reason code 10.4, USD 89 Annual Pro plan (digital SaaS) bought 2026-11-27, due_by 2026-12-08 23:59 UTC. Customer Sam Rivera, sam.rivera@example.com, purchase IP 203.0.113.24, device ID d-7781. Logged in 8 minutes after payment and exported 14 images; logged in again 2 Dec. Two earlier undisputed payments on the same card: 17 Mar 2026 and 2 May 2026, same IP, device and email. One more payment on 30 Oct 2026 from a different IP. Receipt PDF (1 page). Customer never contacted support.

    • Read your context and instructions
    • Compiled the stripe chargeback evidence

    Decision: Counter. Fraud claim contradicted by matching device/IP history and post-purchase use. 182 h left to due_by.

    Claim vs. proof

    ClaimOur factField
    Payment unauthorisedSame IP + device as 2 earlier undisputed paymentsenhanced_evidence.visa_compelling_evidence_3
    Didn't use the serviceLogin 8 min after payment, 14 exports, login 2 Decaccess_activity_log
    Unaware of chargeReceipt emailed at purchasereceipt (file)

    Rebuttal (743 chars): "Sam Rivera purchased the Annual Pro plan (order 88412) on 27 Nov 2026 for USD 89 using a Visa card. Claim: unauthorised payment. Facts: (1) The purchase IP and device ID match two earlier undisputed payments on the same card (17 Mar and 2 May 2026)… Therefore the claim that the payment was unauthorised is not accurate."

    CE 3.0: Qualified. ch_prior_1 (255 days) and ch_prior_2 (209 days) match main:ip + main:device (+ email). ch_prior_3 (28 days) excluded: under 120 days.

    Checker: 9 checks, RESULT: PASS (exit 0). 1,017 text chars, 1 page, 84 KB.

    Staged calls: POST /v1/files purpose=dispute_evidence → POST /v1/disputes/du_test_bf26 with submit=false.

    Prevention: make the statement descriptor match the app name; send a renewal reminder before annual charges.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    The problem

    Black Friday and Cyber Monday orders turn into Stripe chargebacks a few weeks later. You get one submission, a hard due_by deadline (usually 7–21 days), and an issuer reviewer who skims. Most responses lose for avoidable reasons: arguing a refund policy against a "not received" claim, uploading the whole terms of service, putting two files in one evidence slot, going over the size or page limit, or missing the Visa Compelling Evidence 3.0 path on a fraud dispute.

    What it does

    • Triage: counter or accept, using Stripe's own rules (Visa 10.5 has no recourse, inquiries can't be "accepted" away, the 500 USD compliance-dispute fee, fee refunds on a win).
    • Evidence map: for each Stripe reason (fraudulent, unrecognized, product_not_received, product_unacceptable, subscription_canceled, credit_not_processed, duplicate, general) and product type, lists exactly which of the 27 evidence fields to fill and the fact each one proves.
    • Rebuttal letter: a neutral, dated, under-1,500-character uncategorized_text where every claim points to an attached field.
    • File plan: one file per field, PDF/JPEG/PNG, within 4.5 MB combined, under 50 pages (19 for Mastercard), 150,000 text characters.
    • Visa CE 3.0 check: 2+ prior undisputed payments, 120–364 days old, matching 2 main or 1 main + 1 secondary elements.
    • Checker script: standard-library Python that returns PASS/WARN/FAIL with exit codes 0/1/2 before anything is sent.
    • Staged API calls: file upload with purpose=dispute_evidence and dispute update with submit=false, so a human presses the final button.

    Why this beats prompting it yourself

    General models mix up field names, forget that submit defaults to true, invent CE 3.0 rules and write long emotional letters. Every limit and rule here was checked against Stripe's documentation on 16 Nov 2026 and is cited inside the skill.

    Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for E-commerce.

    Covers Stripe card disputes and Stripe's field names only; PayPal, Adyen, Braintree and Shopify Payments use different forms (the reasoning transfers, the fields don't). It does not submit evidence for you: it stages with submit=false and leaves the final, irreversible submit to you. Page limits can vary per dispute, so Stripe's dispute_evidence_page_limit_exceeded error is the final word. It cannot predict or guarantee an outcome; issuers decide. Not legal advice. Facts checked 16 Nov 2026.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before buying a skill.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scan

    Security scan passed 1 day ago

    Accounts
    Stripe account with a dispute
    Software
    Python 3.9+ (for the checker)
    Optional
    Stripe secret key (to stage via API)

    Permissions

    Allowed Hosts

    api.stripe.com (only if you run the staged curl commands yourself)

    File Scopes

    case.json
    and
    evidence
    files
    you
    provide
    skill
    scripts/
    folder

    The checker is standard-library Python, makes no network calls and only reads the case file you pass it. API calls use your own $STRIPE_SECRET_KEY and always stage with submit=false.

    Listed1 day ago

    What's inside

    Frequently Asked Questions

    All eight Stripe categories (fraudulent, unrecognized, product not received, product unacceptable, subscription canceled, credit not processed, duplicate, general) plus Visa/Mastercard compliance disputes, for physical goods, digital products and offline services.

    No. It builds the packet and stages it with submit=false. Submission is one-shot and final, so you review it and press submit yourself in the Dashboard or with one last API call.

    Every limit (4.5 MB, under 50 pages, 19 pages for Mastercard, 150,000 characters, one file per field) and the Visa CE 3.0 criteria were checked against Stripe's documentation on 16 Nov 2026, and the sources are listed inside the skill.

    Stripe's guide explains the rules; this skill applies them to your case: it decides counter vs accept, maps your actual records to the right fields, writes the letter, runs a PASS/FAIL checker and produces the exact API calls.

    No tool can promise that. Stripe's own estimates top out around 60% for the strongest cases. This skill removes the avoidable reasons for losing and tells you when accepting is the better call.

    New in E-commerce