Test cases for bank fund transfer: IMPS, NEFT and RTGS

1. Open Add beneficiary and enter the account number twice
2. Enter the IFSC and check the bank and branch shown
3. Enter a nickname, submit and enter the OTP sent by SMS

Expected: The beneficiary appears in the list with the bank-registered name and a masked account number. Its status shows whether it is active or still in the cooling period.

Why a real phone: The beneficiary OTP arrives by SMS over the carrier network to a real SIM.

1. Enter a valid test account number and IFSC
2. Wait for the name lookup to finish
3. Compare the returned name with the expected account holder

Expected: The account holder's name as the bank holds it appears before the user can save or send. Save stays disabled while the lookup is running.

1. Add a new beneficiary and confirm with the OTP
2. Open the beneficiary list and the new beneficiary's details
3. Start a transfer to it

Expected: The new beneficiary is marked as in its cooling period, with when it becomes fully active or the reduced limit that applies. The transfer screen shows the same information.

1. Pick an active beneficiary and enter ₹10
2. Choose IMPS, review the confirmation screen and authorise as the app asks
3. Open the result screen and the account balance

Expected: The result shows Success with a reference number and the IST time. The balance is ₹10 lower.

1. Pick an active beneficiary and choose NEFT
2. Send ₹10 and note the expected credit time shown
3. Open the transaction's status page until it changes

Expected: The status moves from In process or Pending to Credited or Completed, and each change shows its time. The reference number stays the same throughout.

1. Enter a small amount and open the transfer mode options
2. Enter an amount the app marks as eligible for RTGS
3. Send it by RTGS and open the receipt

Expected: The options list only the modes the bank allows for each amount, each with its expected credit time. The RTGS receipt shows the mode and its reference number.

1. Start a transfer that the app protects with an OTP
2. Wait for the SMS and enter the OTP
3. Submit before the OTP timer ends

Expected: The OTP arrives on the registered number and the transfer completes with a reference number. The SMS names the amount or the beneficiary, so the user knows what they are approving.

Why a real phone: OTP delivery depends on the carrier network and a real SIM.

1. Set up a one-time transfer for a future date
2. Set up a monthly transfer with an end date
3. Open the scheduled transfers list

Expected: Both appear with the beneficiary, amount, frequency and next run date in IST. Each one runs on its date and appears in history with a reference number.

1. Open a completed transfer from history
2. Tap Download or Share and send it to a messaging app
3. Open the shared file

Expected: The receipt shows the amount, mode, reference number, beneficiary name, masked account number, IFSC and IST date and time. The shared copy matches the screen.

1. Enter an IFSC with ten characters
2. Enter an 11-character IFSC whose fifth character is a letter
3. Enter one with a space or a symbol

Expected: Each one shows an inline format error and no bank or branch name. The beneficiary cannot be saved.

1. Enter a correctly formatted IFSC from a branch that has merged or closed
2. Try to save the beneficiary

Expected: The app says the IFSC is not valid for transfers or points to the new branch. It does not save a beneficiary that will fail later.

1. Enter the account number, then re-enter it with one digit changed
2. Fix the digit and continue

Expected: A mismatch error appears and Save stays disabled until both entries match.

1. Enter a beneficiary name that differs from the account holder's
2. Enter the account number and IFSC and wait for the lookup

Expected: The app shows the bank's name for the account next to what the user entered. It asks the user to confirm before saving or sending.

1. Enter a valid IFSC with an account number that does not exist
2. Repeat with a test account that is closed or frozen

Expected: The app says the account could not be verified and does not let the user send money to it without a clear warning. No OTP is sent.

1. Add a new beneficiary and stay within its cooling period
2. Try sending an amount above what the app allows during that period

Expected: The app blocks the transfer before the OTP step and says when the full limit becomes available. No money moves.

1. To an active beneficiary, enter an amount above the configured per-transfer limit
2. Send transfers until the configured daily limit is used, then try one more

Expected: Each attempt above a limit is blocked before the OTP step, with the limit and the amount still available. No money moves.

1. Enter an amount higher than the available balance
2. Tap Send

Expected: The app shows insufficient balance before or at the confirmation step, and no OTP is sent.

1. Start a transfer and enter a wrong OTP
2. Keep entering wrong OTPs until the app stops accepting attempts

Expected: Each wrong OTP shows an error, with the attempts left if the app shows them. After the last attempt the transfer is cancelled and no money moves.

1. Fill in a transfer and reach the confirmation screen
2. Tap Confirm twice very quickly
3. Complete authorisation and open history

Expected: Only one OTP request or authorisation screen appears and only one transfer is made. History shows a single entry.

1. Use a test setup where the beneficiary's bank does not reply in time
2. Send by IMPS and open the result screen
3. Check the status again later

Expected: The result shows Pending with the reference number and advice not to send again. It later turns to Success, or to Failed with the money back in the account.

1. Send by NEFT to a test account set up to return credits
2. Open the transaction status after the return
3. Check the account balance

Expected: The status shows Returned with a reason, and the amount is back in the account under the same reference. No second transfer is triggered.

1. Schedule a monthly transfer for a near date in the test environment
2. Bring the balance below the amount before that date
3. Check the scheduled list and notifications after the date

