Install on your device — safely.
Step-by-step notes for installing the platform's app on Android and iOS. The page documents how to verify the install source, the permissions requested and the post-install verifications. It is descriptive, not promotional.
Install on Android and iOS, with safety checks.
The platform distributes its app through the published app stores for both Android and iOS. The steps below describe the canonical install flow plus a six-item safety check before, during and after install. Where the platform offers a web app as an alternative, the same safety checks apply.
Android
- Visit the platform's published download URL on the device.
- Confirm the URL host matches the published primary domain.
- Confirm the install screen names the platform's published developer.
- Confirm the file size matches the size published in the release notes.
- Install with the official app store; decline "install from unknown sources".
- Open the app and complete KYC before any deposit.
iOS
- Open the App Store app on the device.
- Search for the platform's published name; confirm the developer name matches.
- Confirm the ratings, the version number and the recent-update date.
- Install via the App Store; do not follow third-party "App Store alternatives".
- Open the app, complete KYC and then connect the deposit rail.
- Use the App Store's "purchases" view to confirm the install is official.
After install
The post-install checks mirror the pre-install checks: confirm the in-app support link, confirm the responsible-play controls are present, and confirm the deposit rail matches the planned withdrawal rail. The app access notes chapter covers these checks in greater detail.
If the install fails or stalls
A stalled install is often an issue with the device's "install from unknown sources" setting on Android, or with the App Store's regional availability on iOS. Confirm the device's settings and the published regional availability before requesting support. Where the platform offers a web app, it is a legitimate fallback documented in the same Help centre.
Six items before, during and after install.
The same six items apply before, during and after install. Tick them in order; an unticked item is a follow-up.
- Domain check: install URL host matches the platform's primary domain.
- Developer check: developer name matches the platform's published developer.
- Size check: file size matches the published release notes.
- Permission check: scope limited to storage, network and in-app camera for KYC.
- Rail check: deposit rail matches the planned withdrawal rail.
- Control check: responsible-play controls present and visible from inside the app.
What regional availability means for iOS.
The App Store's regional availability is set by the platform's App Store account. The platform may be available in the App Store for some countries and not others. The availability list is published in the platform's help centre. A reader in a country where the platform's App Store listing is unavailable should consult the platform's documented alternatives — typically the web app plus the disclosed install route.
Why the regional availability matters
A platform that is not available on the App Store in your country is not a sign that the platform is unsafe; it is a sign that the platform has not registered an App Store entity for your country. The reader should weigh the absence against the alternative paths and choose accordingly.
The fallback for unsupported countries
For a reader in an unsupported country, the cleanest fallback is the web app, accessible at the platform's published primary domain. The web app offers the same controls and the same KYC path. The reader should verify the in-app support link matches the platform's primary domain before signing up.
Reading the install safety checks as a settled pattern.
The install safety checks are a settled pattern: confirm the install URL host, confirm the developer name, confirm the file size, confirm the permission scope, confirm the deposit rail and confirm the responsible-play controls. The pattern is portable across Android and iOS; the same pattern applies to the web app and to the direct APK install path.
The Android-specific checks
On Android, the install should always go through the Google Play store. The "install from unknown sources" setting should be disabled after a single APK install. The Google Play Protect scanner should be enabled; the scanner runs a malware check on every APK install, including installs from the Play store.
The iOS-specific checks
On iOS, the install should always go through the App Store. The App Store alternative marketplaces should be declined. The App Store's regional availability check should be confirmed before any tap-to-install action. The reader in a region where the platform is not available should consult the platform's documented alternative.
After install
The post-install checks are identical to the pre-install checks: confirm the in-app support link matches the platform's primary domain, confirm the responsible-play controls are visible from within the app, and confirm the deposit rail matches the planned withdrawal rail. The cleanest approach is to run the checks in order, treating any failure as a follow-up rather than a barrier.
What the platform's installer does.
The platform's installer is the file that the platform publishes for direct install. The installer contains the platform's mobile app plus the platform's KYC, account and deposit flows. The installer is signed by the platform and is published at the platform's download URL.
What the installer offers
The installer offers a one-step install on the reader's device. The installer is what the platform publishes for users on devices without the Play store (e.g., a traveller in a region where the Play store is unavailable). The installer offers the same app as the Play store version.
What to verify before installing from the installer
Verify the install URL host matches the platform's primary domain. Verify the file size matches the platform's release notes. Verify the file hash matches the platform's published hash. Verify the permission scope matches the documented use case.
What to do after installing from the installer
After install, open the app and complete KYC. The post-install checks mirror the pre-install checks: confirm the in-app support link, confirm the responsible-play controls are present, confirm the deposit rail matches the planned withdrawal rail.
Disabling "install from unknown sources"
After a single APK installation, disable the "install from unknown sources" setting in the device's Application or Security settings. The setting is required only for further APK installations; disabling it returns the device to its secure default.
What to do when the install fails.
An install can fail for several reasons: the device is on an older OS version, the storage is full, the install source is blocked by the device, the platform's app store listing is not available in the device's region, or the install URL is a look-alike domain. Each reason has a clean fix; each reason is described below.
The device's OS version
The platform's mobile app typically requires a minimum OS version. The reader who tries to install on an older OS will see an error at the install step. The fix is to update the device's OS or to use the web app as a fallback.
The device's storage
A full device cannot complete the install. The reader who tries to install on a near-full device will see a storage error at the install step. The fix is to free up storage by clearing the cache of other apps, removing unused media or uninstalling apps the reader no longer uses.
The install source is blocked
Some devices, particularly devices managed by an employer or a school, block install sources outside the platform's app store. The reader who tries to install in this state will see an error from the device's mobile device management (MDM) policy. The fix is to ask the MDM administrator to allow the install, or to use the web app.
The app store listing is not available
Some regions do not have the platform's app store listing. The reader who tries to install in this state will see no listing in the app store. The fix is to use the web app as a fallback, or to consult the platform's documented regional availability.
The install URL is a look-alike
A look-alike URL (a domain that is one or two characters away from the platform's primary domain) should be treated as a flag. The reader who lands on a look-alike domain should not enter credentials. The fix is to navigate to the platform's primary domain directly.