Test a wallet withdrawal with its minimum and its fee

The contract this flow keeps

Three figures move and they are all different, which is the source of nearly every complaint about withdrawal fees.

• The amount requested - 1,000 rupees.
• The fee - 20 rupees, which is two percent of the request.
• The amount credited - 980 rupees reaching the bank.
• The wallet debit - the full 1,000, taking the balance from 4,820 to 3,820.

The wallet is debited by the gross amount while the bank receives the net. Both are correct and a customer who only reads one of them will believe they have been short changed, which is exactly why both belong in the assertion.

The objective in plain English

The minimum is tested before the valid amount, which proves the rule exists rather than inferring it from a successful transfer.

---
mode: testing
url: https://my-testing-repo-main.vercel.app/paytm-clone-app/wallet?reset=true
max_steps: 40
tags: [paytm, fintech, wallet]
---

# Paytem 20.4: Wallet to bank

Catalog objective: transfer the wallet balance to the linked bank.
Key assertion: the wallet is debited and the transfer shows as initiated.

## Verify the starting balance
Verify "Paytem Wallet" reads "₹4,820.00" and "Linked bank" reads "HDFB Bank ••••8841".

## Verify the minimum is enforced
Type "50" into "Amount", click "Transfer to bank", and verify an error reads "Minimum transfer is ₹100.00."

## Set a valid amount
Replace "Amount" with "1000" and verify "Transfer fee (2%)" reads "₹20.00" and "Credited to bank" reads "₹980.00".

## Transfer and verify the debit
Click "Transfer to bank" and verify a green banner titled "Transfer initiated" says "₹980.00" will reach the bank after a fee of "₹20.00" and the wallet is now "₹3,820.00".

The fee and the credited amount are asserted before the transfer is submitted, so the customer sees the deduction while deciding rather than discovering it afterwards.

Assertion by assertion

A baseline, a refusal, a quote and a transfer.

Naming the linked bank in the first step is a cheap assertion that prevents the whole flow running against a destination the customer did not expect.

Putting it in CI

kane-cli testmd run tests/paytm/wallet-to-bank_test.md

Add a withdrawal of the entire balance, since the boundary where a fee cannot be covered is where these flows break.

Withdrawal rules are the kind of thing changed by a pricing decision rather than an engineering one. Deriving a suite from written requirements covers keeping the figures tied to a source, and checking before a pull request covers catching the change.