Safeguarding Player Funds: What Coinbase's €3.25M Fine Shows

Safeguarding player funds means being able to show, on any given day, whose money sits in which account and which record proves it. On 22 October 2026 the Central Bank of Ireland fined Coinbase Ireland Limited €3,252,618 because it could not show that reliably, even though no customer lost money.

The period covered runs from 1 November 2020 to 19 August 2025. The settlement notice puts the starting penalty at €4,646,597, cut by 30% under the settlement scheme. The sanctions still need High Court confirmation before they take effect. Coinbase has said it identified and reported several of the issues itself, and that no customer lost money or lost access to funds.

Coinbase Ireland is an e-money institution, so the fine was issued under Irish e-money rules, not MiCA. A game marketplace that holds player money is a different business under a different rulebook. The question is the same, though. At each step of a sale, whose money is it, where does it sit, and what record proves both?

What the Central Bank found

The settlement notice describes three failures that ran together for years.

The designated safeguarding account was underfunded. A shortfall existed on a daily basis for at least 18 months. The largest daily shortfall was €3.4 million in 2023 and €5.2 million in 2024. The average daily shortfall was 0.54% of the amount Coinbase Ireland had to safeguard, which averaged €323 million in 2023 and €470 million in 2024. The notice adds that the firm’s systems could not accurately calculate each day how much it was obliged to safeguard.

Customer money also sat in other entities’ accounts. On 2 March 2023, ahead of the Silvergate Bank failure, Coinbase Ireland told 30 institutional customers to deposit US dollars into an account held by Coinbase Inc., its US group company, and not by the Irish entity. That lasted until October 2024, about 19 months. Separately, some customers who had moved over from Coinbase UK after Brexit kept paying into the Coinbase UK safeguarding account. When the firm found 33 customers who still had access to it in August 2025, it blocked all deposits there from 19 August 2025.

Coinbase Ireland argued that the funds were still protected: each deposit was credited to an individual customer ledger, the US accounts carried FDIC insurance, and the money counted in its safeguarding calculations. The Central Bank rejected that. The rule against mixing customer money with another person’s funds, it wrote, is absolute and allows no exceptions for ledgering, insurance or custodial calculations.

The third failure was oversight. Coinbase Ireland outsourced the safeguarding function to a US group company without enough local expertise to supervise it, and it lacked a process to spot material changes in how funds were held and report them to the regulator.

The systems moved money every day without incident. The failure sat in the records: on a given morning, they could not show how much the firm owed customers.

One sale, followed from payment to payout

Take a single trade. A player sells a cosmetic item to another player for 100 USDC. The marketplace fee is 10, so 90 is owed to the seller. Assume the fee is earned only when the dispute window closes and the marketplace holds the funds while the sale settles. Those are assumptions. Change any of them and the ownership at each step changes too. This is an illustration, not a record of any real marketplace.

Step	Whose money is it	Where it sits	Record that proves it
Buyer pays	Still the buyer’s until the transfer lands	In transit, or inside a payment processor	Pending receipt tied to this sale, buyer and item
Payment lands	Owed to the buyer or seller, depending on delivery	Pooled player-funds account, kept apart from operating cash	Ledger line per user and per sale
Hold	Nobody’s spending money yet. The buyer can still reverse it	Same pooled account	Liability entry, not revenue
Split	10 is the marketplace’s, 90 is a payable to the seller, any royalty is a third payable	Fee swept out only now	One ledger line per owner
Payout	The seller’s, until the rail confirms	In flight, then the seller’s account	Payout record matched to the rail’s confirmation
Reversal	Whoever the contract says funds the refund	Reserve held back, or the marketplace’s own funds	Reserve balance and reversal log

Where the first fork sits

The payment lands in one of two places. If it goes into the company’s operating account, it is mixed with fee revenue and payroll float from the first minute. If it goes into a pooled account kept for player balances, it is still mixed with other players’ money, but not with the company’s. A pooled account can be perfectly traceable without one bank account per player, as long as an internal ledger attributes every unit to a person and a sale and a daily check confirms that the account balance equals the sum of those attributions.

The hold and the split

Between payment and payout there is usually a gap: item delivery, a dispute window, a chargeback window on card payments, or the number of blocks your policy requires before a transfer counts as final. During that gap the 100 is a liability. Booking the 10 as revenue early is how a balance sheet starts lying.

