Find the step where a payment stops.
Deposits and withdrawals are where trust is won or lost. We follow your agreed payment methods end to end, and keep completed attempts, timeouts and blocked attempts apart, so you can see which step stopped the money.
What we check
- Agreed deposit and withdrawal methods
- Amounts and currency display
- Redirects out to a bank or wallet, and the return
- Balances before and after
- Transaction states and receipts
- Error and timeout messages
What you receive
- Timestamps for each action
- Before-and-after states and balances
- Agreed test references for every attempt
- Redacted evidence: screenshots and recordings
- Completed, timed-out and blocked attempts reported separately
- A likely cause and suggested fixes from engineers experienced in iGaming
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
- The payment succeeds but the wallet balance does not update
- A bank transfer stays pending past the agreed observation window
- The return page from a bank app loads slowly or not at all
- A channel cannot start because the test account has no access. We report this as blocked, not as a channel failure
Wallet balance does not refresh after payment return
- Case
- E-wallet deposit, sandbox channel
- Expected
- Balance shows the deposited amount on return
- 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 · Viettel 4G
- Evidence
- EV-P01: recording and screenshots
- Likely cause
- The return page reads the balance before the order reaches its final state, so a slow bank callback leaves the wallet stale.
- Suggested fix
- Refresh the balance once the order is final, and show a pending state until then.
We agree the details before any test runs.
What we need from you
- Agreed payment methods, with sandbox or test channels
- Test accounts, balances and amounts
- Stop conditions and how sensitive data is handled
- The observation window for pending states
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
- Payment methods, test data and amounts
- Stop conditions and sensitive-data handling
Channel names in our reports do not claim an integration with a payment brand. Withdrawal time is measured from submission to the sandbox receipt, not live settlement. 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.