Find the issues that cost you players.
FactQA tests your casino, sportsbook or game with local testers on real phones and mobile networks. Failed deposits, stuck sign-ups and broken bonuses get found before players leave, with the evidence and a likely cause your team can act on.
- Local testers on real devices and networks
- Senior iGaming engineers point to the likely cause and suggest a fix
- Every issue comes with evidence your team can act on
- Retests in the same conditions, so you know it's fixed
- Online casinos
- Sportsbooks
- Game studios
- Aggregators & platforms
- Payment providers
See it in under two minutes.
It passed in your lab. That's not where your players are.
Most releases are checked on fast office Wi-Fi, flagship phones and sandbox payments. Your players in Asia are on mid-range phones, patchy 4G and local payment flows. That gap is where deposits fail and players quietly leave.
Your lab Everything passes
- NetworkOffice Wi-Fi, 1 Gbps
- DeviceLatest flagship phone
- PaymentsSandbox, always returns success
- LanguageTranslated by the team
Real players Where it breaks
- NetworkViettel 4G, one bar, late at night
- DeviceMid-range phone, older browser
- PaymentsReal bank flow, slow return page
- LanguageRead by native speakers
We test the right-hand column, so you can fix it before launch or after your next release.
Five things you can take straight to your team.
The issues only local players run into
We walk your product the way a player in Vietnam, Thailand or China does, on their kind of phone and network. We find what an office test can't.
- From "Works on our devices" to confirmed on mid-range phones over local 4G
- From "OTP probably arrives" to checked on local carriers
- From "Translated" to read by native speakers
Evidence your developers can act on
No vague "it didn't work". Each issue arrives with the steps, what we expected, what we saw, and the device, network and build it happened on.
- From "Can't reproduce" to exact steps, screenshots and recordings
- From a long bug list to ranked issues, each with severity and priority
- Observed
- Payment page shows success; wallet keeps the old balance until a manual refresh. 3 of 5 attempts.
- Environment
- Ho Chi Minh City · OPPO Reno11 · Android 14 · Chrome 128 · Viettel 4G
Engineers who know iGaming tell you where to look
Our engineers have deep iGaming experience. For each issue we tell you what we think is behind it, where to look first and how to fix it, so your team starts from a lead and not a guess.
- From "Where do we even start?" to a likely cause and where to look first
- From a list of symptoms to practical fix suggestions from people who know the industry
Wallet balance does not refresh after payment return
The return page reads the balance before the order reaches its final state, so a slow bank callback leaves the wallet stale.
Order-state handling on return, and callback timing from the payment provider.
Refresh the balance once the order is final, and show a pending state until then.
Our engineers' assessment from observation and experience. Confirm it against your logs.
Proof that the fix actually worked
After your team ships a fix, we run the same test again in the same conditions. You see the before and after side by side, not a promise.
- From "We think it's fixed" to verified on the same device and network
- From release anxiety to a clear record of improvements and regressions
A clear view of where you stand against competitors
We run your product and selected competitors through the same journey on the same device and network. You see exactly where you lead and where you lag.
- From guessing how you compare to measured speed and reliability, side by side
- From "feels slower" to a number you can set a target against
Test the moments that cost you players.
We agree the journeys, preconditions and expected results with you, then run them in market.
Onboarding
Sign-up, verification codes and sign-in, step by step.
"The code never arrived."See what we check →Payments
Deposits, redirects, status and withdrawals through local methods.
"I paid, but I see no money."See what we check →KYC
Document upload, guidance and verification status.
"Upload failed. Why?"See what we check →Gameplay & bonuses
Game entry, interactions and bonus claims against the rules.
"My bonus didn't show up."See what we check →Performance
Load time, interruptions and reconnects on real networks.
"It keeps loading."See what we check →Localization
Language, currency, dates and time zones, read by locals.
"This doesn't read right."See what we check →Compatibility
Layout and key journeys on agreed phones, computers and browsers.
"The button is cut off."See what we check →Benchmarking
Your product against competitors, on the same device and network.
"They load faster than us."See what we check →Local testers. Local conditions.
Pick a market to see what we check on the ground.
China
Guangzhou and other major cities
- Networks
- China Mobile, China Unicom, China Telecom
- Devices
- Huawei, Xiaomi, OPPO, vivo, iPhone
- We check
- Simplified Chinese copy, local verification flows, payment returns, browser and app variants
Vietnam
Ho Chi Minh City, Hanoi
- Networks
- Viettel, VinaPhone, MobiFone
- Devices
- OPPO, Samsung, Xiaomi, iPhone
- We check
- VND formatting, bank and e-wallet flows, OTP delivery, mid-range phones on 4G
Thailand
Bangkok and other major cities
- Networks
- AIS, True, dtac
- Devices
- Samsung, OPPO, vivo, iPhone
- We check
- THB formatting, Thai-language copy, local bank and QR payments, KYC uploads
Devices and networks are agreed per project.
From a short call to a retested fix.
- 1
Scope
Tell us the product, markets and journeys that matter. We agree test cases, devices and networks on a short call.
- 2
Test in market
Local testers run the journeys on real devices and networks, with a delivery manager keeping it on track.
- 3
Get the report
Ranked issues with evidence, a likely cause and a suggested fix, plus a summary by market.
- 4
Retest
Once you've shipped fixes, we rerun the same tests in the same conditions and show before and after.
This is what lands in your inbox.
A player-journey review across three markets: what was checked, where it broke, and what your team can investigate next.
Results by market
Top issues
What do you need from us to get started?
A staging or production build, test accounts, and a list of the journeys that matter most. We agree scope, markets and success criteria on a short call.
Which devices and networks do you use?
Real phones on local mobile networks in each market, for example a mid-range Android phone on 4G in Ho Chi Minh City. We agree the mix with you per project.
What does an issue report look like?
Each issue has the steps, the expected and observed result, severity, device, network and build, plus screenshots or recordings, a likely cause and a suggested fix for your team.
Do you only report problems, or help us fix them?
Both. Our engineers have deep iGaming experience, so each issue comes with what we think is behind it, where to look first and how we would fix it. Your team makes the changes, and we retest on the updated build. A likely cause is our assessment from observation, so please confirm it against your own logs.
Do you retest after we fix something?
Yes. We rerun the same test in the same conditions and show the before and after, so you can see whether the fix held.
Can you compare us with competitors?
Yes. We run your product and selected competitors through the same steps on the same device and network, and report speed, failures and journey clarity side by side.
Is our data kept confidential?
Your builds, accounts and findings stay with you. We are happy to sign an NDA before kick-off.
Tell us where your players are. We'll show you what they see.
Book a short call to talk through your product, your markets and what you'd like to learn.