—
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
Pincode lookup
▶
pending
POS
POST
Pincode 560001 returns Karnataka and its post offices
user
pending
POS
POST
Pincode 110001 returns Delhi
user
pending
NEG
POST
Unknown pincode 000000 is rejected
user
pending
NEG
POST
Missing pincode is rejected
user
pending
NEG
POST
Pincode with letters is rejected
user
pending
NEG
POST
Pincode with 5 digits is rejected
user
pending
NEG
POST
Pincode with 7 digits is rejected
user
pending
NEG
POST
Pincode lookup without token is 401
user
pending
POS
POST
Pincode lookup answers within 5 s
user
3
Create nominee: validation errors
▶
pending
NEG
POST
Missing nominee_dob is rejected
user
pending
NEG
POST
Missing nominee_relation is rejected
user
pending
NEG
POST
Relation outside the allowed list is rejected
user
pending
NEG
POST
Salutation outside MR/MRS/MS is rejected
user
pending
NEG
POST
Phone with 5 digits is rejected
user
pending
NEG
POST
Phone with letters is rejected
user
pending
NEG
POST
Email without @ is rejected
user
pending
NEG
POST
PAN with a non-individual 4th letter is rejected
user
pending
NEG
POST
PAN with 9 characters is rejected
user
pending
NEG
POST
Future date of birth is rejected
user
pending
NEG
POST
Date of birth that is not a date is rejected
user
pending
NEG
POST
First name with a digit is rejected
user
pending
NEG
POST
No first_name and no full_name is rejected
user
pending
NEG
POST
Minor without guardian is rejected
user
pending
NEG
POST
Minor whose guardian is also a minor is rejected
user
pending
NEG
POST
Differently abled without the extra fields lists every missing field
user
pending
NEG
POST
Impairment percentage above 100 is rejected
user
pending
NEG
POST
UDID with 15 digits is rejected
user
pending
NEG
POST
DCB relation outside the 26-value list is rejected
user
pending
NEG
POST
Empty body lists all three mandatory-field errors
user
pending
NEG
POST
Create without any token is 401
user
pending
NEG
POST
Create with partner headers but a garbage Bearer token is 401
user
4
Create nominee: success paths
▶
pending
POS
POST
Create a nominee (adult, minimum fields)
user
pending
POS
POST
Second nominee created as default takes the default flag from the first
user
pending
POS
POST
Single-word full_name is accepted and last name becomes "."
user
pending
POS
POST
Three-part full_name is split into first, middle and last
user
pending
POS
POST
Nominee PAN is stored encrypted and upper-cased
user
pending
POS
POST
Minor nominee with an adult guardian is accepted
user
pending
POS
POST
Differently abled nominee with all certificate fields is accepted
user
pending
POS
POST
Same idempotency_key sent twice returns the same nominee (first call)
user
pending
POS
POST
Same idempotency_key sent twice returns the same nominee (replay) and adds no row
user
pending
POS
POST
Create works with the Bearer token alone (no partner headers)
user
pending
POS
POST
Alias POST /api/v1/user-nominee behaves the same
user
5
List and get nominee
▶
pending
POS
GET
List returns only this user's nominees, newest first, with has_active_holding
user
pending
POS
GET
limit=2 returns two rows
user
pending
POS
GET
page=2&limit=2 returns different rows than page 1
user
pending
EDG
GET
Invalid page/limit (page=abc) falls back to page 1, limit 10
user
pending
POS
GET
List phone is plain digits (decrypted) for a non-SSFB nominee
user
pending
NEG
GET
List without token is 401
user
pending
POS
GET
Get one nominee by id
user
pending
NEG
GET
Get nominee with an unknown id is 404 in the body
user
pending
NEG
GET
Get nominee by id without token is 401
user
6
Nominee address
▶
pending
POS
POST
Save an address for a nominee
user
pending
POS
GET
Read the nominee address back decrypted
user
pending
POS
GET
List addresses for a nominee by f_user_nominee_id
user
pending
POS
POST
Saving an address again for the same nominee updates the row (no second row)
user
pending
NEG
POST
Address without f_user_nominee_id is rejected (FIXUSER1090)
user
pending
NEG
POST
same_as_user without an own address is rejected (FIXUSER1616)
user
pending
NEG
POST
Pincode with letters is rejected
user
pending
NEG
POST
Address without token is 401
user
pending
POS
POST
Nominee created with nomineeAddress also gets the address row
user
pending
NEG
GET
Address lookup without token is 401
user
7
Update nominee
▶
pending
POS
PUT
PUT /user-nominee/:id changes the name
user
pending
NEG
PUT
PUT with a relation outside the list is rejected
user
pending
POS
PUT
PUT with is_default=true moves the default flag
user
pending
NEG
PUT
PUT for an unknown nominee id is a 400 error
user
pending
NEG
PUT
PUT without token is 401
user
pending
POS
PUT
PUT /user-nominee/v1/update changes email and phone
user
pending
POS
PUT
v1/update with PAN stores it encrypted
user
pending
NEG
PUT
v1/update for an unknown nominee id is 404
user
pending
NEG
PUT
v1/update with an invalid email is rejected
user
pending
NEG
PUT
v1/update without token is 401
user
8
Issuer-specific behaviour (SSFB, DCB, Unity, AUSFB, IIB)
▶
pending
POS
POST
SSFB: nominee phone is stored encrypted
user
pending
POS
GET
SSFB: list decrypts the phone back to 10 digits
user
pending
POS
PUT
SSFB: v1/update re-encrypts a new phone
user
pending
POS
POST
DCB: SPOUSE derives generic relation "Wife" and keeps dcb_nominee_relation
user
pending
POS
POST
USFB: nominee with a valid address is accepted
user
pending
NEG
POST
USFB: address with city not in the Unity picklist is refused with the failing flag (HTTP 201, body 400)
user
pending
NEG
POST
USFB: address with state not in the Unity picklist is refused with the failing flag (HTTP 201, body 400)
user
pending
NEG
POST
USFB: address with missing line1 is refused with the failing flag (HTTP 201, body 400)
user
pending
NEG
POST
USFB: address with missing pincode is refused with the failing flag (HTTP 201, body 400)
user
pending
NEG
PUT
USFB: v1/update with a bad city is refused with flags
user
pending
POS
POST
Other issuer codes (AUSFB, DCB, USFB without address) use the same DB save
user
pending
EDG
POST
IIB: create is forwarded to IndusInd and writes no row in Fixerra user_nominee
user
9
Investment nominee (per transaction)
▶
pending
POS
POST
Save one nominee at 100% for a transaction (the shape the app sends)
invest
pending
POS
POST
Two nominees 60/40 are both saved
invest
pending
POS
POST
Four nominees at 25% each are accepted (maximum allowed)
invest
pending
POS
POST
SUCCESSIVE nominees are saved with percentage 0 and their serial order
invest
pending
NEG
POST
Percentages 60 + 30 (not 100) are rejected
invest
pending
NEG
POST
Single nominee at 50% is rejected
invest
pending
NEG
POST
Empty array is rejected
invest
pending
NEG
POST
A plain object instead of an array is rejected
invest
pending
NEG
POST
Five nominees are rejected (maximum 4)
invest
pending
NEG
POST
Mixed SIMULTANEOUS and SUCCESSIVE in one plan is rejected
invest
pending
NEG
POST
SUCCESSIVE without serial_order is rejected
invest
pending
NEG
POST
SUCCESSIVE with the same serial_order twice is rejected
invest
pending
NEG
POST
Save without token is 401
invest
pending
POS
POST
Save without partner headers (Bearer only) works
invest
pending
POS
GET
data-by-transaction returns the rows with the nominee name and address
invest
pending
EDG
GET
data-by-transaction for an unknown transaction returns an empty list
invest
pending
NEG
GET
data-by-transaction without token is 401
invest
pending
POS
POST
validate-nominee (Unity picklist): nominee with a good address passes every flag
invest
pending
POS
POST
validate-nominee: nominee without an address reports the address flags false
invest
pending
NEG
POST
validate-nominee without token is 401
invest
10
Delete nominee
▶
pending
POS
DELETE
Delete a nominee
user
pending
POS
GET
Deleted nominee no longer appears in the list
user
pending
NEG
DELETE
Delete the same nominee again is a 400 error
user
pending
NEG
DELETE
Delete an unknown nominee id is a 400 error
user
pending
NEG
DELETE
Delete without token is 401
user
pending
POS
DELETE
Deleting the default nominee hands the default flag to another one
user
11
Known bugs (fail until fixed)
▶
pending
POS
POST
Setup: create the victim nominee owned by the main user
user
pending
NEG
GET
KNOWN BUG: another user cannot read my nominee by id
user
pending
NEG
PUT
KNOWN BUG: another user cannot rename my nominee (PUT /user-nominee/:id)
user
pending
NEG
PUT
Control: another user cannot change my nominee through v1/update (passes today)
user
pending
NEG
POST
KNOWN BUG: another user cannot write an address onto my nominee
user
pending
NEG
GET
KNOWN BUG: another user cannot read my nominee address
user
pending
NEG
DELETE
KNOWN BUG: another user cannot delete my nominee
user
pending
NEG
POST
KNOWN BUG: address cannot be saved for a nominee id that does not exist
user
pending
EDG
GET
KNOWN BUG: address lookup for a nominee without an address answers HTTP 200 with body 502
user
pending
NEG
PUT
KNOWN BUG: renaming a nominee with PUT does not make it the default
user
pending
NEG
POST
KNOWN BUG: saving nominees again for the same transaction replaces the old rows
invest
pending
NEG
POST
KNOWN BUG: a nominee id that does not exist is refused
invest
pending
NEG
POST
KNOWN BUG: negative percentages that still sum to 100 are refused
invest
pending
NEG
POST
KNOWN BUG: validate-nominee without nominee_id is refused
invest
12
Cleanup
▶
pending
POS
DELETE
Cleanup: delete the address created for a non-existent nominee
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.