If you ticked the boxes and still want to proceed, the rest of this guide explains how the EGN issue works, what payments actually look like for UK users, and two short examples of things that went wrong and how they were fixed. Next up: the mechanics of the EGN trap and why British players specifically run into it.<\/p>\n
Why the EGN trap matters to UK punters in the UK<\/h2>\n
Honestly? It\u2019s a translation + legacy-data problem that turns into a compliance headache. Palms Bet\u2019s platform is built primarily for Bulgarian customers, so some identity fields and internal workflows expect a Bulgarian Civil ID (EGN). If the signup or deposit flow sees blank or non\u2011local values it can push the account into a manual queue \u2014 and that\u2019s when paperwork requests multiply and delays start. This matters because manual queues are where funds sit, and sometimes accounts get closed if the operator deems the ID forms \u201cnon\u2011standard\u201d or missing critical fields.<\/p>\n
That leads to an awkward trap: you might deposit \u00a350 or \u00a3100, enjoy a few spins, and then request a withdrawal \u2014 only to be asked for notarised source-of-funds or a Bulgarian-style ID number. At that point you\u2019re staring at a multi-step process that can end with confiscation if the compliance team thinks the documentation doesn\u2019t match internal expectations. Next I\u2019ll show how payments interact with this process and which rails are more\/less painful for Brits.<\/p>\n
Payments and local rails for UK players in the UK<\/h2>\n
In practical terms, Palms Bet holds balances in BGN\/EUR, not GBP \u2014 so every move involves FX. Expect conversion on deposit and again on withdrawal; that eats a bit of value compared with a UKGC operator that keeps pounds. Typical small examples: depositing \u00a320 may become roughly 44 BGN; withdrawing \u00a3100 might arrive as ~\u20ac115 minus bank FX. These are realistic numbers to keep in mind while deciding whether the entertainment value is worth it.<\/p>\n
Look \u2014 here’s what worked best for many UK punters: Revolut (depending on BIN), SEPA to a European IBAN, and Open Banking\/Trustly-style transfers when accepted. But note: PayPal and Skrill routes are often blocked for UK profiles on this cross\u2011border setup, while Paysafecard and Apple Pay can be deposit-only and offer no withdrawal path. Faster Payments and PayByBank are great options in principle for Brits, but Palms Bet doesn\u2019t always display them for non-Bulgarian accounts. Because of that mismatch, you should prepare for SEPA delays and FX costs, and get your bank comfortable with international gambling receipts before you attempt a larger withdrawal.<\/p>\n
![\"Palms](\"https:\/\/pelmsbet.com\/assets\/images\/promo\/2.webp\")
<\/p>\n| Option<\/th>\n | Payment ease (UK)<\/th>\n | KYC friction<\/th>\n | Suitability for crypto users<\/th>\n<\/tr>\n |
|---|---|---|---|
| Palms Bet (cross\u2011border)<\/td>\n | Medium \u2014 BGN\/EUR only; Revolut\/SEPA workable<\/td>\n | High \u2014 EGN expectation, manual reviews common<\/td>\n | Poor \u2014 crypto deposits uncommon; KYC still required<\/td>\n<\/tr>\n |
| UKGC\u2011licensed operator (e.g., major bookies)<\/td>\n | High \u2014 GBP balances, Faster Payments, PayPal, Apple Pay<\/td>\n | Medium \u2014 standard UK KYC; quicker turnaround<\/td>\n | Low \u2014 crypto generally not accepted on licensed sites<\/td>\n<\/tr>\n |
| European operator with GBP pockets<\/td>\n | Medium\u2011High \u2014 sometimes accepts GBP via Open Banking<\/td>\n | Medium \u2014 standard EU KYC<\/td>\n | Medium \u2014 occasional crypto rails but watch compliance<\/td>\n<\/tr>\n<\/table>\n |