Power Your Software Testing with AI Agents and Cloud
The Native AI-Agentic Cloud Platform to Supercharge Quality Engineering. Test Intelligently and Ship Faster.
- TestMu AI (Formerly LambdaTest)
- /
- Use Cases
- /
- Test a bank transfer and its reference number
Test a bank transfer and its reference number
Sign in, pick a recipient and a source account, send, and confirm the reference number that makes it traceable.
Published on:
A transfer inside a banking app is the one flow where the customer has the most to lose and the least ability to undo. The reference number is what makes it traceable afterwards, which is why it belongs in the assertion.
This use case sends a transfer on the Chaise Bank clone, through the full login.
The checks that matter
Choosing which account the money comes from is as important as choosing where it goes, and it is the part most transfer tests leave on a default.
- The recipient - selected from saved contacts and restated before sending.
- The source account - chosen explicitly rather than accepting whichever is default.
- The memo - free text carried through to the confirmation.
- The reference number - the value the customer quotes if the money does not arrive.
Asserting the source account matters because a transfer taken from a savings account rather than checking can overdraw one and breach a withdrawal limit on the other, while the recipient and amount both look perfectly correct.
Note: A full login followed by a transfer runs as one flow, so authentication does not have to be a separate test with its own setup. Start on TestMu AI. Start for free
The flow as a test file
The login is compressed into a single step because it is setup rather than subject, which keeps the three transfer steps separately attributable.
---
mode: testing
url: https://my-testing-repo-main.vercel.app/chase-clone-app?reset=true
max_steps: 50
tags: [chase, banking, payments]
---
# Chaise Bank 23.2: Zelly transfer
Catalog objective: send a Zelly payment to a saved contact.
Key assertion: a confirmation with a reference number is shown.
## Sign in
Type "priya.nair" into "Username", "Bank2026!" into "Password", click "Sign in", type "483921" into "One-time code", and click "Verify and sign in".
## Open Zelly and choose a recipient
Go to https://my-testing-repo-main.vercel.app/chase-clone-app/zelle and choose "Tom Alvarez", then verify "Sending to" reads "Tom Alvarez".
## Send the money
Select the Total Checking account in "From account", type "120" into "Amount", type "Half of the tickets" into "Memo", and click "Send money".
## Verify the confirmation and reference number
Verify a green banner titled "Money sent" says "$120.00" was sent to "Tom Alvarez", with "Reference number" of "ZL-154800", "Amount" of "$120.00" and "Memo" of "Half of the tickets".The confirmation is asserted for the reference number, the amount and the memo together, so a transfer confirmed without a traceable reference fails.
Step by step coverage
Authentication, selection, the send and the record.
| Step | What it proves |
|---|---|
| Sign in | The account is reachable through the full two-step login |
| Open the transfer page and choose a recipient | A saved contact is selectable and restated |
| Send the money | Source account, amount and memo are all set explicitly |
| Verify the confirmation and reference number | Recipient, amount, memo and a reference number are all recorded |
The step ceiling is raised to 50 to accommodate the login, which is the cost of testing anything behind a two-factor gate.
Adding it to a suite
kane-cli testmd run tests/chase/zelle-transfer_test.mdAdd a transfer that exceeds the available balance, since the refusal is what protects the customer from a fee.
Flows behind a login benefit from a saved browser profile. The Kane CLI introduction covers profiles, and evidence based QA covers keeping proof of a money movement.
Author
Bhawana is a Community Evangelist at TestMu AI with over 3 years of experience creating technically accurate, strategy-driven content in software testing. She has authored 50+ blogs on test automation, cross-browser testing, mobile testing, and real device testing. She also serves as Product Marketing Manager for Kane CLI, the command-line tool that runs browser automation from the terminal using natural-language flows in a real Chrome browser. Bhawana is certified in KaneAI, Selenium, Appium, Playwright, and Cypress, reflecting her hands-on knowledge of modern automation practices. On LinkedIn, she is followed by 6000+ QA engineers, testers, AI automation testers, and tech leaders.
Bank Transfer FAQs
Did you find this page helpful?
TestMu AI forEnterprise
Get access to solutions built on Enterprise
grade security, privacy, & compliance
- Advanced access controls
- Advanced data retention rules
- Advanced Local Testing
- Premium Support options
- Early access to beta features
- Private Slack Channel
- Unlimited Manual Accessibility DevTools Tests




