Onboarding
Check entry points, verification messages, registration and sign-in across the agreed player journey.
Explore the Scope IGAMING / IN-MARKET QA
Closer to
Real Players.
Registration, payments and gameplay, checked on local devices and networks. Turn experience gaps into documented steps, evidence and retest results.
CN / VN / TH
Local teams and environments. Scope agreed per project.
FIELD NOTES / 001DELIVERY PREVIEW
VIETNAM / HCMCVN-PAY-02
Payment Succeeded.
Why Is the Balance Stale?
OPPO Reno11 · Viettel 4G
build 1.8.0 → 1.8.1
build 1.8.0 → 1.8.1
BEFORE / OCCURRENCES3/ 5
RETEST / OCCURRENCES0/ 5
01 / ENVIRONMENT02 / OBSERVATION03 / RETEST
A finding your team can understand and act on.
FACTQA / CLOSER TO REALITYFollow the Player Journey
01
Local ExecutionPeople, devices and networks in market
02
Complete JourneysCheck every agreed step, end to end
03
Traceable EvidenceDocument conditions and observations
04
Build RetestsVerify the change in agreed conditions
JOURNEY SAMPLE/01Follow Every Step.
FROM FIRST VISIT TO FINAL RECEIPT
Follow Every Step.
Find the Friction.
Trace the same 10 test accounts from their first visit to the withdrawal receipt. Select a step to see the outcome, the interruption and what to check next.
04 / Deposit
EV-J04 · Evidence Record- Median Time
- 24 s · successful attempts
- 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.
Vietnam · build 1.8.0 · sandbox. Only accounts completing a step continue; 7 of the original 10 complete the journey. These are controlled test counts, not visitor conversion rates. Step timing uses successful-attempt medians; benchmark and payment repeats use separate samples.
BENCHMARK SAMPLE/02Who Performs Better
YOUR BRAND, IN CONTEXT
Who Performs Better
in Your Target Market?
Compare your product with selected brands on the same local device and network. Compare speed, reliability and journey clarity to see where competitors perform better and what to investigate.
Vietnam · Ho Chi Minh City
OPPO Reno11 · Android 14 · Chrome 128 · Viettel 4G
Game ready to play · median seconds · lower is faster
| Brand | First Screen (s) | Game Ready (s) | Sign-In (s) | Game Failures / 10 |
|---|---|---|---|---|
| Your Brand | 3.8 s | 6.4 s | 8.1 s | 1 / 10 |
| Brand A | 2.4 s | 4.8 s | 9.1 s | 0 / 10 |
| Brand B | 3.0 s | 5.6 s | 7.4 s | 1 / 10 |
| Brand C | 4.2 s | 6.9 s | 8.6 s | 2 / 10 |
Better Than Your Brand on This Metric
In Vietnam, Brand A is 1.6 s faster and Brand B is 0.8 s faster than your brand at game entry.
Brand A is faster at game entry, but its sign-in response is slower than yours. Select another metric to inspect the trade-off.
Game-entry click to playable state, with sign-in prerequisites satisfied.
Timed flows use 10 attempts per brand; successful median timing and failures are separate. Interleave runs with matching device, network, cache and account prerequisites. Count registration steps on the same path and bonus clarity with the same four checks. The final column refers only to game entry. Conclusions apply to the selected metric.
/03Every Player Journey.
BUILT AROUND YOUR PLAYERS
Every Player Journey.
Every Critical Detail.
From a specific issue to an end-to-end journey, we agree the test cases, preconditions, expected results and evidence for your product and market.
Payments
Check payment entry, redirects, status updates, balance display and withdrawal progress.
Explore the ScopeKYC Journeys
Review document submission, image upload, guidance and verification status for usability issues.
Explore the ScopeGameplay & Bonuses
Check game entry, interactions, bonus claims and displayed states against the agreed rules.
Explore the ScopeIn-Market Performance
Record loading, interruptions and reconnect behaviour alongside the actual device and network.
Explore the ScopeLocalization
Check language display, currency, dates and time zones. Agree any native-language review separately.
Explore the ScopeCompatibility
Check layout, interactions and key journeys on agreed phones, computers, operating systems and browsers.
Explore the ScopeBenchmarking
Compare agreed products using the same steps and recording criteria to identify observable differences.
Explore the ScopeFor casino, sportsbook, game content and aggregation platformsScope an End-to-End Journey ↗
/04Local Context.
A CLOSER LOOK AT EACH MARKET
Local Context.
Specific Findings.
Go beyond a single result: inspect local payment journeys, changes across builds and country-level evidence records.
Local Payments, Checked End to End.
Separate payment failures, verification blocks and pending orders with traceable records.
Explore Report ↗Did the New Build Improve the Experience?
Repeat speed and failure checks in the same environment, preserving improvements and regressions.
Explore Report ↗Vietnam · Ho Chi Minh City
Environment, key findings, payment records and retest observations in one country brief.
Read Country Brief ↗Thailand · Bangkok
Environment, key findings, payment records and retest observations in one country brief.
Read Country Brief ↗SAMPLE DELIVERY/05See What a Test
FROM TESTING TO ACTION
See What a Test
Puts in Your Hands.
Explore a player-journey report: what was checked, where it failed, and what your team can investigate next.
Player Journey · Three-Market Review
Sign-in / verification / KYC / deposits / payment return / withdrawals / game entry / bonuses
03Markets
06Device / Network Combinations
48Execution Items
06Issues to Investigate
Know Where the Journey Breaks
Results by market, with blocked work kept visible.
Passed 38Failed 6Blocked 4
ChinaPassed 12 · Failed 3 · Blocked 1
VietnamPassed 14 · Failed 1 · Blocked 1
ThailandPassed 12 · Failed 2 · Blocked 2
48 items = 8 checkpoints × 6 device / network combinations. Blocked items lack prerequisites and are not counted as passed. Repeat attempts are recorded separately.
From a Finding to a Next Step
3 of 6 issues shown. Open a record to see the observation, impact and suggested investigation.
P1Wallet balance does not refresh after payment return
VN-PAY-02
Observation · In 3 of 5 attempts, the payment page showed success but the wallet kept its previous balance until a manual refresh.
Impact · Players cannot confirm the deposit and may retry it.
Investigate · Check return-page refresh and order-state handling. Server logs are needed to confirm the cause.
Build 1.8.0 · occurrences3 / 5
Build 1.8.1 · occurrences0 / 5
Retest: same device and network, 5 attempts. Other combinations still require verification.
P2Upload error gives no recovery instruction
TH-KYC-01
Observation · An oversized image triggers a generic error without size or format guidance.
Impact · Players have no clear next step to complete verification.
Investigate · Review upload validation and Thai error messages; retest supported and unsupported files.
P3Bonus action label clips on a narrow screen
CN-UI-03
Observation · At 360 px width, the action label clips although the button remains usable.
Impact · The bonus action is harder to understand.
Investigate · Review text wrapping and container width, then retest adjacent screen sizes.
THE DETAIL BEHIND THE NUMBERS
One Issue.
A Traceable Record.
Follow VN-PAY-02 from its environment to its reproduction steps and retest. Your team receives the context needed to investigate, not just a failure count.
Screenshots, recordings and environment details are organized by issue ID in a project delivery.
VN-PAY-02SAMPLE DELIVERY
Country and CityVietnam · Ho Chi Minh City
Device and SoftwareOPPO Reno11 · Android 14 · Chrome 128
Local NetworkViettel 4G · mobile data
Product BuildTest environment · build 1.8.0
Sample issue record · evidence IDs illustrate how files are indexed.
/06Our People.
OUR DELIVERY MODEL
Our People.
Your Local Advantage.
Work with FactQA to define the player journey. Our own local QA teams carry out the checks and return the environment details, evidence and results.
01
Locally Run by Our Teams
FactQA assigns its own QA staff, confirms the project requirements and checks device and network availability.
02
Consistent Evidence
Agreed cases capture steps, outcomes and evidence. Missing items and blockers are reviewed before delivery.
03
Follow Through on Fixes
After you supply a fix, agreed retests return to the original environment and record the updated outcome.
/07Local by Presence.
LOCAL PRESENCE
Local by Presence.
Precise by Practice.
A useful check starts with a defined location, device and network. We confirm the environment with you before testing.
CN
- People
- FactQA’s own local QA teams
- Devices
- Phones and computers, confirmed per order
- Networks
- Local connections, confirmed per order
- Evidence
- Screenshots, recordings and retest results
These are our team locations. Cities, devices, networks, target markets and available test scope are confirmed per project. Ask about other locations.
/08A Small First Scope.
A CLEAR PATH TO DELIVERY
A Small First Scope.
A Clear Way to Work.
01
Share the Problem
Your product, country and workflow.
02
Agree Scope and Quote
Confirm devices, networks, steps and timing.
03
Run and Record
Follow the steps and capture the outcome.
04
Deliver and Retest
Repeat agreed checks after your fix.
/09
BEFORE WE START
Good Questions
Who carries out the tests?
FactQA’s own local QA teams. We agree the staffing, test environment, evidence and retest scope before each project starts.
How far do payment and KYC tests go?
We can scope the full journey. Accounts, payment methods, test data, amounts and stop conditions are agreed beforehand. Any live transactions or personal identity data require an explicit project arrangement.
Do you need source code?
Usually no. A URL or installation method, any needed test account, and the steps and expected results are enough. Share credentials through an agreed channel after scoping.
Can you help locate issues and suggest next steps?
We help narrow down where an issue may occur, based on reproduction steps and observed behaviour, and suggest practical next steps for investigation and improvement. Our findings come with execution records, environment details, screenshots, recordings and agreed retest results.
What if the issue does not appear?
We record the environment, attempts and observed results, then review missing trigger conditions with you. Not reproduced does not mean resolved.
How are fees and timing agreed?
The quote depends on countries, environments, steps, rounds and deliverables. Scope, fees and timing are confirmed before work starts.
/10Which Player Journey
LET’S MAKE IT CONCRETE
Which Player Journey
Needs a Closer Look?
Tell us your product type, target countries and the onboarding, payment or game journey to test. We will review local resources and scope.
REQUEST SUMMARY
Contact cs@factqa.com.
Prepare a request summary, then send it by email or copy and download it.