Deposit limits: gross deposits, net figures and time windows

What changed in Great Britain?

The Commission's customer-led financial-limit changes distinguish gross deposit limits from other controls. The second implementation phase was extended to 30 September 2026. Older material still referring to 30 June should be read alongside the updated implementation announcement.

Net-based controls can still be offered, but they should not be confused with a gross deposit limit. Check the calculation and time period shown in your account. A withdrawal does not automatically create fresh gross deposit allowance.

Read the period as well as the amount

A calendar-day limit and a rolling-period control are not the same calculation. Note when the period begins, when it resets and what transactions count. Ask support to explain a rejected deposit against that specific rule rather than trying several amounts.

A hypothetical £50 gross limit with £40 already deposited leaves £10 of that period's allowance. A later £20 withdrawal does not change the £40 already deposited. This is an arithmetic illustration, not a recommended budget or an operator-specific limit.

A limit is a protection

Do not move to another card, wallet or account to evade a spending control. If the limit has become a source of pressure, take a break and consider safer-gambling help or self-exclusion.

If a transaction is missing rather than genuinely refused by the limit, use deposit triage. A financial control and a pending bank authorisation require different evidence and should not be treated as the same problem.

Which figure has reached its limit?

An account may show a cash balance, a deposit allowance and other controls on the same screen. Check the label beside the refusal before comparing those numbers. A figure headed remaining could refer to any of them. Keep the full message so you can identify which calculation stopped this particular payment.

A gross deposit count concerns money paid into the account over the relevant period. It does not subtract a later withdrawal merely because that withdrawal reduces money held with the operator. A balance, by contrast, can change through account activity without rewriting the record of deposits already made during that period.

A control based on deposits minus withdrawals is net-based, not gross. Its remaining figure may be correct for that calculation while differing from the gross allowance. Check the name above each figure before comparing them. Substituting one for the other changes the question, even if both appear in the same account menu.

A spending or loss-related control may count something different again. Money returned during play can be staked again, increasing turnover without a fresh deposit. That is why a list of stakes cannot simply replace a deposit history. To check the refusal, use the transactions counted by the particular control named in the message.

Save the control’s name, amount, period and explanation of what counts. If the remaining allowance looks wrong, those details give support a calculation to check against individual entries. A general payment-method page or another person’s account settings cannot explain which transactions this account included in its own displayed figure.

The purpose is clarity rather than finding an unused route for more spending. If a control stops a payment, changing cards or wallets does not change the protective intention behind that stop. Treat the message as information to understand through the genuine support route, not an invitation to test several other instruments until one succeeds.

How does a withdrawal affect a worked gross-deposit example?

Consider an arithmetic illustration with a hypothetical £120 gross limit for a stated period. Two completed deposits of £60 and £40 produce a £100 gross deposit total. The remaining gross allowance in that illustration is £20. These amounts are invented for explanation; they are neither a recommended budget nor the limits of a particular operator.

Now add a hypothetical £70 withdrawal. The money held in the account may change, but the two deposits remain £60 and £40 in the period's deposit history. The gross total stays £100 rather than becoming £30. Subtracting the withdrawal would change the calculation to a different quantity and would no longer describe that gross total.

If the same illustration later contains another completed £20 deposit in the period, the gross total reaches £120. A further withdrawal would still not erase any of those deposits from the period's gross record. This is an explanation of the arithmetic, not an instruction to use the remaining amount or a prediction that any specific payment will be accepted.

The illustration uses completed deposits. If your history also contains a pending authorisation, reversal or unreconciled transfer, keep its status beside the amount rather than treating it as another completed deposit. The account’s actual rules and records are needed to explain how that entry affects the control; the simple arithmetic does not settle it.

Put the deposits in date order, with the withdrawal alongside them as a separate type of entry. This lets you check the running gross total without relying on a changing balance. If the total differs from the account display, you can point to the exact entry or period boundary that appears inconsistent.

The result of the illustration is a distinction, not a personal spending plan. A remaining allowance does not establish that the money is affordable to lose, that a session should continue or that a different control will permit a payment. If the limit is creating pressure to recover money, stop and use the support page rather than treating the example as a target.

Balance, turnover and remaining allowance move for different reasons

A cash balance shows money recorded in the account at a particular point. A deposit allowance applies a control over a stated period. Turnover records the stakes committed during play. Read those labels before comparing the figures: an event can change one of them while leaving the other records unchanged.

For example, an account can contain returned money that is staked again without a fresh deposit occurring. The turnover record can therefore grow while the period's gross deposit total stays unchanged. This observation explains why counting the number of game rounds cannot independently reconstruct how much was paid into the account during the period.

