Download: the official store path and what to verify first
The download chapter reads the install path against the verification path. Where the path differs, the chapter names the threshold at which the desk recommends the APK route as a fallback.
Where the install is verified
The official app store is the desk's recommended install path on both Android and iOS. The store listing carries three verification anchors: the developer badge, the build number and the developer name. The chapter walks the three anchors in order so readers can match them against the operator's own disclosure before any tap on 'install'.
A second route exists: the APK path, and it is documented separately. The APK route is the fallback for devices that cannot access the official store or for users who prefer the build version published on the operator's own release page.
Download checklist
Five steps. (1) Search the operator's own name in the store; ignore any listing that uses generic app names. (2) Check the developer badge against the operator's own page. (3) Confirm the build number matches the version on the operator's release page. (4) Open the listing, scroll to the data safety panel, confirm the wallet access is documented. (5) Install. Run the first-launch checklist from the app chapter before any deposit.
What the desk does not verify
The desk does not verify the speed of the install, the size of the APK file, the regional restrictions of the listing or the in-app promotions shown in the screenshots. Those change weekly and are the operator's responsibility to update. The desk only verifies the install path itself.
Download questions the desk receives most often
Why does the listing size differ by device?
Android and iOS ship different binary formats. The size differences are not a verification problem.
Editorial observation.Can I install from a third-party store?
Yes, but the desk only verifies the official store. Third-party stores are out of scope for this handbook.
Editorial scope.What if the operator does not list on my app store?
Use the APK route and verify the build against the operator's release page.
Editorial fallback. see APK download.Will the app store refund a mistaken deposit?
Refund policy is the operator's. The customer care chapter lists the verified routes for escalation.
Editorial scope. see customer care.Install from the official store, then run the first-launch checklist.
The install path is the simplest verification in the chapter. The first-launch checklist is the discipline step.