—
Total
—
Passed
—
Failed
—
Skipped
—
Running
—
Duration
1
Setup: second user for cross-user checks
▶
pending
POS
POST
Second user (random new number): send OTP and read it from Redis
user
pending
POS
POST
Second user: verify OTP, user is created, keep the token
user
2
IFSC lookup
▶
pending
POS
POST
HDFC IFSC returns bank, branch, micr and state
user
pending
POS
POST
ICICI IFSC returns ICICI Bank
user
pending
POS
POST
SBI IFSC returns State Bank of India
user
pending
EDG
POST
Lower case IFSC is accepted and returned in upper case
user
pending
EDG
POST
IFSC with surrounding spaces is trimmed
user
pending
EDG
POST
Looking the same IFSC up again returns identical details
user
pending
NEG
POST
Empty body is rejected
user
pending
NEG
POST
IFSC with 10 characters is rejected
user
pending
NEG
POST
IFSC with 12 characters is rejected
user
pending
NEG
POST
IFSC whose 5th character is not 0 is rejected
user
pending
NEG
POST
IFSC sent as a number is rejected
user
pending
NEG
POST
IFSC with SQL characters is rejected
user
pending
NEG
POST
IFSC with special characters is rejected
user
pending
NEG
POST
Well formed IFSC that no bank owns answers FIXUSER1054
user
pending
NEG
POST
No token is refused
user
pending
NEG
POST
Invalid token is refused
user
3
Add and verify a bank account
▶
pending
POS
POST
Add a bank with full name: saved, verified and default
user
pending
POS
POST
Second bank (lower case IFSC) becomes the default and the first one stops being default
user
pending
EDG
POST
Adding the same account again does not duplicate it and makes it default again
user
pending
POS
POST
First and last name can be sent instead of a full name
user
pending
NEG
POST
No holder name at all is rejected
user
pending
NEG
POST
Well formed IFSC that no bank owns is rejected
user
pending
POS
GET
After the adds the user has exactly 3 live bank rows (A, B, C)
user
pending
NEG
POST
A second user cannot add an account that is already linked to the first user
user
pending
NEG
POST
Account number with 8 digits is rejected
user
pending
NEG
POST
Account number with 19 digits is rejected
user
pending
NEG
POST
Account number with letters is rejected
user
pending
NEG
POST
IFSC with a non-zero 5th character is rejected
user
pending
NEG
POST
Without a partner header the bank goes through the SSFB penny drop and a made-up account is refused
user
pending
EDG
POST
Name mismatch with account_holder_name in the query answers HTTP 201 with body 400 (FIXUSER1055)
user
4
List and get bank accounts
▶
pending
POS
GET
decrypt=true returns the 3 accounts in clear with logo, alias and code
user
pending
POS
GET
Without decrypt the account numbers stay encrypted
user
pending
EDG
GET
limit=1 returns one row
user
pending
EDG
GET
page=2&limit=2 returns the third row
user
pending
EDG
GET
A page past the end returns an empty list
user
pending
EDG
GET
page=0&limit=0 falls back to page 1, limit 10
user
pending
EDG
GET
Non numeric page falls back to page 1, limit 10
user
pending
POS
GET
issuer_code=SSFB with decrypt adds the unsupported flag to every row
user
pending
POS
GET
page_name=review_and_pay still returns the 3 accounts
user
pending
EDG
GET
issuer_code=USFB is served from Unity and answers 200
user
pending
NEG
GET
No token is refused
user
pending
POS
GET
A second user sees none of the first user's accounts
user
pending
POS
GET
Get one account by id returns the row with an encrypted number
user
pending
EDG
GET
Unknown id answers 200 with an empty payload
user
pending
NEG
GET
No token is refused
user
5
Set default bank account
▶
pending
POS
PATCH
Make C the default: answered with the request, only C is default in the DB
user
pending
POS
PATCH
Make A the default again: the flag moves, still one default
user
pending
NEG
PATCH
Unknown bank id is refused with FIXUSER1366
user
pending
NEG
PATCH
Empty body lists the three mandatory fields
user
pending
NEG
PATCH
Issuer code outside the list is refused with FIXUSER1364
user
pending
NEG
PATCH
is_default sent as text is refused with FIXUSER1365
user
pending
NEG
PATCH
Missing bank id is refused with FIXUSER1363
user
pending
NEG
PATCH
No token is refused
user
pending
NEG
PATCH
A second user cannot change the default of the first user (FIXUSER1366)
user
6
Sync bank to Unity
▶
pending
POS
POST
Sync a bank the user added to Unity: answered {synced: true}
user
pending
EDG
POST
Sync works without a holder name (falls back to a placeholder)
user
pending
NEG
POST
Empty body is rejected
user
pending
NEG
POST
Account with 8 digits is rejected
user
pending
NEG
POST
Account with letters is rejected
user
pending
NEG
POST
Badly formed IFSC is rejected
user
pending
NEG
POST
Well formed IFSC that no bank owns is rejected
user
pending
NEG
POST
No token and no partner headers is refused
user
7
UPI bank details
▶
pending
NEG
GET
No token is refused
user
pending
NEG
GET
A number with no UPI bank record is refused with FIXUSER1525 and no bank row is added
user
8
Delete bank account
▶
pending
POS
DELETE
Owner deletes bank C: soft deleted, others untouched
user
pending
POS
GET
A deleted account no longer shows in the list
user
pending
NEG
DELETE
No token is refused
user
9
Known bugs (fail until fixed)
▶
pending
NEG
PATCH
KNOWN BUG: is_default=false does not make the account the default
user
pending
NEG
GET
KNOWN BUG: another user cannot read my bank account by id
user
pending
NEG
PUT
KNOWN BUG: another user cannot rename my bank account (PUT /bank-accounts/:id)
user
pending
NEG
DELETE
KNOWN BUG: another user cannot delete my bank account
user
pending
NEG
POST
KNOWN BUG: a bank cannot be inserted as verified without going through verification (POST /bank-accounts)
user
pending
NEG
PUT
KNOWN BUG: PUT on an id that does not exist does not create a bank row
user
pending
NEG
DELETE
KNOWN BUG: deleting an id that does not exist answers a FIX error code, not "Cannot"
user
pending
NEG
POST
KNOWN BUG: sync-to-unity refuses an account the user never added or verified
user
10
Verification rate limit
▶
pending
EDG
POST
Repeated bank verification calls hit the per-user limit: 429 with FIXUSER1517
user
pending
EDG
GET
Once limited, the account list is still served (the limit only covers verification)
user
API calls run on the Node.js server, not in the browser — they will not appear in Chrome DevTools → Network.
Use this panel to inspect every request, status, timing, and curl for the run.