Test scheduling a card payment against its due date

Failure modes in this flow

The rule is a date comparison, and date comparisons are where off-by-one errors live.

• The amount follows the choice - selecting the statement balance populates $2,318.44.
• A late date is refused - the 30th is rejected against a due date of the 28th, with the reason stated.
• A valid date is accepted - the 26th schedules successfully with a reference.
• The record agrees - amount, type, date and funding account all listed together.

Testing the refusal first is what proves the comparison exists. A payment scheduled two days early tells you nothing about whether a payment two days late would also have been accepted.

Writing the objective

The refusal is asserted with the due date named in the message, because an error that fires without explaining the constraint leaves the customer guessing at a valid date.

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

# Amrex 25.2: Card payment scheduling

Catalog objective: schedule a payment for the statement balance.
Key assertion: the scheduled payment carries the correct amount.

## Choose the statement balance
Choose "Statement balance" and verify "Payment amount" reads "$2,318.44".

## Verify a late date is refused
Set "Payment date" to "2026-09-30", click "Schedule the payment", and verify a red banner says that date is after the 2026-09-28 due date.

## Schedule it for a valid date
Set "Payment date" back to "2026-09-26", click "Schedule the payment", and verify a green banner titled "Payment scheduled" says $2,318.44 is scheduled for 2026-09-26 with reference "PMT-31840".

## Verify the scheduled payment
Verify the "Scheduled payments" card lists "$2,318.44" against "Statement balance · 2026-09-26 · Chaise Bank ••••8841" with a "Scheduled" badge.

The scheduled record names the funding account as well as the amount, so a payment scheduled from the wrong account fails even though the figure is right.

The assertions in detail

A selection, a refusal, a schedule and the record.

A scheduled payment that confirms but does not appear in the list is a payment the customer cannot cancel, which is why both are asserted.

Running it locally

kane-cli testmd run tests/american-express/payment-scheduling_test.md

Add a test on the due date itself, since the boundary is whether that date counts as on time and that is the case the rule is most likely to get wrong.

Date rules shift with billing cycles rather than releases. Running Kane CLI in CI covers catching that drift, and generating the boundary cases covers producing the set.