Gambling deposit limits: gross deposits, periods and changes

Gross and net do not count the same movement

A gross limit counts deposits without subtracting withdrawals. A net-deposit calculation subtracts withdrawals within its defined period. A loss calculation concerns stakes and returns instead. They can produce different figures from the same account activity.

For example, suppose £60 is deposited and £20 is withdrawn during a period. Gross deposits are £60, while net deposits are £40. This is a hypothetical arithmetic example, not an operator’s account record or a suggestion to recycle funds.

Read the current definition, not an old help snippet

The Commission’s revised RTS 12 requires gross deposit limits to be offered and reserves the deposit-limit label for that definition. Other financial limits may still be available, but their calculation must be understood separately.

The implementation deadline for the revised definition was extended to 30 September 2026. Older search snippets may still mention 30 June. The current technical standard, last updated on 30 September, is the source used for this guide.

Check how the periods interact

The required gross-limit options include 24 hours, seven days and one month. Read the account explanation for when each period begins and restarts. Do not assume that every control called daily in an older help article uses the same clock.

Where several customer limits run at once, the most restrictive applies. Reaching a shorter-period cap is not permission to use a larger weekly figure. Changing a payment method should not be treated as a way around an account-level control.

Increasing and reducing a limit are different requests

A customer-led increase requires the customer’s request, a cooling-off period of at least 24 hours and positive confirmation after that period. Merely waiting does not automatically complete every requested change.

A reduction must take effect immediately, subject to the standard’s treatment of a technical failure and the information the customer must receive. If the confirmation does not match what you requested, keep the notice and ask the operator to explain the active setting.

Set the control before the payment

Find the financial-limit facilities through the account or deposit screen. Read the type, amount and period together, and retain the confirmation. A deposit route’s minimum amount is a different constraint from the personal maximum you have chosen.

Avoid selecting a limit in response to an offer, a losing session or an attempt to recover money already spent. A cap is a boundary on funding, not a target to use up. If gambling is affecting essential spending, use a break or stronger support rather than raising the boundary.

1. Open the genuine account’s financial-limit settings.
2. Read whether the calculation is gross, net, stake or loss based.
3. Choose an amount and inspect every active period.
4. Read the confirmation and effective time.
5. Check that a lower limit has actually been recorded.

What a deposit limit cannot do

A funding cap does not necessarily stop play with an existing balance. It also does not make a slot stake, insurance bet or roulette wager affordable. Those are separate decisions affecting how available money can be lost.

For time away from gambling, read the time-out guide. For an additional payment barrier, read about bank gambling blocks. Combining tools can address different parts of the account without treating any one tool as a guarantee.

Record the type, amount, period and status

A useful limit record contains the type, amount, period and active status. A figure of £50 is incomplete without knowing whether it counts gross deposits, net deposits, losses or something else. The period determines which movements are included, and the status tells you whether the setting is active or merely requested. Save those fields together when setting or reviewing a control. A screenshot showing only the number can leave the most important calculation questions unanswered.

Compare two illustrative labels: an active gross-deposit cap of £50 over seven days, and a £50 monthly loss control. The first counts deposits within its defined seven-day period; the second measures something else over a different period. Matching amounts do not make them duplicate settings. If a label is unfamiliar, ask the operator to explain it. This is especially useful where older account wording calls a calculation that subtracts withdrawals a deposit limit, even though that differs from the current gross definition.

The control's confirmation should be read alongside the current account display. If they differ, keep both and ask which setting is active. A requested increase, a completed reduction and an old confirmation can all appear in the same email history. Date and status are therefore part of the evidence, not incidental detail. The goal is to know the boundary currently applied, rather than reconstructing it from a remembered amount.

Calculate gross deposits without recycling withdrawals

Gross deposits count the deposit movements without deducting withdrawals. In a hypothetical period with deposits of £20, £15 and £10, the gross total is £45. A £12 withdrawal during the same period does not reduce that total to £33 for a gross-deposit calculation. Keep the withdrawal in its own record, but do not use it to replenish the deposit allowance. The example is arithmetic for understanding the definition, not a suggestion to make those payments.

Now give that example an active gross cap of £60, with no other deposits counted. Subtracting £45 from £60 leaves £15 under that particular calculation. It still does not establish that a £15 deposit will be accepted: another active limit or account condition may be tighter, and the actual period must be clear. The remainder explains one control only. It does not promise that the whole cashier will accept the payment or suggest that the unused allowance needs to be spent.

Recording gross and net figures separately can prevent accidental substitution. In the same example, £45 of deposits minus £12 withdrawn gives £33 of net deposits for that chosen period, under the stated simple assumptions. It remains £45 gross. A lower net figure does not mean a gross limit has reset. Write the definition beside each total so a spending review does not silently turn one measure into permission for another payment.

Put each event inside the correct period