Expected: The run shows Failed with the insufficient balance reason, and the user is told. The next monthly run stays scheduled.

1. Open a scheduled transfer and change its amount and date
2. Cancel another scheduled transfer
3. Let both dates pass

Expected: The edited transfer runs with the new amount on the new date, and the cancelled one does not run. The scheduled list shows both changes at once.

1. Enter 100000, then 1000000, then 10000000 as the amount
2. Look at the amount field and the confirmation screen

Expected: The amounts show as ₹1,00,000, ₹10,00,000 and ₹1,00,00,000. Where the app shows the amount in words, it reads one lakh, ten lakh and one crore.

1. Submit the OTP for a transfer
2. Turn on airplane mode within a second
3. Turn the network back on and open the transaction status
4. Repeat, submitting just as you walk into a lift or basement

Expected: The app shows Pending or Checking, not Failed, then the final status with the reference number. It does not offer to send again until the status is final.

Why a real phone: Real dead zones lose packets slowly; an emulator's network cut is instant and clean.

1. Start a transfer in a weak-signal area so the OTP SMS is delayed
2. Tap Resend when the app allows it
3. Enter the older OTP first, then the newer one

Expected: The older OTP is rejected or the app says which code to use, and the newer OTP completes the transfer. Only one transfer is made.

Why a real phone: SMS delay depends on weak coverage on a real carrier network.

1. On a 3–4 GB RAM phone, start a transfer and reach the OTP screen
2. Switch to the messages app, then open the camera and a game
3. Return to the banking app

Expected: The app asks for login again or shows the transfer ready to restart. No transfer is made without a fresh OTP, and history shows no half-made entry.

Why a real phone: Low-RAM phones and OEM memory managers kill apps left in the background.

1. Reach the OTP screen for a transfer and type two digits
2. Answer an incoming call, then end it
3. Return to the app

Expected: The OTP screen is still there with its timer, or the app says the OTP expired and offers Resend. No transfer is made without the full OTP.

Why a real phone: Needs a real incoming SIM call during the OTP screen.

1. On Wi-Fi, enter the account number and IFSC
2. Turn Wi-Fi off while the name lookup is running
3. Wait for the lookup on mobile data

Expected: The lookup finishes on mobile data or shows a retry, and Save stays disabled until a name is returned.

Why a real phone: Needs a real SIM on Jio, Airtel or Vi for the handover.

1. Keep the bank-registered number in SIM 2 and mobile data on SIM 1
2. Add a beneficiary and wait for the OTP

Expected: The OTP arrives on SIM 2 and can be entered or auto-filled before it expires.

Why a real phone: Needs two physical SIMs receiving SMS on a real dual-SIM phone.

1. Start a transfer in an app that offers OTP auto-fill
2. Allow the prompt to read the SMS
3. Repeat, declining the prompt and typing the OTP

Expected: The allowed prompt fills the OTP field. When the prompt is declined, typing the OTP by hand still works.

Why a real phone: OTP auto-read depends on real SMS delivery and the phone's SMS handling.

1. On a Xiaomi, Vivo or Oppo phone, keep the default battery settings
2. Make a transfer, then let a scheduled transfer run while the app is closed
3. Check the SMS inbox and notifications

Expected: A debit SMS arrives for both transfers. The app notification for the scheduled run arrives, or appears when the app next opens.

Why a real phone: OEM battery savers on Xiaomi, Vivo and Oppo delay or drop app notifications.

1. On a 5-inch phone, pick a beneficiary with a long name
2. Enter an amount and open the confirmation screen

Expected: The full name, masked account number, IFSC, mode and amount are readable. The Confirm button can be reached without hiding any of them.

1. Add a beneficiary
2. Check the SMS inbox and the email of the registered account

Expected: An alert arrives naming the new beneficiary or a masked account number, and says what to do if the user did not add it.

Why a real phone: Alert SMS delivery depends on the carrier network and a real SIM.

1. Open the transfer confirmation screen and try a screenshot
2. Open the OTP screen and try the screenshot gesture and screen recording

Expected: Screenshots and recordings are blocked or come out blank on both screens.

Why a real phone: OEM screenshot gestures and recorders on Android skins must respect the secure flag.

1. Open the beneficiary list
2. Open a receipt and share a copy of it

Expected: The list and the shared receipt show only the last few digits of the beneficiary's account number.

1. Start adding a beneficiary and leave the app idle past the configured session timeout
2. Return and tap Submit
3. Log in again and open the beneficiary list

Expected: The app asks the user to log in again, and no beneficiary is saved from the expired session. The list shows no half-added entry.

1. Turn on TalkBack and open the add beneficiary form
2. Type an account number and IFSC, then move focus over each field
3. Open the confirmation screen

Expected: Account numbers and the IFSC are read digit by digit or in groups, not as one large number. Every field has a spoken label.

1. Switch the app language to Hindi
2. Add a beneficiary with a nickname typed on a Hindi keyboard
3. Type the account number using the Hindi keyboard's own digits

Expected: Labels, errors and statuses appear in Hindi, and the Hindi nickname shows correctly in the list. Devanagari digits in the account number field are either accepted as the same number or rejected with a message.

1. Set font size and display size to the maximum
2. Add a beneficiary and make a transfer

Expected: All labels, the amount and the Confirm button stay visible without cut-off text.