card credit A deposit funded by a credit card. The clearest case: the instrument extends credit, the deposit draws on it, and the player is servicing a balance afterwards. The name on the card does not matter, and neither does the player’s intention to clear it.
Borrowed Stake / The ban
The operator’s duty
Why the company, not the customer, carries this rule
Most of the rules in this series attach to the reader’s own conduct. This one attaches to the company. An operator that accepts a deposit funded by a credit facility has broken a licensing condition, and the reason the rule is written that way is that the harm it prevents is produced by the acceptance rather than by the wish.
Direct answerA credit-card gambling prohibition stops an operator from accepting a deposit funded by a credit facility, from extending credit for gambling or from allowing an account to bet on credit. It was introduced in several licensed markets because losses funded by borrowing are larger, arrive faster and cause more harm than losses funded from the player’s own income. Compliance is a duty on the operator, enforced through its licence, and a deposit accepted in breach of it is the company’s exposure before it is anything else.
What the prohibition covers, and what it does not
covers 1
covers 2
indirect credit A deposit that reaches a credit facility in two steps. A wallet topped up by a card, or a prepaid voucher bought on credit, delivers borrowed money to the operator without the operator ever seeing a credit instrument. This is the part of the prohibition that needs the operator to look past the rail - and the part the loop page is about.
covers 3
betting on account An account allowed to bet on credit. Letting a customer place a wager before funding it, or carry an amount forward to a settlement date, is the credit product itself rather than a payment route into it. The credit account page takes that case on its own.
not covered
permitted Debit, transfers, cash and genuine prepayment. A debit card, a bank transfer, a wallet funded from a current account and cash are all funded from money the player owns, and none of them is affected. What the prohibition is not is a ban on spending; it is a ban on the operator being paid with money the player does not have.
Worked example - why the line is drawn at the rail (illustrative)
Two players, same stake, same game, same month.
Player 1 deposits 250.00 from income. Money available before the deposit: 250.00. After a month at a 96% return: expected value of the play is -10.00, so 240.00 remains, and nothing is owed.
Player 2 deposits 250.00 drawn on a card, 24.9% APR, cash-advance classification, no interest-free period, cleared after 90 days.
Interest on 250.00 for 90 days: 250.00 x 0.249 x 90 / 365 = 15.36
Expected value of the play: -10.00
Total position after 90 days: 240.00 held, 265.36 owed, net -25.36
The comparison is the whole argument for the prohibition. The same wager produces a 10.00 expected loss on one route and roughly two and a half times that on the other, and the extra 15.36 is charged whether the bet wins or loses. A rule that aimed at the player's choice would leave that arithmetic in place; a rule that aims at the operator removes the route.
What the operator is expected to do
- Screen the instrument, not the intention. A payment method is classified, and the classification is what the operator’s deposit logic is built on. A card reported as credit is refused at the authorisation step rather than after the deposit has been spent.
- Look past the first hop. The hard part is the wallet. An operator handling a wallet deposit has to reason about what funded the wallet, which is why funding-source questions - not funding-method questions - appear in the reviews described on the source-of-funds desk.
- Keep the customer’s own route visible. Where the money genuinely is the player’s but the journey is unusual, the resolution is a documented explanation rather than a refusal, because the obligation is about where the money came from rather than about which button moved it.
- Unwind a deposit accepted in breach. A deposit that should not have been accepted is normally returned when it is identified, with the balance it built removed - the same resolution shape this desk describes on the consequences page.
Why the rule is written at the point of acceptance
Because acceptance is the only moment at which the operator can act for free. After the deposit, the operator’s only options are retrospective: hold the account, unwind the deposit, argue about who is owed what. Before it, refusing the instrument costs nothing and harms nobody.
There is also a moral hazard argument that the drafting makes explicit, and it is worth stating plainly because it is the reason this desk exists. An operator whose revenue rises with the size of its customers’ losses has an interest in larger deposits, and the largest deposits in the market are the ones taken from money the customer does not have. The prohibition removes that interest at the point where the money arrives, which is precisely why it is a licensing condition rather than a term the operator writes for itself.
What this page is not. It reproduces no named regulator’s rule as if it applied everywhere, because the shape of the prohibition differs between markets and some jurisdictions permit credit betting inside a narrow permission. It also does not describe how a credit-funded deposit can be arranged so that an operator does not see it. The prohibition is explained so that a reader can read their own account’s funding clause and their own statement; where the rule bites, the money to check is the money that funded the stake.