This article is an integration planning guide, not a substitute for current authenticated API documentation. Confirm field names, availability, and operational requirements with the integration team.
Choose a wallet architecture
Clarify whether the merchant or sportsbook is the source of truth for balances. Document who owns deposits, withdrawals, bet debits, settlement credits, and reversals.
Handle balance requests
Balance callbacks should return a consistent account balance for the correct merchant user and currency. Avoid mixing units when multiple currencies or scaled denominations are involved.
Make transaction processing idempotent
A repeated callback must not create duplicate credits or debits. Store a unique transaction reference, validate the requested action, and return a deterministic result for retries.
Plan for insufficient funds and failures
Treat insufficient balance, timeouts, signature failures, and temporary service interruptions as distinct outcomes. Keep audit logs without exposing tokens or personal data.
Reconcile every movement
Compare the merchant ledger with sportsbook transaction records and order states. Escalate unexplained differences rather than applying manual adjustments without an audit trail.
Frequently asked question
How can duplicate wallet transactions be prevented?
Use unique transaction identifiers, idempotent processing, and a persistent ledger of completed operations.
Related integration resources
Discuss your integration
For commercial inquiries or to request appropriate technical documentation, contact FB Sports on Telegram.
@Lemon95278