Technical & Operations Q&A

Technical integration and operations: make every transaction traceable and recoverable.

Direct answers for engineering, operations and reconciliation teams evaluating a multi-provider game API from session launch through long-term service.

Wallet architectureIdempotency and reconciliationAPI securityAvailability and migration
Integration and transactions

Connect game sessions and wallet transactions first

Define call sequence, system responsibility and duplicate or timed-out request handling.

What is the difference between single-wallet and transfer-wallet models?

Direct answer

In a single-wallet model, the operator owns the player's main balance and the game side calls it for bets and payouts. In a transfer-wallet model, funds move into a game-side wallet first and return through a separate transfer workflow.

Single wallet centralizes balance but requires a reliable, concurrent and idempotent operator wallet. Transfer wallet reduces real-time callback dependency during play but adds deposit, withdrawal, synchronization and funds-in-transit reconciliation.

How this applies to AG GAME

AG GAME supports both models. Select one before testing because their endpoints, states and acceptance scenarios differ.

What is the end-to-end flow for listing and launching a game?

Direct answer

Synchronize providers, categories and games; confirm availability; create a session with merchant, player, game, language, currency and return parameters; then pass the launch result to the front end.

Also test stable player identity, expiry, duplicate launch, device compatibility, maintenance, invalid parameters and return flow. Catalog presence does not guarantee session creation.

How this applies to AG GAME

AG GAME API v5.0.0 provides unified provider, category and game queries plus sessions; current fields and endpoints are defined in the API reference.

How do balance, bet, payout and rollback transactions work together?

Direct answer

The game side queries available balance when needed, an accepted bet debits the operator ledger, and the result produces a payout. A rollback references the original transaction and creates a traceable state change.

Do not rely only on arrival order. Drive the ledger from transaction type, unique ID, original reference, round ID and final status. Bets and payouts may arrive separately, and a timeout is not a failure.

How this applies to AG GAME

AG GAME uses request traces, transaction IDs and round IDs to correlate the workflow; direction and fields depend on the wallet model.

How should duplicate debits or payouts be prevented?

Direct answer

Assign each business transaction a stable unique ID and enforce uniqueness in the ledger. Repeating that ID must return the original business result without changing the balance again.

Cover concurrent duplicates, network retries and recovery in persistent storage, not only a short-lived cache. Reject and record a reused ID with different content.

How this applies to AG GAME

AG GAME wallet callbacks use transactionId for idempotency and reqTraceId for tracing; the customer wallet must persist status and return a consistent response to duplicates.

What should happen after a timeout, disconnect or interrupted game?

Direct answer

A timeout means the caller did not receive a definitive result in time; it does not prove failure. Query or reconcile the original transaction before deciding to retry, roll back, compensate or await round settlement.

A player disconnect does not cancel an accepted transaction. Define retry limits, backoff, final states, unfinished-round treatment, escalation and audit records, then reproduce them in testing.

How this applies to AG GAME

AG GAME transfer flows require checking the original merchantTransactionId after timeout before resending; callback duplicates are handled idempotently by transactionId.

Data and performance

Make balances, currencies and performance verifiable

Use shared identifiers, explicit definitions and layered measurement for operations.

How should transaction and round IDs be used for reconciliation?

Direct answer

Use the unique transaction ID to locate one ledger entry, the round ID to group bets, payouts, rollbacks and compensation, then reconcile both reports under the same currency, time zone and status rules.

Retain raw requests and responses, timestamps, precision, links and final state. A displayed balance or sample is not a ledger. Unmatched items should enter an owned exception list.

How this applies to AG GAME

AG GAME request traces, transaction IDs, merchant transaction IDs and round IDs serve different purposes; incident reports should include the identifiers for the selected wallet mode.

How should currency codes, amount precision and settlement currencies be handled?

Direct answer

Agree currency codes, minor units, decimals, rounding and availability. Use integer minor units or fixed decimal arithmetic rather than binary floating point for money.