A withdrawal can reduce an account balance without restoring gross deposit allowance. An outcome in a game can also change the account's recorded result while leaving the earlier deposit history intact. Those events can be genuine changes to the account without being changes to the particular quantity limited by a gross deposit control.

Keep the label and explanation beside any number headed available. It might describe a balance or an amount left under one control, while another restriction still applies. Sending only the number to support loses that distinction and may lead them to check a different figure from the one you meant.

If the issue is an unsettled game result rather than a deposit, retain the game reference. If it is an uncredited transfer, retain the payment reference. Neither question is resolved by choosing whichever remaining-allowance figure looks closest to the disputed amount. The relevant record follows the event whose status actually needs to be explained.

A precise query might say: the completed deposits in this period do not match the gross allowance shown. That is clearer than saying the balance is wrong. If you are unsure whether the issue is an incoming transfer or the limit calculation, the deposit problem directory helps separate the two questions.

Which transactions belong inside the time window?

A limit needs a period as well as a number. The amount counted in one stated window may differ from the amount counted in another because the included transactions differ. Do not remove the period label when noting a setting, and do not assume that a day, a rolling interval and a calendar boundary mean the same thing in every control.

Check when the stated period starts and ends, which time zone it uses, and which dated entries fall inside it. If the account explanation leaves a boundary unclear, ask support to identify it. Repeated payment attempts around an assumed reset time will create more entries without establishing the rule you need to check.

Imagine two labelled periods, A and B. Under the example’s stated rule, an entry in A stays in A’s total and a later entry in B belongs to B. Moving a deposit between those columns simply to increase the apparent allowance changes the premise. It does not explain how the original remaining figure was calculated.

Times close to midnight deserve a retained time-zone label. The bank record, device clock and operator history may not all display the same zone. That difference can make two genuinely related entries look like they fall on different calendar dates. It should be resolved through the records, not by guessing that one system must have reset when another clock changed.

Keep the date of the Commission’s announcement when comparing it with an older article. The implementation point originally announced may have been updated later, as described above. For an account query, then return to the control currently displayed: its name, counted transactions and period are the details needed to check that particular calculation.

Understanding the window is not a reason to resume spending at its next boundary. A reset in a control, where the rules provide one, is an accounting event rather than a recommendation. If attention has narrowed to waiting for more allowance, consider a pause or self-exclusion instead of organising further payments around the edge of a protective setting.

More than one control can be relevant to the same attempt

An account message can involve more than one kind of restriction. A deposit allowance, a bank block, an operator account check and an issuer refusal are separate matters. A payment that appears to fit one stated allowance is not guaranteed to be accepted through all of the other systems involved in authorising it.

If the account lists several financial controls, note each name and period separately. Money left under one allowance does not override another restriction. Ask which control produced the refusal. Adding or combining the remaining figures would create an allowance that the account itself has not offered and would not explain why this attempt stopped.

Similarly, an operator's acceptance of an instrument in general does not establish acceptance of a particular attempted amount. The selected cashier route and current account state are relevant to that attempt. A payment-method logo does not override a protective setting or make a rejected request evidence that the method is broken throughout the market.

Save the refusal message, the bank’s entry and the control description before making further attempts. Compare what each actually shows. No bank debit is different from a pending authorisation, and neither observation alone tells you every restriction applied earlier. These records give support something specific to reconcile without adding another attempted payment to the case.

Do not cycle the payment through more cards or wallets to see which one gets through. That works against the protection and may leave additional pending entries to investigate. Ask the organisation responsible for the message to explain it against the existing attempt, rather than using further transactions to probe the boundary.

The relevant next page depends on the evidence. A genuinely refused incoming instruction belongs with declined deposits. An amount held at the bank but absent from the account belongs with pending deposits. Pressure to continue after a control has stopped spending belongs with independent support, rather than a comparison of alternative funding routes.

Pending entries and reversals need a status, not an assumption

Your bank list may contain pending authorisations, refused requests and reversals as well as completed deposits. Similar amounts next to each other are not necessarily the same kind of transaction. The gross example used completed deposits; checking a real allowance also requires the status of each disputed entry and the account’s rule for counting it.

For each disputed entry, retain the current status at the bank and at the operator. The words pending, completed and reversed describe different states, and their meanings can depend on the service displaying them. The task is to match the specific records before deciding which entry the account's control currently includes.

A bank reservation can affect an available bank balance without independently proving a settled casino deposit. Conversely, an operator record may contain information that the bank's brief transaction label omits. Neither side's overall balance is a substitute for its individual entry, reference and timestamp when the question concerns which amount has actually been counted.

Ask whether the disputed entry is included in the control and how a later status correction affects the calculation. Keep the service’s answer with that reference. Another operator’s reversal policy cannot supply a universal release time here, and an overall changed balance cannot tell you when this particular allowance will reflect a correction.

