Wecap APK download · latest version, signed build
The official Wecap APK is the only safe Android install path. The current build is v3.4 (24 MB), released July 2026, with SHA-256 verification below.
v3.4 · 24 MB · July 2026
Always install the latest build. Wecap stops supporting builds that are 90 days old; alerts stop, security patches stop, contest types roll forward.
| Field | Value |
|---|---|
| App name | Wecap |
| Package | com.wecapin.client |
| Version | 3.4.0 (build 30402) |
| Size | 24 MB |
| Released | 22 Jul 2026 |
| Min Android | 8.0 (API 26) |
| Target Android | 14 (API 34) |
| SHA-256 | Verify on /apk-download/ before install |
Verify the APK before you log in
Tampered APKs carry matching package names but different hashes. Verify before you enter any credentials.
How to verify the SHA-256
- 1Download the APK
Save the file to your phone's download folder. Do not open yet.
- 2Run a hash tool
Android file managers and most terminal emulators can compute SHA-256. Compare against the value on /apk-download/.
- 3Match the certificate
Open the APK info screen. The signing certificate must match the official Wecap publisher name.
- 4Install only on match
If any check fails, delete the file and re-download from the official link.
Update policy
- Builds ship monthly during the cricket calendar.
- Critical security patches ship as out-of-cycle releases.
- 90-day support window: alerts stop on older builds.
- Auto-update checks run on launch and once per day.
Recent builds of the Wecap APK
The Wecap Android client ships under the same package name across every release. The recent history is below; older builds are archived at the changelog endpoint.
| Version | Released | Notes |
|---|---|---|
| v3.4.0 | 22 Jul 2026 | Format rail parity, captain pick desk in app, biometric upgrade prompt |
| v3.3.2 | 08 Jul 2026 | Bug fix: deposit retry on transient UPI failures |
| v3.3.0 | 21 Jun 2026 | T10 lobby refresh, ODI captain column, methodology colophon in-app |
| v3.2.0 | 04 Jun 2026 | Improved KYC document scan, faster liveness check |
| v3.1.0 | 12 May 2026 | Test match lobby, multi-format lineup |
| v3.0.0 | 21 Apr 2026 | Major UI refresh, slate utility palette, split-axis timeline signature |
How Wecap signs and verifies every APK
Every official Wecap APK is signed with the same publisher certificate. Tampered copies break the certificate chain at install time, before any sensitive screen is shown. The signing model has three parts.
Publisher certificate
Wecap signs every APK with the official publisher certificate. The certificate chain is verifiable from the APK info screen on Android 8.0 and above.
Build provenance
Each build carries a provenance manifest linking the binary to its source revision. The manifest is verifiable from the changelog endpoint and matches the value on /apk-download/.
Code obfuscation
Release builds ship with R8 obfuscation enabled. The obfuscation map is held by the publisher and never shipped to users, so tampered binaries can't simply copy a release and rebuild it.
What to expect on the first launch
The first launch of the Wecap APK runs through five steps before you reach the play desk. Most users complete all five in under a minute on a stable connection.
- 1Welcome screen
Brief intro carousel: captain pick desk, salary cap, verified winners ledger. Skip from any screen.
- 2Mobile number entry
Same identity as the web desk. Foreign numbers are gated until KYC review is complete.
- 3OTP verification
SMS OTP plus in-app push. Validity five minutes. Biometric upgrade is offered after a successful OTP.
- 4Device binding
The first device is bound with one tap. Subsequent logins on the same device skip the binding prompt.
- 5Welcome code
If you have an active welcome code, the app prompts you to apply it before you reach the wallet menu. See /bonus-code/ for the current campaign.
Reader questions about the Wecap APK
Reader questions sent to the desk in the last quarter, answered in editorial voice. Send yours via /contact/.
Why does the APK need SMS permission?
The OTP delivery uses your carrier's SMS channel. SMS permission is required for the OTP to arrive. If you deny the permission, the OTP delivery falls back to in-app push only.
Can I install the Wecap APK on Android 7?
No. The Wecap APK requires Android 8.0 (API level 26) or higher. Older Android versions can use the web desk at /how-to-play/.
Does the APK include any third-party SDKs?
The Wecap APK ships with the minimum required SDKs: payment aggregator SDK, crash reporting, push notification SDK. No advertising SDKs, no analytics SDKs from third parties, no social SDKs.
What if my phone is rooted?
The Wecap APK installs on rooted devices but the contest engine disables certain security features. Withdrawals may require additional verification on rooted devices.
Can I run the Wecap APK in an emulator?
No. The contest engine refuses to run on emulators. The desk uses this to prevent scripted contest entry.
Storage requirements in detail
The Wecap APK is 24 MB on disk, but the app cache grows with use. The storage targets below cover most user profiles.
| User profile | Cache size | Total |
|---|---|---|
| Casual user | ~30 MB | ~54 MB |
| Daily player | ~80 MB | ~104 MB |
| Multi-format player | ~150 MB | ~174 MB |
| Heavy user | ~300 MB | ~324 MB |
What phones and tablets the APK supports
The Wecap APK runs on Android 8.0 and above. The compatibility matrix below covers the most common devices.
| Manufacturer | Tested | Notes |
|---|---|---|
| Samsung | Galaxy S / A series | Full feature support including biometric |
| OnePlus | OnePlus 8 and above | Full feature support |
| Xiaomi | Mi / Redmi / Poco | Full feature support; some MIUI permission prompts |
| Realme | Realme 7 and above | Full feature support |
| Vivo | Vivo V / Y series | Full feature support |
| Google Pixel | Pixel 4 and above | Full feature support |
| Motorola | Moto G / Edge | Full feature support |
| Nothing | Phone 1 and 2 | Full feature support |
Network requirements for the Wecap APK
The Wecap APK works on most network conditions. The table below covers the minimum and recommended targets.
| Surface | Minimum | Recommended |
|---|---|---|
| Matchday load (live contest) | 3G | 4G / Wi-Fi |
| KYC document upload | 3G | Wi-Fi |
| Withdrawal request | 3G | Wi-Fi |
| Editorial column reading | 2G | 3G |
| Push notifications | 2G | 3G |
What deep links work on the Wecap APK
The Wecap APK supports deep links from SMS, email and QR codes. Three patterns are documented below.
Contest deep link
A link like wecapin.com/contest/[ID] opens the contest directly in the app. If the app is not installed, the link opens the web desk.
Captain pick deep link
A link like wecapin.com/captain/[DATE] opens the captain pick desk for the given date in the app.
Wallet deep link
A link like wecapin.com/wallet opens the wallet menu directly. Useful for in-app customer care chat sessions.
When the APK ships, in detail
The Wecap APK ships on a predictable cadence. The release window is documented below.
- 1Monthly release
First Tuesday of each month at 12:00 IST. The release notes are published at the same time.
- 2Out-of-cycle patch
Critical security patches ship out-of-cycle. The patch is announced 24-72 hours before the rollout.
- 3Same-day hotfix
Live issues ship as same-day hotfixes. The hotfix is announced when verified.
- 4End-of-support
Builds reach end-of-support 90 days after release. Notification is shown in-app 14 days before.
Why Wecap uses APK distribution
Wecap distributes the Android build as an APK rather than relying solely on Google Play. The choice has two reasons.
- 1Speed
APK distribution lets Wecap ship updates faster than the Google Play review cycle. Monthly cycles are possible because the APK is verified by the publisher certificate, not by a third-party review.
- 2Reach
Some Android devices (Chromebooks, Kindle Fire, regional brands) don't ship with Google Play. The APK reaches these devices.