Builds your dispute rebuttal package — structured, bot-readable, and network-agnostic.
BRAND
Terms & Conditions
EMPTY
Refund Policy
EMPTY
Cancellation Policy
EMPTY
Paste the full dispute/chargeback notification from your processor or bank. Kounter will auto-extract the reason code, cardholder, amount, order number, and tracking data.
AUTO-DETECTED FROM NOTIFICATION
Enter manually or let Kounter detect it from your communication and facts below.
DETECTED:
Cardholder name, order #, disputed amount
Paste all customer messages, emails, portal logs. The AI mines this for self-defeating admissions and highlight suggestions.
One fact per line. Dates, carrier events, tracking numbers, fulfillment steps.
Describe exactly where and how the policy was shown at checkout. For most platforms: a required checkbox the cardholder must tick before proceeding (e.g. "I agree to [Brand]'s terms and privacy policy"). Screenshot of this screen is your strongest evidence.
List each billing reminder or pre-charge notification sent to the cardholder. Date, type (email/SMS), and subject line.
Was the subscription active, paused, or restarted by the cardholder? Include who initiated the restart if applicable.
When did the cardholder first request cancellation vs. when was the charge? Leave blank if no cancellation was ever requested before the dispute.
⚖️ Dispute Rebuttal Package
STEP 1Rebuttal Anchor — Product / Service Description
PROCESSOR REASON SELECTION
PRODUCT OR SERVICE DESCRIPTION
STEP 2Policy Disclosure Fields
STEP 3 — Attach to SubmissionForensic Audit Report
🖍️ Red Box ProtocolSuggested Highlights — From Customer Communication
Evidence IndexUpload Checklist
Add Brand
Used in rebuttal headers and legal citations.
Identity
What customers see. Used in dispute headers and rebuttal body.
Registered legal entity. Used in Legal Authority section. Leave blank if same as brand.
—
Policy URLs
Policy Disclosure at Signup
Used in Section 1 of every audit report. Keep it short — just how and when it was shown.