Unity Small Finance Bank (USFB) — AUTH Journey
Fixed Deposit · New to Bank · Unity Small Finance Bank (USFB)
—
Total
—
Passed
—
Failed
—
Skipped
—
Running
—
Duration
1 OTP login: send OTP
10 cases
▶
pending POS POST Send OTP to a valid registered number user
pending POS POST Resend OTP right away is accepted (no cooldown) user
pending NEG POST Phone without 91 prefix is rejected user
pending NEG POST Phone with 11 digits is rejected user
pending NEG POST Phone with 13 digits is rejected user
pending NEG POST Missing phone is rejected user
pending NEG POST Phone sent as a number is rejected user
pending NEG POST Phone with letters is rejected user
pending NEG POST Non-Indian mobile (starts with 1) is rejected user
pending POS POST Send OTP responds within 3 s user
2 OTP login: verify OTP
11 cases
▶
pending NEG POST Missing consent is rejected user
pending NEG POST OTP with letters is rejected user
pending NEG POST OTP with 5 digits is rejected user
pending NEG POST OTP with 7 digits is rejected user
pending NEG POST Phone without 91 is rejected user
pending NEG POST Unknown partner_url is rejected user
pending NEG POST Wrong OTP is refused (HTTP 201, body 403) user
pending POS POST Right OTP for existing user returns tokens user
pending POS GET Access token claims and 24 h lifetime user
pending POS GET New access token works on GET /user user
pending POS POST consent=true is accepted the same as false user
3 Known bugs (fail until fixed)
6 cases
▶
pending NEG POST KNOWN BUG (critical, develop): IndiaMart login with junk encryptedPhone must not return a token user
pending NEG POST KNOWN BUG: decrypted-utm with junk input should be an error, not empty success user
pending NEG POST KNOWN BUG: decrypted-utm without encrypted should be 400 user
pending NEG POST KNOWN BUG: email OTP verify route exists (app calls it) user
pending NEG POST KNOWN BUG: check-user should reject a phone without 91 user
pending NEG GET KNOWN BUG: token from the previous login should stop working after a new login user
4 check-user + mobile prefill
4 cases
▶
pending POS POST check-user: existing phone user
pending NEG POST check-user: unknown phone user
pending POS POST mobile-prefill/email answers and never errors user
pending NEG POST mobile-prefill/email without token is 401 user
5 New user login (delete + re-create)
4 cases
▶
pending POS DELETE Delete the QA test user (setup for new-user login) user
pending POS POST Send OTP for the deleted number user
pending POS POST Right OTP for a new number creates the user (with campaign + agent code) user
pending POS POST Campaign on an existing user is not overwritten user
6 Partner SSO (create user, authcode, SSO login)
22 cases
▶
pending NEG POST Create user without partner headers is 401 user
pending NEG POST Create user with a wrong partner key is 401 user
pending NEG POST Create user with an unknown partner code is 401 user
pending NEG POST Authcode without partner headers is 401 user
pending NEG POST SSO login with a junk authcode user
pending NEG POST SSO login without consent user
pending NEG POST SSO login without authcode user
pending NEG POST Create user without phone user
pending NEG POST Create user with phone without 91 user
pending POS POST Partner creates / links the QA user user
pending POS POST Same create call again does not duplicate the link user
pending NEG POST Authcode without data user
pending NEG POST Authcode with broken URL encoding user
pending NEG POST Authcode with unsigned (plain) phone user
pending POS POST Authcode by phone for a linked user user
pending NEG POST Authcode by PAN signed without JSON quotes is refused user
pending NEG POST Authcode by PAN for a PAN no user has user
pending POS POST SSO login with the phone authcode user
pending POS GET SSO token works on GET /user user
pending POS POST SSO agent code: last touch wins user
pending NEG POST SSO login with a tampered authcode user
pending EDG POST KNOWN RISK: same authcode works again (not one-time) user
7 IndiaMart / email login
3 cases
▶
pending NEG POST IndiaMart login without encryptedPhone user
pending NEG POST Email login: unknown email user
pending NEG POST Email login: missing email user
8 Agent login
14 cases
▶
pending NEG POST Agent OTP: phone with 91 prefix is rejected user
pending NEG POST Agent OTP: phone starting with 5 is rejected user
pending NEG POST Agent OTP: missing phone user
pending NEG POST Agent OTP: unknown partner_url user
pending NEG POST Agent SSO with junk authcode user
pending NEG POST Agent SSO with empty authcode user
pending NEG POST Agent SSO refuses a customer authcode user
pending NEG POST Agent authcode without partner headers is 401 user
pending POS POST Agent OTP for a valid number and partner user
pending NEG POST Agent verify without partner_url user
pending NEG POST Agent verify with a wrong OTP returns no token user
pending POS POST Agent OTP for the agent test number user
pending POS POST Agent verify creates or finds the agent user
pending NEG GET Agent token is refused on customer GET /user user
9 Logout and login again
9 cases
▶
pending NEG POST Logout without token is 401 user
pending POS POST Second login (keeps the first token for the revoke check) user
pending POS POST Logout with a valid token user
pending NEG GET Same token is refused after logout user
pending NEG GET Older token of the same user is refused after logout user
pending NEG POST Logout twice: second call is 401 user
pending POS POST Login again after logout: send OTP user
pending POS POST Login again after logout: new token works, session not revoked user
pending POS GET Token after re-login works on GET /user 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.