In-market QA for iGaming · China · Vietnam · ThailandSee a sample report →
KYC

Check the verification journey before players give up on it.

Identity checks ask players for photos, documents and patience. We test the journey against the rules you give us: what the form accepts, what it rejects, and what the player is told along the way.

What we check

  • Data entry and field validation
  • Image upload: file types and sizes
  • Requests for additional documents
  • Result messages
  • State changes after submission, against the rules you supplied

What you receive

  • The input conditions for each case
  • Messages shown to the player
  • State changes and blockers
  • Sensitive fields redacted as agreed
  • A likely cause and suggested fixes from engineers experienced in iGaming
What it looks like

Every finding comes with the evidence behind it.

This is the shape of a single record in your report.

Examples of what this can surface

  • An oversized image fails with a generic error and no guidance
  • Status stays "pending" with no explanation or time estimate
  • A request for an extra document does not say which document
  • The result message and the account state disagree
TH-KYC-01P2

Upload error gives no recovery instruction

Case
Upload an ID photo larger than the accepted size
Expected
A message that states the size and format limits
Observed
Generic error; no size or format guidance, no retry hint
Environment
Bangkok · iPhone 13 · iOS 17 · AIS 4G
Evidence
Recording, screenshot of the message
Likely cause
The size limit is enforced on the server but not checked in the app, so the player only sees a generic error.
Suggested fix
Check size and format before upload, and state the limits in the message.
Before we start

We agree the details before any test runs.

What we need from you

  • The verification rules and the documents you accept
  • Test identities or approved test data. We do not use real personal data unless agreed
  • Stop conditions and how sensitive fields are handled

What we agree up front

  • Target market and test location
  • The build, accounts and access we will use
  • Devices and networks
  • Steps and expected results
  • Number of attempts, delivery timing and retests
  • Verification methods, test data and amounts
  • Stop conditions and sensitive-data handling

Functional QA does not constitute security testing, game-math validation or certification. Additional work is scoped separately. Likely causes and fixes are our engineers' assessment from observation and experience. Please confirm them against your own logs and code.

Want this tested in your markets?

Tell us the product, the markets and the journeys that matter. We will come back with a scope and a plan.