Choose the period before adding movements. A statement month, a rolling window and a period described in the account interface may not share the same start and end. This page does not invent a universal reset clock for every account. Read the explanation actually supplied with the control and retain it if the boundary is important to your enquiry. If the account only shows a general label, ask when the period begins and how the remaining figure is calculated.

Consider why the dates matter. In an illustrative history, £25 falls before the selected period and £30 falls within it. Together they make £55 over a broader interval, but the selected period contains £30. That does not establish that a real control should exclude the earlier £25; its own window must be known first. Use the example to check that the dates in an account-history filter match the dates the limit actually covers before comparing the two figures.

Keep the timestamp and currency of each relevant movement. A transaction's displayed day can depend on the system showing it, so a bank date alone may not settle where the operator counts the deposit. Ask about the named reference if a boundary movement appears inconsistent. Do not make a new payment near a reset point to test the clock. The existing records and the operator's explanation should be used to understand how the period applies.

Work through overlapping controls one at a time

Several active controls can restrict the same proposed deposit. The most restrictive applies, so a large monthly figure does not cancel a smaller shorter-period boundary. List the active limits separately, calculate the remaining amount under each applicable definition, then identify the tightest boundary. Keep any unknown period or status visible. If a field is unclear, ask about it rather than treating the largest displayed amount as the effective permission to fund.

An account could, for example, have £10 remaining under a short-period gross cap and £40 under a longer-period cap. The longer-period figure does not free up £40 for another deposit. On those simple assumptions, the £10 boundary is tighter, and a separate protective restriction could prevent the payment entirely. This illustrates how overlapping controls interact; it does not recommend using what remains. Read each setting in context before treating any displayed remainder as the amount the account would allow.

This is also why a deposit minimum should be kept separate from a personal maximum. If a hypothetical route's minimum were greater than the remaining allowance, raising the personal cap is not the necessary conclusion. The useful observation is that the intended payment does not fit the existing boundary under those assumptions. You can leave the boundary in place and stop. A payment method should not turn a protective maximum into a target that must accommodate its minimum.

Distinguish an increase request from an active increase

The existing technical-standard source describes a cooling-off period and positive confirmation for a customer-led increase. Read any notice according to where it sits in that process. A request acknowledgement is not the same as a completed active setting, and the passage of time alone should not be assumed to finish the change. Keep the request time, the confirmation instructions and the final active display together if you need to understand what the account currently applies.

Imagine requesting a higher weekly cap, receiving an acknowledgement and still seeing the previous cap marked active. In that example, the requested amount has not been shown to apply. Read the acknowledgement alongside the account status to establish what stage the request has reached. The guide cannot supply a screen sequence used by every operator, and completing the increase is not needed to understand the records. The point is to distinguish an acknowledged request from a setting that has actually changed.

If the reason for seeking an increase is to recover money lost or to complete a payment after reaching a boundary, pause and consider a stronger break or support route. A cooling-off process should not become a countdown to a spending goal. The amount requested is not evidence that it is affordable. Keep the administrative distinction clear while treating the underlying reason for the request as a separate and important personal question.

Check a reduction against the active display

A reduction is a different instruction from an increase, and the source describes its immediate effect subject to the standard's treatment of technical failure and required information. After submitting a reduction, read the confirmation and active account setting. If the display does not match what you requested, save the discrepancy and ask the operator to explain it. Do not test the control by attempting a deposit larger than the intended boundary.

Suppose you ask to reduce a limit from £100 to £40, but the confirmation still reads £100. That illustrative mismatch calls for a question about the control: which amount is active, and what happened to the reduction request? Keep the intended instruction, the submitted request and the response together. A new payment, whether accepted or refused, adds another account movement without necessarily explaining why the confirmation differs. Ask about the setting itself before treating a transaction result as an answer.

If the account shows usage above a newly reduced boundary, ask how it presents the period and the active restriction. Do not assume that the old deposits have disappeared or that the reduction retrospectively alters the history. The ledger records past movements, while the limit concerns the applicable boundary on funding. Their relationship should be explained by the account's current instructions, with each dated record preserved rather than overwritten to force the numbers to match.

A deposit cap and a spending review answer different questions

A cap restricts funding under its definition. A spending review explains what happened over a chosen period. Deposits alone do not calculate game losses because opening balances, withdrawals and closing balances may also matter. Keep the ledger measures separate instead of treating the control's used figure as a complete statement of gambling outcomes. The transaction-history guide provides the detailed reconciliation method for money and game entries.

The difference can be shown with a simple cash-account example. Start with £20, deposit £30, withdraw £10 and finish with £15. Assuming no fees, bonuses, open bets or other movements, the game result is a £25 loss: £20 plus £30 minus £10 minus £15. Gross deposits are £30. These calculations answer different questions, and neither recommends an acceptable loss. Keep the assumptions beside the arithmetic; extra components in a real account would need to be identified and accounted for separately.

This difference also explains why a low deposit allowance does not necessarily stop play with money already held. A customer may need an access restriction rather than a funding boundary if the goal is time away from gambling. Use the time-out and self-exclusion guides for those controls. Do not treat a deposit cap as proof that every later stake is affordable or that the existing balance cannot be lost.

