About this reference

Scope of this reference

Pocket Vegas is a reference about payment routes. Gambling operators, payment providers and regulators remain separate third parties. Deposits, player funds, games and bets are handled by those third parties rather than through this site.

The pages classify payment mechanisms and record dated register fields. They do not score gambling businesses. Where a company is named, it appears because it handles money on a route described here or because a public register connects it to a licence or permission on a stated date.

How a route gets described

Each route is traced to the rules that actually apply to it, rather than to how it is marketed. That means reading the licence conditions and the published guidance that defines the terms they use, and checking any status claim against the public register rather than against a company's own description of itself.

Where a question is genuinely unsettled, this reference says so instead of picking the tidier answer. Where a figure appears, it is the figure the source states.

How sources are selected

Statutory claims begin with the legislation itself. The Payment Services Regulations 2017 are used for the Schedule 1 distinction between payment services and excluded activities, including the £40 single-transaction and £240 monthly conditions attached to the electronic communications exclusion. The Consumer Credit Act 1974 supplies the basis for Section 75 rather than a summary written by a card provider or affiliate site.

Regulatory interpretation comes from the body responsible for the rule. PERG 15.5 in the FCA Handbook supplies the subject-matter test and the treatment of downstream providers in an electronic-communications chain. Gambling Commission licence conditions supply the payment- service test and the credit-card prohibition. The distinction matters because a regulator's summary can be broader than the binding condition it describes; where that happens, the page quotes the condition's actual test rather than upgrading the summary into law.

Company and permission claims use registers and corporate disclosures. FCA register files are used for firm reference numbers, entity names, permission types and effective dates. Companies House records help distinguish legal entities sharing a brand. A provider's own published terms are used for commercial fees and limits, since those figures are set by the provider rather than by statute. Secondary summaries may identify a question worth checking, but they are not treated as the final authority for a number, date or legal status.

Corrections and unresolved questions

A correction starts with the claim and the source behind it. If a reference number belongs to a similarly named company, the entity is corrected without transferring the permission across the group. If a commercial cashier limit has been confused with a statutory ceiling, the two are separated and labelled by source. This is more than a wording change: the wrong entity or wrong source changes what the figure means.

Dated facts keep their dates when corrected. A typographical error in a 25 August 2026 register snapshot can be fixed against the retained files without pretending the file was read again. A status found in a later register edition belongs to a new dated reading. It is not silently inserted into an older snapshot, because doing so would combine facts that were never true at one point in time.

Some questions remain open after the primary sources are exhausted. The published Boku entity disclosures and FCA files identify two companies and their different roles, but they do not identify which permission a particular UK gambling deposit charged to a phone bill is intended to use. The paysafecard material states the issuer and its terms but does not settle how licence condition 6.1.2 applies to a voucher bought earlier with a credit card. Those gaps stay visible. Naming a likely answer would turn an inference into a fact about a real business or rule.

Maintaining dated register references

The licence lookup uses a snapshot read on 25 August 2026. Every result repeats that date, and the operator list uses its own printed snapshot date. Neither surface describes itself as a live feed. A visitor opening the page later is still reading the dated file until a new edition is acquired, checked and published.

Register maintenance treats connected files as one edition. Domain rows link addresses to licence accounts; licence rows describe the permissions and statuses held by those accounts. Replacing one file without the other can join records from different dates. The address counts, pair counts and status totals shown on the licence page are regenerated from that same edition so the prose and the lookup do not describe different datasets.

The publication is maintained anonymously. No founder, editor or corporate owner is invented to fill that choice. The source trail, dated register labels and narrow claim boundaries carry the accountability that a fabricated biography could not.