Editorial Policy
We publish our own verified picture of iGaming payments, not a catalog of other people's claims. That standard has consequences: load-bearing facts trace to primary sources, dates on pages are real modification dates, and when we get something wrong, the correction is public. This page is the whole contract, including the part most publishers skip: the log of our own errors.
What we publish, and in whose voice
Assertions on this site are made in our voice, because we have done the work to stand behind them. Sources appear as evidence, not as shelter: when we write that a provider holds a license, we checked the register, and the citation is there so you can too. Where we could not verify a claim, we say so explicitly, and phrases like self-reported, provider-stated or not register-verifiedare our verdicts on the evidence, not decoration. Attribution of the "according to X" kind is reserved for two cases: claims we could not independently confirm, where the attribution is a warning, and figures that are inherently non-public, where it is the honest limit of anyone's knowledge.
Nothing here is sponsored and nothing is ranked for money: the scoring is built from data under a published methodology, providers cannot pay to enter the catalog or improve a score, and the details live in our methodology and advertising policy. We publish without bylines, deliberately: reviews are produced by an editorial process rather than a personality, every substantive claim is checkable against the cited source, and the site stands behind the work as one voice.
The evidence bar
Load-bearing facts, the ones a reader might act on, must trace to a primary source: a regulator's register, a legislature's record, a network's published rules, a company's own filing. Trade press can point us at a story; it does not get to be the evidence, because trade-press dates and numbers drift, and our corrections log below documents cases where they drifted onto our pages before we tightened this rule.
License claims get the strictest treatment. We audit them against the registers themselves, entity by entity, because registers are brand-blind and marketing is not: the series so far covers the ESMA CASP register, the UK FCA register, the Brazilian central bank and six US state gaming registers. When a register cannot be publicly checked, we say "not checked", never "not found", and claims that fail verification are reframed on the provider's review the day the audit closes, in both directions: overclaims get flagged, and providers whose cards undersold their real licensing get upgraded with the same diligence.
Numbers we cannot trace do not run. That includes statistics whose trail ends at content farms, single-vendor claims with no second source, and round numbers that every outlet repeats and none can origin. Where our own catalog is the dataset, figures are computed from it at build time rather than typed in, so they cannot drift from the underlying data.
Dates and freshness
The visible "Updated" date on any page is the date its content substantively changed, and it is the same date the sitemap and structured data carry. We do not scatter fresh-looking dates across unchanged pages; a date only moves when the content does. Provider reviews run on a quarterly re-verification baseline, 75 providers deep, with an event-driven layer on top: a register audit, a rule change or a market launch triggers same-day updates to every affected page instead of waiting for the next scheduled pass.
Corrections policy
When we find a factual error in something we published, we correct the text, move the page's modification date, and record the error in the public log below: what we said, what is correct, and how it surfaced. Most entries come from our own verification passes; that is the point of running them. Errors of judgment (a score you disagree with, an editorial call) are not corrections; errors of fact are, and the difference is whether a primary source settles it.
If a provider disputes a factual claim on its review, we investigate against primary sources. If they are right, we correct it and log it here. If the dispute is with our scoring or framing, we explain our reasoning and the score stands. Spotted an error, on any page? Tell us, ideally with the primary source, and it gets the same treatment.
Corrections log
Our published errors, newest first. Maintained from July 2026; earlier fixes were folded into the July audits. Claims by others that we refuted before publishing live in the articles, not here.
Compliance calendar
- What we published:
- The April 18 CE 3.0 row stated that a per-qualification fee applies from April 17.
- Correction:
- Removed. The fee claim traces to a single vendor write-up and to no primary or second independent source. It returns if corroborated.
- Surfaced by:
- Primary-source verification for our CE 3.0 article.
Paramount Commerce review
- What we published:
- Profile prose still described the UK subsidiary, Citadel Commerce UK Limited, as FCA-authorised in five places, and presented "Malta FIAU" as a licence.
- Correction:
- The FCA authorisation (FRN 575193) was cancelled July 12, 2024 per the FCA register; the structured card was fixed on July 14 but the prose lagged until our Malta audit caught the desync. FIAU standing is an AML registration, not a licence, and is not publicly verifiable.
- Surfaced by:
- MFSA/MGA register audit.
Xace review
- What we published:
- The Malta authorisation was dated "February 2024".
- Correction:
- January 18, 2024, per the EBA/MFSA register.
- Surfaced by:
- MFSA/MGA register audit.
Aeropay review
- What we published:
- The card stated that no state gaming vendor licenses were found in public records.
- Correction:
- Aero Payments, Inc. holds 2025-vintage gaming vendor registrations in PA, NJ, MI, WV (interim supplier license) and CO, all register-confirmed. True when written, wrong by mid-2026.
- Surfaced by:
- US state register audit.
Pavilion Payments review
- What we published:
- New Jersey was listed first among the company's state gaming approvals.
- Correction:
- No Pavilion, Global Payments, VIP Preferred or CPay entity appears in the NJ DGE Active Vendors Report (July 14, 2026 edition). NJ removed from the license list until the register shows it.
- Surfaced by:
- US state register audit.
Nuvei review and industry report
- What we published:
- "Licensed or authorized in 48 states + DC + PR" was presented without a time anchor.
- Correction:
- The figure comes from the 2023 annual filing, the last public one before the November 2024 take-private (SEC Form 25-NSE). Now marked frozen-in-time, with the gaming-side registrations re-verified against six state registers.
- Surfaced by:
- US state register audit.
OKTO review
- What we published:
- Brazil access was described as running "via partner U4C".
- Correction:
- U4C was renamed OKTO IP S.A. and control passed to OKTO in January 2025 per the DOU: a captive authorized payment institution, a stronger setup than our card described.
- Surfaced by:
- BCB register audit.
Paramount Commerce review
- What we published:
- The card carried an active FCA authorisation claim.
- Correction:
- The authorisation was cancelled July 12, 2024 per the FCA register; the claim had sat stale on our card for two years.
- Surfaced by:
- FCA register audit.
Industry report (two entries)
- What we published:
- Two report facts cited secondary sources that failed our verification standards on re-check.
- Correction:
- Both entries replaced with facts traceable to primary sources (a company announcement on PRNewswire; Congress.gov).
- Surfaced by:
- Full industry-report re-verification.
Europe region page, payments-challenges guide, industry report
- What we published:
- Sweden's gambling credit-card ban was dated April 1, 2026, in four places.
- Correction:
- May 1, 2026. The effective date moved during the Riksdag process, confirmed via Spelinspektionen; an outdated trade-press date had propagated across our pages.
- Surfaced by:
- July content audit.
PSP comparison and Curacao articles
- What we published:
- MiCA authorization wording in two older articles contradicted our own MiCA register audit.
- Correction:
- Synced to the ESMA register snapshot the audit is built on.
- Surfaced by:
- July content audit.
Cite the work with confidence
Attribution rules, our most-cited figures, and how to reach us for expert comment are on the press page.