Test a card statement and the figures behind it

The contract this flow keeps

The statement carries four independent figures, and each of them is derived from the same transaction list in a different way.

• The dates - a statement date and a payment due date twenty days apart, which is the window the customer plans around.
• The amounts due - a total of 42,618.50 and a minimum of 2,130.93.
• The credit position - a limit of 400,000.00 and available credit of 357,381.50.
• The transactions - a sum that equals the total amount due.

Available credit plus total due equals the limit, and the transaction sum equals the total due. Asserting all four means an inconsistency surfaces as a specific failure instead of a customer discovering it at a card terminal.

The objective in plain English

The card number is asserted in its masked form, which doubles as a check that the statement is not exposing a full card number on a billing page.

---
mode: testing
url: https://my-testing-repo-main.vercel.app/hdfc-clone-app/cards?reset=true
max_steps: 40
tags: [hdfc-bank, banking, cards]
---

# Hindfirst Bank 24.4: Credit card statement view

Catalog objective: open the card statement and verify the due date and minimum due.
Key assertion: the figures render and match the summary.

## Verify the statement header
Verify the statement summary shows "Card number" of "•••• •••• •••• 7712", "Statement date" of "2026-09-05" and "Payment due date" of "2026-09-25".

## Verify the amounts due
Verify "Total amount due" reads "₹42,618.50" and "Minimum amount due" reads "₹2,130.93".

## Verify the credit position
Verify "Credit limit" reads "₹400,000.00" and "Available credit" reads "₹357,381.50".

## Verify the figures agree with the transactions
Verify the transactions table lists "Skyline Airlines" at "₹28,450.00" and that "Sum of transactions" reads "₹42,618.50".

The final step names a specific transaction as well as the sum, so a total that is correct against a wrong transaction list still fails.

Assertion by assertion

From the header to the amounts to the transactions that produce them.

Checking that the minimum due is distinct from the total is worth stating. A minimum that equals the total is a calculation failure that reads as a very expensive month.

Putting it in CI

kane-cli testmd run tests/hdfc-bank/card-statement_test.md

Add a zero balance variant, since a statement with nothing owed is where due dates and minimums tend to render oddly.

Statement pages are a good candidate for a scheduled check rather than a release-time one. Kane CLI in a pipeline covers scheduling, and calling an API in the same run covers reconciling the displayed figures against the billing service.