Test a beneficiary cooling period before a transfer

Failure modes in this flow

A control that blocks by default fails in two directions, and the expensive one is the direction nobody tests.

• The block does not apply - a brand new payee can be paid immediately, which is the fraud window the rule exists to close.
• The block never lifts - a legitimate payee stays unusable and the customer calls the branch.
• The badge and the behaviour disagree - the row says cooling period while the transfer goes through, or the reverse.

The second step is the one most suites omit. It actually attempts the payment during the cooling period and asserts the refusal by its exact wording, rather than trusting the badge on the row.

Writing the objective

The attempt during the cooling period includes the OTP, so the refusal is proven to come from the cooling rule rather than from an incomplete form.

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

# Hindfirst Bank 24.2: IMPS transfer

Catalog objective: add a beneficiary and send IMPS after the cooling period.
Key assertion: the transfer succeeds with a reference id.

## Add the beneficiary
Type "Tom Alvarez" into "Name", type "50100338817001" into "Account number", click "Add beneficiary", and verify an amber banner says the beneficiary cannot be paid for 30 minutes.

## Verify the cooling period blocks payment
Verify the "Tom Alvarez" row carries a "Cooling period" badge, then select "Tom Alvarez" in "Beneficiary", type "481902" into "OTP", click "Send by IMPS", and verify a red banner reads "Tom Alvarez is still in the cooling period and cannot be paid yet."

## Let the cooling period elapse
Click "Simulate the 30 minute cooling period" and verify a green banner says the beneficiary is now active and the "Tom Alvarez" row carries an "Active" badge.

## Send the transfer
Type "481902" into "OTP", click "Send by IMPS", and verify a green card titled "Transfer successful" shows "Reference number" of "IMPS620041", "Beneficiary" of "Tom Alvarez", "Amount" of "₹2,500.00", "Mode" of "IMPS" and a "Success" badge.

The step ceiling is 55, the highest in this set, because the flow adds a payee, fails a transfer, advances time and then transfers successfully.

The assertions in detail

Each step pins one side of the rule.

The reference number on the final card is what the customer quotes if the money does not arrive, so it belongs in the assertion alongside the amount.

Running it locally

kane-cli testmd run tests/hdfc-bank/imps-transfer_test.md

Point this at a sandbox. The flow creates a payee and moves money in whichever environment the front matter names.

Time-dependent rules are awkward to exercise by hand and a natural fit for an automated flow. Running Kane CLI in CI covers scheduling them, and the test.md format covers the step ceiling used here.