Keep an unresolved entry separate from the confirmed completed-deposit total while its status is being checked. That leaves the gap visible instead of silently deciding it. When the responsible service explains the entry, compare its treatment with the stated rule. There is no need for a new deposit to complete that investigation.

If there are several similar attempts, identify them separately rather than treating one returned amount as proof that every attempt was reversed. A later identical amount may belong to another reference. Keeping each instruction distinct is more useful than making further tests that introduce additional entries while the original allowance question remains unanswered.

What should a limit-calculation query say?

Name the control, copy its period and displayed total, and list the individual entries you believe it includes. Support can then compare the calculation with those references. Saying only that the casino will not take money leaves open whether the question concerns the limit, the selected payment route or the bank’s handling of the attempt.

Explain the mismatch directly. Is a completed deposit apparently counted twice, is the period boundary unclear, or is a pending entry included unexpectedly? If a withdrawal was expected to restore gross allowance, that is a different misunderstanding to resolve. Keeping the questions separate helps avoid an answer about increasing a limit when you asked how it was counted.

If a screenshot helps, include the label and period rather than cropping to the remaining number alone. Remove unrelated account and payment information where the official process permits it. Passwords, login codes and full card security details are not needed to explain a control's arithmetic and should not be sent through an ordinary public message.

Ask for a written explanation of the included entries and the period boundary, then save the dated reply. If the display later changes, you can compare it with that explanation. Without the label and period, an old remaining figure may look inconsistent simply because it belongs to another control or a different time window.

The query should remain an explanation request rather than a demand for a workaround. A limit being applied as designed is not a payment defect to bypass. If the described calculation is understood but the urge to continue remains strong, use support for that pressure instead of moving the same spending intention into another account or another payment instrument.

Cashier Fieldnotes can help you identify the relevant records and phrase the question, but it cannot inspect or alter an account. Send any request for an account-specific correction through the responsible service’s process. That keeps private evidence with the organisation able to check it, while preserving the protective purpose of the control.

Review a setting without testing how close a payment can get

You can review a limit without making a payment. Open its current explanation and note the amount, period and transactions counted. If you want to reduce spending or access, use the account’s genuine controls and relevant support routes. A test deposit is not needed before taking that protective step or asking how the setting works.

An allowance is not a target that needs to be used. The fact that a displayed amount remains under a chosen control does not establish that it is affordable for the household, needed for entertainment or suitable for recovering earlier losses. The control's arithmetic and an individual's financial situation are different questions.

After requesting a setting change, check the confirmation and whether the account shows it as active. A submitted request and an active setting are not necessarily the same state. Use the current official process for any unresolved question rather than assuming the change already applies or borrowing a waiting time from another service.

After reducing a setting, read the confirmation rather than making small payments to test its edge. If the state remains unclear, ask the provider to explain what is active. More transactions could create spending and extra records without giving a clearer answer about the protection you intended to put in place.

If managing a limit feels like negotiating permission to continue despite money or wellbeing concerns, a broader pause may be more useful than another calculation. Safer-gambling support explains independent help, while the self-exclusion page distinguishes controls aimed at preventing access rather than simply counting incoming payments.

Understanding the calculation does not commit you to using the allowance. You can resolve an incorrect entry, keep the confirmation and still decide against another deposit. The review is complete when the setting and its records are clear; there is no need to demonstrate that conclusion by returning to play.

Keep a useful private note without exposing account documents

A short private note can contain the date, control name, period, displayed amount and the references needed for the particular query. It does not need to become a public record of a bank account. Store the material in a place appropriate to its sensitivity and avoid adding passwords or one-time codes to an explanatory document.

If someone helps you check the figures, agree which records they need and what question they are helping with. They do not need your credentials or another gambling account to understand the arithmetic. Account-specific checks still belong with the genuine service, using its own process for any private evidence it legitimately needs.

Keep original status labels when summarising transactions. Changing pending to failed for convenience can erase the very distinction the query depends on. If a label changes later, retain the dated change rather than silently rewriting the earlier note as though the later status had always been known.

Separate the saved fact from your interpretation of it. For example, the history may show a completed deposit, while your concern is that it falls in the wrong period. Support can then check that concern without losing the original reference and timestamp. If the interpretation changes, the underlying entry remains available for comparison.

For publication corrections, send only the source or wording problem relevant to this guide through the route described on the contact page. This publication does not need a reader's full statement or identity document to correct an explanation of gross versus net counting. Private account evidence belongs with the organisation responsible for the account.

Once the service explains the calculation, keep the answer with the current control description. That can close the accounting query without another test payment. If the investigation is feeding pressure to gamble, the support links address that concern separately; there is no need to prolong an arithmetic check until it becomes a reason to deposit again.