An app labelled “exchange game” may be a sports betting exchange, a simulated game or something else. Identify the product before applying advice. This BouncingBall8 guide focuses on sports exchanges that accept back and lay requests; virtual exchange games may have different mechanics.
No app is certified safe by this checklist. We have not tested a named app or verified that it is available or authorised for use in Bangladesh.
Confirm who operates the app
Compare the app’s publisher, developer website, support domain and legal entity in its terms. A copied logo, store listing or positive rating is not proof of ownership. If a licence is claimed, check the relevant official register for the exact entity, activity and domain.
Do not confuse the app publisher with a payment business, odds supplier or game provider. Our operator-evidence guide explains the limits of familiar trust signals.
Review installation requests and permissions
Use a source you can independently connect to the genuine publisher. Do not disable device protections or install a file sent by an unsolicited support contact to fix an account issue.
Read why an app requests access to contacts, messages, microphone, location or files. Some functions can have legitimate reasons, but permission is not automatically necessary merely because the app asks. Decline or stop when the purpose is unclear. An app-store review is not a substitute for these checks.
Check the order screen before considering an order
| Field | What should be understandable |
|---|---|
| Back or lay | Which outcome the position supports or opposes. |
| Stake and liability | The worst-case loss, not only the opposing stake. |
| Price and size | Requested odds and amount available at that price. |
| Matching | Matched, unmatched and partially matched amounts. |
| Order settings | What happens after cancellation or when a market goes in-play. |
| Charges | The applicable commission or other fees and calculation basis. |
For illustration, laying 50 units at decimal odds of 4.00 creates liability of (4 − 1) × 50 = 150 units if fully matched under ordinary win/lose settlement. A clear screen must distinguish that possible loss from the 50-unit lay stake.
If only 20 units of that request match, the matched part has 60 units of liability under the same assumptions. The remaining request can still matter until cancelled or expired. Read our exchange mechanics guide.
Connection loss does not establish cancellation
Do not assume a frozen display means no order was accepted. Check the official order history and exposure before submitting again. In-play delays and suspension can prevent an intended hedge or exit.
The in-play guide explains feed timing. Keep market and order identifiers for a dispute, without sharing passwords or one-time codes.
Account and payment safeguards
Use a unique password, protect the linked email and enable multifactor authentication where offered. Check account recovery, active-session controls, verification, withdrawal conditions and the complaint route.
A familiar payment logo or responsive support chat does not establish that withdrawals work as advertised. Do not send an extra payment to an unknown person to unlock supposed winnings.
Decide what not to accept
Unclear liability, unexplained permissions, mismatched publisher details and pressure to install unfamiliar files are reasons to stop. Do not treat a checklist score as permission to gamble or a promise of profit.
Set time and spending boundaries separately from app features. See our harm-reduction resource.
Sources: Betfair on lay liability; FTC on account authentication. Calculations are hypothetical and do not verify an app. Reviewed 9 November 2026.