Read threshold language without converting it into a budget

Financial vulnerability checks and deposit limits can both mention money over a period, but their purposes differ. A published check trigger is not a personal spending allowance. A customer-set cap is not an assurance that spending up to that cap is affordable. Label each number with the process it belongs to before comparing it with the account's activity. This avoids turning a regulatory threshold or a control setting into a goal to reach.

A notice about a check might use net deposits while your personal control uses gross deposits. In that example, one history can give different totals because the definitions differ. Calculate each for the process it belongs to, and ask the operator which process the notice concerns. Splitting payments or changing instruments to avoid a check does not resolve that question. Focus on understanding the request and whether gambling should pause, rather than treating the two totals as competing amounts you can spend.

Essential spending and financial commitments are not determined by whether the account accepts another deposit. If gambling is affecting those needs, use the independent help resources and stronger protective tools instead of seeking a higher funding boundary. This article does not provide a personalised financial assessment. It explains how to read controls so an account's numerical display is not mistaken for advice about what you can afford to lose.

Keep payment-method coverage separate from the account limit

A payment route and an account-level control describe different parts of the process. Changing the card, voucher or wallet does not make an account-level boundary irrelevant. If an attempted deposit fails, read the actual message and ask which restriction applies. Do not try several instruments to discover a route around it. That approach can both undermine the protection and leave several transactions to reconcile when the original issue was a clear funding boundary.

Bank gambling blocks add another kind of barrier. Their coverage belongs to the bank's own implementation and should be read through that bank's guidance. A deposit-limit confirmation does not explain the block, and a bank authentication approval does not establish that an operator limit has capacity. Keep each control's purpose and evidence separate. If broader protection is needed, ask the bank and use operator access tools rather than treating different controls as obstacles to be defeated.

A troubleshooting note could list the attempted payment, the active operator cap and the bank-side message separately. That illustrative structure helps direct the questions: the operator can explain its setting and the bank can explain its own record. Ask about the existing reference without initiating another payment. A general description that the deposit failed loses the distinction between those observations. It also gives no basis for assuming that another payment route is available or that trying it would be appropriate.

Keep a control history that preserves changes

Save dated confirmations when a control is set or changed. A short private log can identify the old active amount, the requested amount, the request date and the final active state. It does not need passwords, full payment details or a complete account export. Preserving the sequence is useful if a later support reply refers to an earlier setting, particularly when several periods or financial controls were adjusted at different times.

A log could, for example, show a weekly reduction on one date and a monthly request on another. Merging both notices into an undated summary makes it hard to tell which control a reply concerns. Save the source message with each entry and include the relevant period when contacting support. A number alone can point to the wrong control even when the currency and account are correct. Keeping the dates and periods together preserves enough context to follow a later explanation.

If an old help snippet conflicts with current instructions, retain the dates and ask which wording applies. The existing article identifies the revised source and implementation extension rather than treating the older date as current. Do not describe this guide as freshly verified merely because you have opened it today. Public source dates, account change dates and the dates of your own observations serve different purposes and should remain distinct in the record.

Resolve a mismatch with a concrete question

To query a limit, name the control and show where its calculation is unclear. Include the displayed type, amount, period and active status, followed by the particular deposit references you think belong in the total. Ask how the remaining figure was calculated. That gives the operator a specific question to answer and leaves open whether any further payment should happen. The explanation should connect the movements it counted to the control's defined window, rather than simply say that the account will not accept more money.

If the reply uses a different definition, ask for clarification rather than replacing your notes silently. A statement about net deposits cannot explain a gross-deposit remainder without showing the relationship. A statement about a monthly cap cannot settle a shorter-period restriction. Keep the written answer attached to the question so the remaining uncertainty is visible. You can stop at understanding the boundary; no further deposit is needed to validate that you read the explanation correctly.

When the issue is resolved, record which setting is active and how its used amount was explained. Leave any unrelated check, bank block or balance discrepancy as a separate item. A clear conclusion is limited to the control reviewed. It does not predict acceptance of future payments, recommend an amount to spend or establish that other protective measures are unnecessary. The benefit is knowing what the current boundary means and keeping it distinct from the wish to continue gambling.

You do not have to use the remaining allowance

A displayed remainder explains a calculation; you do not have to use it. For illustration, £12 remaining means that the stated calculation leaves £12 within that boundary, subject to its assumptions and other restrictions. Choosing not to deposit needs no further justification. If you keep checking when the period will reset, consider whether a break from account access would address the concern more effectively than watching the funding display. Understanding the control can be a complete task without another payment.

Keep the purpose of the control in your own words beside the numerical confirmation. That might be a wish to restrict funding or to pause and review spending; it need not include a personal financial document. When later requests or messages appear, the note can help distinguish the original protective intention from pressure to raise the amount. The active limit remains a boundary, and an unexplained account calculation can be questioned without changing that intention.