Spending controls
A limit should stop the transaction.
A spending limit is not much use if it only generates a warning after the money has gone.
Beaver's Live spending controls are enforced where the spend happens.
Set the boundary. Enforce the boundary.
The current good practice context
What the Code asks for.
For relevant signatories, the DCMS Code says operators should either apply suitable and proportionate maximum monthly total spending limits, or give players the ability to set individual monthly total limits across the operator's prize draws.
Where player set limits are used, customers should be able to set them early in the relationship and should be allowed to set the value to £0.
The Code also sets specific credit card restrictions, including a £250 monthly credit card limit per player and no credit card payments for instant win prize draws.
Those are external good practice expectations. Here is what Beaver actually does.
Checkout enforcement
This is the important bit.
A weak spending control says "you have exceeded your limit" after the purchase. A useful control prevents the transaction that would exceed it.
Live Beaver's spending caps are enforced at checkout and on top ups.
A spending report describes what happened. A spending control changes what can happen.
Audit record
Illustration of where enforcement happens, with example values. Not the Beaver product interface.
-
Player monthly limit
Let the player set the ceiling.
Live
A monthly cap set by the player. The useful part is not the settings form. It is the enforcement at checkout and on top ups.
The number matters at checkout, not only in settings.
-
Operator platform cap
The platform can set a ceiling too.
Live
An operator level cap the customer cannot exceed, even where their own limit would otherwise allow more. The effective boundary is whichever applicable rule is more restrictive.
PLAYER LIMIT | OPERATOR CEILING | AVAILABLE SPEND | CHECKOUT -
Limit increases
Raising the boundary should not be immediate.
Built
Cooling off on spending limit increases: a raise does not take effect immediately. We will state the exact delay once that configuration is confirmed, rather than invent one.
Lower now. Raise later.
-
Credit cards
Credit card caps and instant win blocking.
Built
A rolling 30 day credit card spending control, and payment method filtering intended to prevent credit card use on instant win products.
The control logic is built. Production enforcement still needs real merchant validation.
Still to confirm
Tiny details we will not guess.
Claim discipline applies to small things too. Before we publish them, we are confirming from the product:
- That the player limit accepts and enforces £0
- The exact cooling off duration
- Exactly which transaction types count towards each limit: purchases, wallet top ups, promotional credit, refunds
If we cannot explain what counts towards the limit, we have not explained the limit.
Evidence
A limit should leave a trail.
A spending control should leave enough evidence to answer: what was the configured limit, what was the current spend, which transaction was prevented, did the limit later change, and who changed an operator controlled value.
Live Beaver's audit system records actor, reason, before and after values for sensitive changes involving money, entries or marketing.
Questions
Asked and answered
Does Beaver have player spending limits?
Yes. A player set monthly cap is Live.
Can an operator set a maximum too?
Yes. A platform spending cap per operator is Live.
Where are the limits enforced?
At checkout and on top ups.
Can a player immediately increase their limit?
A cooling off mechanism for limit increases is Built. We will state the delay once the configured duration is confirmed.
Does Beaver enforce the DCMS credit card restrictions?
The credit card logic is Built, including a rolling cap and blocking credit cards on instant wins. Production merchant validation is still required before we describe that behaviour as proven live.
Primary sources
Where this page gets its facts
- DCMS: Voluntary Code of Good Practice for Prize Draw Operators(opens in a new tab)Spending limits and credit card restrictions.
Checked 19 September 2026. Guidance changes; always read the current version at source.
See it stop a transaction
Settings are easy. Enforcement is the product.