When the window closes with no dispute, the 100 divides. The 10 becomes the company’s money, and only now. The 90 becomes a payable to the seller. A studio royalty is a third payable, and tax withholding, where it applies, a fourth. The only defensible moment to move the 10 into the operating account is after this split.

Payout and reversal

In-flight money is where reconciliations go wrong. Count a payout in both the pooled account and the transfer and you double count. Count it in neither and you have a hole. A failed payout has to reverse the payable back to the seller, not drop out of the books.

A late dispute or a transfer that looked final and was not forces the money to come back from somewhere. If you have already swept the fee and paid the seller, it comes back from your own funds. A reserve held from each sale until the reversal window closes is one way to cover that. Decide whose money pays for a reversal before one happens.

Where the trace breaks

The Coinbase case maps onto five places where a marketplace loses the ability to answer the question.

Commingling puts fee revenue and seller balances in one account, with a ledger that records totals but not owners.

Entity mismatch is the one that cost Coinbase Ireland. A studio company, a marketplace company and a parent each hold part of the flow because that was the convenient account to open. A customer who pays into the wrong entity has paid a different legal person than the one who owes them, and moving the money across the next morning only shortens how long that lasted.

The omnibus wallet is the onchain version. One hot wallet receives every deposit, and nothing onchain says which part belongs to which player. That works only if an offchain ledger says it and someone reconciles that ledger against the wallet balance every day. A wallet with no ledger is a pile of money with no owners. A ledger with no matching wallet is a list of promises.

The underfunded account is what the daily shortfall figures describe: liabilities of 470, assets of 465, and a process that does not alarm anyone because the gap is under one percent. A reconciliation nobody reads is not a reconciliation.

The oversight gap is the last one. A payment provider, a custodian or a group company runs the process, and nobody on your team can describe its controls or notice when they change. Outsourcing moves the hands that hold the money. It does not move the obligation to know where the money is.

What MiCA says about client funds

If your marketplace provides crypto-asset services such as custody, exchange or transfer for EU players, it may be a crypto-asset service provider (CASP) under MiCA. Article 70 of Regulation (EU) 2023/1114 covers the safekeeping of clients’ crypto-assets and funds:

• Article 70(2): where the business model requires holding client funds, the CASP must have adequate arrangements to safeguard clients’ ownership rights and prevent the use of client funds for its own account.
• Article 70(3): by the end of the business day after receipt, the CASP must place client funds other than e-money tokens with a credit institution or a central bank.

Article 111 sets fines of up to €5 million or 5% of annual turnover, whichever is higher, for providing crypto-asset services without authorisation. Whether your marketplace is in scope depends on the services it provides and how the tokens are structured. Most studios with onchain trading are worth checking, and the CASP licence check is a quick way to see where yours lands. For the wider picture, see our guide to Web3 game compliance and what CASP licensing means for game developers. Licence costs are broken down in Web3 gaming compliance costs.

What a CTO can check this week

None of this is legal advice, and none of it needs a licence to start. These checks are bookkeeping.

1. Draw the path of one real sale from your own system. Next to each step write who owns the money, which account or wallet holds it, and which record proves it. Every blank goes on the list.
2. Confirm accounts and wallets are titled in the legal entity that actually owes the players. A parent company’s account holding player funds is the pattern in this case.
3. Check that the ledger attributes balances to a user and a sale, and that pending, payable, fee and reserve are separate lines. Record revenue only once the fee is earned.
4. Reconcile daily. Name one owner, set the threshold for a difference that must be escalated the same day, and write down who receives the escalation.
5. Read your provider’s controls yourself, or have someone on the team who can. Ask what happens to in-flight transfers if the provider fails, and whether player funds are segregated from the provider’s own money in a way that survives its insolvency. A ledger does not create that protection. The contract and the account structure do.
6. Decide in writing which balance covers a refund or a reversed payout, and when fee revenue may leave the player-funds account.

The test is a plain one. Take yesterday’s sales and produce, this afternoon, a figure for what you owe players and a figure for what sits in the accounts that back it. If the two match and you can show the working, you are ahead of where this case started. If they do not, the size of the gap matters less than the fact that you can now see it.

Genesis Engine, built by Triolith Games AB, is designed to put custody, the player-funds ledger and reconciliation at the platform level, so a studio does not run that stack alone. You can read how it fits together on the Genesis Engine page.

FAQ