Deposit limits, the platform-side cap.
A deposit limit is set on the platform, not on the sticky note. The cap is harder to override than the session budget, because the cap is what the platform enforces.
What a deposit limit is
The cap that the platform enforces.
How to set the cap
Set the cap to a number you would be comfortable losing across the period. The number should match the session budget multiplied by the expected sessions.
Expected sessions
Most readers play two to four sessions per week. Pick the lower bound of your expected sessions and set the weekly cap accordingly. A reader who plays four sessions per week with a 500 budget per session should set the weekly cap at 2000.
The 7-day cooling period
Most platforms offer a 7-day cooling period on changes to deposit caps. The cooling period prevents a reader from raising the cap in the heat of a session. Leave the cooling period on. The platform knows this is a discipline lever.
When to lower the cap
Lower the cap after a losing week, not after a winning one. The opposite is more common; the discipline is to lower after losses and hold after wins.
The discipline test
A reader who lowers the cap after a winning week and raises it after a losing week has lost the discipline. The cap should move in one direction: down after losses, hold after wins. The mechanical test makes the rule easier to follow.
A clean reset
A clean reset means holding the cap for a year and reassessing at the year mark. A reader who reassesses monthly can find reasons to raise the cap every month. The yearly reset is the cleanest period.
Questions about deposit limits
The questions the desk hears most about platform deposit caps.
Most platforms impose a cooling period. The cap can be raised only after the cooling period has elapsed. Leave the cooling period on.
You cannot lose more than the cap, because the cap limits how much you can deposit. The cap protects against the recovery deposit, which is the most expensive habit at the desk.
Most platforms allow a daily, weekly and monthly cap on the same account. The desk recommends setting all three.
Other responsible-play controls
Deposit limits are one of three platform controls. Time reminders and self-exclusion sit beside it.
Where the cap sits in the wider control stack
The cap is one of three layers, and it sits in the middle.
A reader who has set a session budget controls the spend in a single sitting; a reader who has set a deposit cap controls the spend that can possibly arrive at the table across the period. The two controls point at different things. The session budget answers the question "how much will I lose tonight"; the deposit cap answers "how much can I send to the platform before the period resets". A reader who has only set the session budget has set the cheapest lever; a reader who has only set the cap has skipped the front line; a reader who has set both has the discipline of the middle path.
The three layers, in order
The desk reads the controls as three layers. The first layer is the session budget, which is a number on the reader's own sticky note. The second layer is the deposit cap, which is a number on the platform. The third layer is self-exclusion, which is the lever that stops everything. The order matters. The session budget is the cheapest and most flexible; the deposit cap is the next rung, set on the platform and harder to override; self-exclusion is the last rung, set when the first two have not held.
Why the cap is the harder lever
The session budget can be overridden in the moment, with a sticky note pushed aside or a notepad closed. The deposit cap cannot. Once the platform has refused a deposit, the reader is forced to either sit at the table with the existing balance or stop. The forced stop is the design. The platform is the silent co-author of the discipline, and a reader who has set the cap has outsourced part of the decision to a piece of software that does not get tired, does not get bored, does not chase a loss.
Designing a cap that will last a year
Pick a number you can hold on a bad week, not a good one.
The hardest part of the deposit cap is not setting it. The hardest part is leaving it alone. A reader who sets the cap during a quiet week and reconsiders it during a noisy week will move the cap every month, and the cap stops being a control the moment it becomes a moving target. The cap should be designed on a day when the table is irrelevant, and the number should be one that survives contact with the table later.
A household test, not a personal test
The desk recommends a household test rather than a personal test. The deposit cap affects the household budget even when the spend does not. A reader who has set a weekly cap of 2000 but who is also funding a school fee, a rent payment or a medical insurance premium in the same week is competing with the cap for the same rupee. The test is mechanical: would missing one weekly cap, multiplied by four, change a planned household expense? If yes, lower the cap.
The annual review
The annual review is the only review the desk recommends. A reader who reviews the cap monthly finds reasons to raise it; a reader who reviews it weekly will raise it every week. The annual review has one question: did the cap cause a real financial problem in the year past? If the answer is no, leave the cap where it is. If the answer is yes, lower it. The cap moves in one direction only.
The cushion principle
A reader who has set the cap at exactly the spend ceiling will hit the cap before the period ends, and the hit will feel like a failure. The desk recommends a small cushion, roughly ten per cent below the ceiling the reader can actually afford. The cushion is the difference between a cap that holds and a cap that is breached in the third week and abandoned in the fourth.
How caps interact with bonuses and credits
The deposit and the credit are not the same rupee.
Most Indian platforms offer sign-up bonuses, daily login credits, referral credits and tournament tickets. The cap, by default, counts only the deposit. A bonus added by the platform does not add to the cap, because the bonus is not a deposit; it is a credit. A reader who has set a weekly cap of 2000 and who receives a 500 sign-up bonus is still capped at 2000 in deposits; the bonus sits on top.
Why this matters at the table
The distinction matters at the table because the credit can be lost. A reader who treats the credit as house money and chases a session with it has not technically breached the deposit cap, but has lost 500 of credit on top of the 2000 the cap was designed to govern. The discipline is to treat the credit as part of the session budget, even when the platform separates the two balances in the lobby.
Reading the bonus terms
The bonus terms are on the operator page. The desk recommends reading the bonus terms before accepting any credit, and the deposit cap should be designed without counting on the bonus as a regular feature. A reader who builds the deposit plan around a recurring bonus is planning against a credit the operator can withdraw at any time, and the plan will fail when the credit ends.
Free tickets and tournament entries
Free tickets to tournaments are similar to credits. They do not count against the deposit cap. They also do not count against the session budget unless the reader adds cash to the same session to chase the freeroll further. The cap is the cap on deposits; the session budget is the budget on the table; the two should be set independently.
Across platforms, currencies and shared accounts
The cap is per account, per platform, per currency.
A deposit cap set on one platform does not follow the reader to the next platform. The cap is set in the responsible-play section of the account, and the account belongs to one operator. A reader who plays on two platforms has two caps to set, two cooling periods to honour, two reviews to run. Setting the cap on the larger platform only is a common mistake; the smaller platform becomes the recovery path.
Currencies and conversions
Some platforms accept deposits in rupees, others in dollars or in a platform-specific token. The cap is usually set in the deposit currency, not in the rupee equivalent. A reader who deposits through a payment gateway that converts at the moment of deposit should design the cap against the rupee budget and let the platform convert. Setting the cap in dollars and the budget in rupees creates a moving target every time the exchange rate shifts.
Shared or household accounts
A reader who shares a wallet with a family member, or who uses a single payment method across accounts, has a problem the cap cannot solve on its own. The cap is set on the platform account, not on the payment method. A reader who has capped one platform at 2000 per week and who holds the same debit card on a second, uncapped platform is using the same rupee twice. The fix is to cap every platform that holds the same payment method, or to remove the payment method from the platforms that are not in active use.
The pause between platforms
The desk recommends a pause between platforms. A reader who has set the cap on platform A and who then opens platform B in the same week should set the cap on B before the first deposit. Setting the cap after the first deposit is too late; the cap will read as a reduction, and reductions are harder than fresh caps. The rule is mechanical: cap before deposit, not after.
When the platform does not offer a cap
Cap the payment method instead of the platform.
Most major Indian operators offer deposit caps in the responsible-play section of the account. A small number of operators, particularly those that route deposits through third-party gateways, do not offer a cap on the platform itself. The reader in that situation is not without options. The cap can be set on the payment method, which is the layer the platform does not own.
Card-level controls
Most Indian banks offer daily, weekly and monthly caps on debit cards and credit cards. The caps are set in the card-management section of the bank's app or netbanking portal. A reader who cannot cap the platform can cap the card; the platform will refuse the deposit when the card declines, and the card decline reads the same way as the platform-side cap, to the reader.
UPI and wallet limits
UPI apps and third-party wallets also impose per-transaction and per-day limits. The limits are set by the payment service provider and the bank, not by the platform. A reader who is using UPI for deposits can lower the daily UPI limit at the bank and raise the friction on the deposit; the deposit will fail at the UPI step rather than at the platform step, which is a less clean refusal but is still a refusal.
The pre-funded wallet
Another route is the pre-funded wallet. A reader who loads a small fixed amount onto a separate wallet each week and uses that wallet for deposits has effectively self-imposed a weekly cap, because the wallet empties before the cap could be breached. The wallet is a manual cap, and the manual cap is weaker than the platform-side cap, but it is better than no cap.
Switching operators
If none of the above works, the cleanest answer is to switch operators. A reader who is using a platform that does not offer deposit controls is using the wrong platform, and the responsible-play levers are part of the product. The desk does not name operators, but the reader should expect any licensed Indian operator to offer at least daily, weekly and monthly deposit caps as a baseline.
Questions about deposit limits
What readers ask the desk most often about platform-side caps.
No. The cap covers deposits only. Bonuses, free tickets and promotional credits sit on top of the cap and are governed by the platform's promotional terms, not by the cap.
Most platforms allow the daily cap without the weekly cap, but the desk does not recommend the configuration. The weekly cap catches the pattern of seven small deposits in seven days, which the daily cap alone does not.
Cap the payment method instead. Card-level limits, UPI limits and a pre-funded wallet are all workable substitutes. The cleanest answer is to switch operators if the platform offers no controls at all.
No. The cap should be set per account, per platform, per currency. A shared rupee budget can be split across platforms, but the cap on each platform must be set independently in the responsible-play section.
The cap is the cap. A reader who needs to deposit more than the cap for a single session should treat that need as a warning sign, not as a problem the cap should solve. The warning sign is what the cap is for.
When a cap is not enough
A deposit cap is a tool, not a treatment.
A cap works when play is broadly under control and the reader wants a boundary that holds on a bad night. A cap does not work when the impulse to play has stopped responding to boundaries altogether. If you find yourself raising the cap repeatedly, waiting out the cooling-off period in order to deposit again, or looking for a second account or another payment route once the cap binds, the cap has stopped being the relevant question.
That pattern is worth taking seriously rather than managing with a tighter number. The desk is an editorial publication and is not qualified to give clinical or financial advice. A reader in that position should speak to a qualified professional, and may want to combine that with self-exclusion and with bank or payment-method blocks that sit outside the platform's control.