Test disputing a card charge and the case it opens

Failure modes in this flow

The case has to be attached to the right charge and carry the right reason, because the reason determines how it is investigated.

• The charge - merchant and amount, restated after selection so the customer can confirm.
• The reason - a category chosen from a list, which routes the investigation.
• The detail - free text supporting the claim.
• The case - a reference, the merchant, the amount and the reason, all recorded together.

Asserting the reason on the created case, not only at selection, is what catches a dispute filed under a default category. The case exists, the customer is told it was opened, and it is investigated as the wrong kind of claim.

Writing the objective

The charge is restated after selection and asserted before the reason is given, which is the confirmation step that stops a dispute being filed against the wrong transaction.

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

# Chaise Bank 23.5: Card dispute

Catalog objective: dispute a transaction with a reason selection.
Key assertion: the dispute is submitted with a case reference.

## Sign in
Type "priya.nair" into "Username", "Bank2026!" into "Password", click "Sign in", type "483921" into "One-time code", and click "Verify and sign in".

## Choose the charge
Go to https://my-testing-repo-main.vercel.app/chase-clone-app/disputes and choose "Brightline Electronics - $349.99", then verify "Disputing" reads "Brightline Electronics · $349.99".

## Give a reason
Select "I don't recognise this charge" in "Reason" and type "No order was placed with this merchant." into "Extra detail".

## Verify the case reference
Click "Submit dispute" and verify a green banner titled "Dispute submitted" names case "CASE-154800" opened for Brightline Electronics at "$349.99", and the disputes list shows that case with the reason "I don't recognise this charge".

The final assertion checks the confirmation banner and the disputes list, since a case that confirms but is not listed cannot be tracked by the person who raised it.

The assertions in detail

A login, a selection, a reason and the case.

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

Running it locally

kane-cli testmd run tests/chase/card-dispute_test.md

Add a variant disputing an already disputed charge, since duplicate cases are a real operational cost and the refusal needs to be deliberate.

Dispute flows are worth verifying from both the customer and the agent side. Kane CLI as a QA agent covers building that out, and running Kane CLI in CI covers scheduling it.