Test opening a dispute and the case it creates

The checks that matter

The case is the artifact, and every field recorded on it has to be right for it to be worth anything to the customer.

The decision date is the field most worth asserting and the one most often missing. It is the only thing that tells the customer when to stop waiting, and its absence turns a resolved process into repeated calls.

The flow as a test file

The charge is selected by date, merchant and amount together, which is what stops a dispute being opened against a neighbouring transaction from the same merchant.

---
mode: testing
url: https://my-testing-repo-main.vercel.app/amex-clone-app/disputes?reset=true
max_steps: 45
tags: [american-express, banking, disputes]
---

# Amrex 25.3: Dispute a charge

Catalog objective: start a dispute on a recent charge.
Key assertion: a case is opened with a confirmation.

## Pick the charge
Select the "2026-09-02 - Skyline Airlines - $642.10" charge and verify "Amount" reads "$642.10".

## Give a reason
Choose "I did not receive the goods or services" and type "The flight was cancelled and never rebooked or refunded." into "What happened".

## Open the dispute
Click "Open the dispute" and verify a green card titled "Case opened" appears.

## Verify the case details
Verify the case shows "Case number" of "AMX-58210", "Merchant" of "Skyline Airlines", "Amount" of "$642.10", "Reason" of "I did not receive the goods or services", "Decision by" of "2026-10-16" and a badge reading "Under review".

The reason is chosen from the list and a free text explanation is typed, because the category routes the investigation while the detail informs it.

Step by step coverage

A charge, a reason, the submission and the case.

Asserting the amount on the case as well as the charge catches a dispute opened for a partial figure, which resolves for less than the customer expected.

Adding it to a suite

kane-cli testmd run tests/american-express/dispute-charge_test.md

Add a variant on an older charge that falls outside the dispute window, since the refusal needs to explain itself rather than just fail.

Dispute and support flows are worth covering on both the customer and agent side. Kane CLI as a QA agent covers building that out, and evidence based QA covers keeping proof.