Four Come feature surfaces, named for what they prove
Contest cards with captain math
Each Come match card names the contest tier, the captain pick and vice-captain multipliers, the pitch report and the settlement rule. The data shown is the same data the support desk uses to verify a Come app request, so the install, deposit and contest actions all resolve to the same source.
- Captain × 2 and Vice-captain × 1.5
- Contest tier shown before entry
- Settlement rule visible on the card
Player form, role fit, team balance
The Come roster view surfaces recent form, role fit and team balance before a contest is locked. Pick the eleven with the same numbers the captain pick math is built on; the surface is identical across deposit, contest and support flows.
- Last-five form per player
- Role-fit indicator for the pitch
- Balance warning before lock
Balance, pending withdrawals, bonus state
The Come wallet shows the live balance, pending withdrawal state, bonus state and the chosen payout route. UPI is the fastest verified path; bank transfer takes one to three working days. The fields shown match the support-desk verification flow.
- UPI · instant verified
- Bank · 1-3 working days
- Bonus state per wallet card
KYC, self-limit, notifications, VIP
The Come account surface holds KYC state, self-limit, notification preferences and VIP level. Verified: KYC is required before the first withdrawal, and the self-limit tiers are persisted server-side so they survive a reinstall.
- KYC · required before withdraw
- Self-limit · daily, weekly, monthly
- VIP · level-up cashback published
Verified feature surface. Every field listed is the same field the Come support desk verifies on request. Where a value is not published, this surface says so instead of inventing one. The verified install path is /install/.
Why these four and not twelve
The Come product surface is deliberately narrow. Match data, roster, wallet and account cover every flow the support desk is asked to verify: a contest dispute resolves against the match card, a roster question resolves against the player form and role-fit data, a withdrawal ticket resolves against the wallet state, and a KYC or self-limit ticket resolves against the account surface. Anything else a contest app might offer - chat, side games, third-party offers - is not on the verified surface, and the support desk will not verify it.
This is a feature, not a limitation. Each field on the four surfaces is the same field the support desk checks, so the answer is the same in the app, in the install walkthrough and on a ticket. Verified fields are listed with their source; unverified fields are listed as such rather than invented.
How the four surfaces map to the install route
The install walkthrough at /install/ ends with the lobby. The lobby renders all four surfaces, but only the parts of each that the device state allows. Before KYC completes, the wallet shows balance but locks deposit, contest entry and withdraw. After KYC, all four surfaces are active. A reinstall preserves the account surface (KYC, self-limit, VIP, notification preferences) but resets the contest surfaces - that is intentional, and it is the behaviour the support desk verifies when a ticket says "I reinstalled and my wallet is empty".
What the support desk will and will not verify
The Come support desk verifies match data (contest tier, captain pick, settlement rule), roster (last-five form, role fit, balance warning), wallet (balance, pending withdrawal state, payout route, bonus state) and account (KYC, self-limit tier, notification preferences, VIP level). It does not verify third-party offers, side games, chat activity or any field that is not listed on the four surfaces above. Tickets that ask for those fields are routed back to the public documentation rather than resolved on the ticket.