If game and settlement currencies differ, define rate source, timestamp, direction and variance treatment. Every conversion should be explicit and traceable.

How this applies to AG GAME

AG GAME's 35 country or currency codes describe capability scope; enabled codes, precision and settlement are confirmed in project testing and contract terms.

How should API latency, game load time and concurrency be measured?

Direct answer

API latency covers request-to-response time, game load time covers launch-to-interaction experience, and concurrency measures correctness and target latency under a stated request volume and business mix.

State region, network, device, endpoint, sample size, P50/P95/P99, error rate, cache state and period. A single average does not describe peaks or transaction capacity.

How this applies to AG GAME

AG GAME publishes average end-user latency below 150 ms and capacity of 100 million orders per day; both require project validation for region, network and workload and are not fixed guarantees for every request.

What can a global CDN improve, and what latency remains elsewhere?

Direct answer

A CDN places cacheable images, scripts and other static assets closer to users. Dynamic sessions, wallet transactions and provider services still reach origin or business systems.

User network, DNS, TLS, device, asset size, cache hit, regional servers, provider response and operator wallet all affect experience, so measure each layer separately.

How this applies to AG GAME

AG GAME uses four regional central servers and 200+ CDN nodes. Projects should still test static loading, sessions and wallets from target regions.

Security and continuity

Control credential, incident, version and migration risk

Carry security boundaries and recovery requirements into integration and maintenance.

How should API signing, keys, access and data separation be implemented?

Direct answer

Use cryptographic signatures to verify origin and integrity, constrain credential purpose and environment, and separate test and production merchants, keys, data and logs. Never place secrets in front-end code or public repositories.

Define timestamp tolerance, nonce replay prevention, key issue and replacement, anomalous access and minimized logging. Signing does not replace TLS, server authorization or ledger validation.

How this applies to AG GAME

AG GAME uses HMAC-SHA256 with merchantCode, timestamp, nonce, signType and body in the current authentication flow; production credentials are controlled per project.

How should provider incidents, maintenance and recovery be handled?

Direct answer

Distinguish game, provider, aggregation, wallet and network failures; disable or degrade only the known impact scope, communicate status, and verify final transactions before restoring entry points gradually.

Service terms should define monitoring, notification, response and recovery targets, boundaries and incident records. Do not promise isolation without architecture and event evidence.

How this applies to AG GAME

AG GAME provides 24/7 technical support and targets second-level detection and minute-level response; actual isolation and recovery depend on the incident and project.

How should API upgrades or aggregator migration handle compatibility and open transactions?

Direct answer

Freeze current mappings, build a compatibility matrix and rollback conditions, validate with test traffic, then move new sessions in stages while the old path completes existing sessions and rounds.

Preserve player, game, transaction and round mapping; define the old-session cutoff, open-transaction query period, report retention and discrepancy treatment. Do not close an old interface while balances or states are unknown.

How this applies to AG GAME

AG GAME's public API is currently v5.0.0. Upgrade and migration plans depend on project version, wallet model and the open-transaction inventory.

How should game source, availability and supporting evidence be verified?

Direct answer

Start with the required provider, game, version and target-region list. Confirm the content source chain, available scope, validity and restrictions, and match any agreement, provider confirmation or test material to that list.

A catalog or launch URL proves technical availability only, not universal availability for every region or use. Evidence sufficiency depends on the project and applicable requirements; specialist review may be needed.

How this applies to AG GAME

AG GAME confirms available providers and games against target regions and project conditions. Public catalog, language and currency lists do not replace project-level evidence.

AG GAME

Need endpoint fields and request examples?

Read the AG GAME API reference for current endpoints, authentication parameters, request structures and errors, or contact the technical team about project capacity and launch.

Let's talk

Contact us

Discuss the cooperation scope with our business team.

WhatsAppContact channel+63 9524867581
WhatsApp

WhatsApp QR code

Scan to open the WhatsApp chat.

AG GAME WhatsApp contact QR codeOpen WhatsApp