# FactQA Player journey record sample



Vietnam · Ho Chi Minh City · build 1.8.0 · sandbox

OPPO Reno11 · Android 14 · Chrome 128 · Viettel 4G



The same 10 accounts proceed step by step; only completed accounts continue. Seven complete the journey. Controlled counts are not visitor conversion rates. Timing uses successful medians; specialist tests use separate samples.



## 1. Visit

Completed / entered: 10 / 10

Median successful time: 3.8 s

Evidence record: EV-J01

Steps: Open test URL → wait for usable main content

Expected: Main content loads and primary controls work.

Observed: All 10 attempts completed; median first-screen time was 3.8 s.

Next check: Continue to registration; page load alone does not validate the journey.



## 2. Register

Completed / entered: 9 / 10

Median successful time: 42 s

Evidence record: EV-J02

Steps: Open registration → enter required fields → receive OTP → submit

Expected: OTP arrives and submission opens the signed-in screen.

Observed: One OTP did not arrive within 60 s; that account stopped here. Nine completed.

Next check: Check OTP request, delivery status and arrival time on the local network.



## 3. Verify

Completed / entered: 8 / 9

Median successful time: 75 s

Evidence record: EV-J03

Steps: Open verification → upload test materials → submit → inspect status

Expected: Test materials can be submitted with a clear processing status.

Observed: One upload failed without a retry control. Eight reached the agreed verified state.

Next check: Review upload error messaging and recovery; materials and review states are supplied by the test environment.



## 4. Deposit

Completed / entered: 7 / 8

Median successful time: 24 s

Evidence record: EV-J04

Steps: Select test payment method → submit → return to wallet → check balance

Expected: Status and balance agree, allowing the game flow to continue.

Observed: One return left a stale wallet balance and stopped under the agreed rule. Seven completed.

Next check: Link payment state, return screen and balance refresh records for investigation.



## 5. Play

Completed / entered: 7 / 7

Median successful time: 6.4 s

Evidence record: EV-J05

Steps: Open game → wait for playable state → perform agreed test action

Expected: Game is playable with expected feedback and test balance display.

Observed: All seven completed; median time to playable state was 6.4 s.

Next check: The benchmark uses 10 separate attempts; counts are kept separate from this journey.



## 6. Withdraw

Completed / entered: 7 / 7

Median successful time: 90 s

Evidence record: EV-J06

Steps: Submit test withdrawal → inspect status → verify sandbox receipt

Expected: Request, status and sandbox receipt can be reconciled.

Observed: All seven received sandbox receipts; median completion time was 90 s.

Next check: This checks sandbox receipts. Live settlement timing requires a separately scoped run.



This sample provides the written evidence-index structure without project screenshot or video files.