Affiliate disclosure.

FintechPays earns commissions on programs we cover. Below we lay out — in the regulator's own terms — what that means for you, how we keep rankings independent of payments, and where to challenge us if you spot a conflict we missed.

§1 · United States (FTC)

Per the FTC Endorsement Guides (16 CFR Part 255), every page on FintechPays that contains an affiliate link discloses the material connection above the fold. The audit-red ¶ disclosure band at the top of every page reads:

we earn commissions on programs we cover — rank determined by rubric, not compensation

We do not accept "sponsored placements" in our rankings. Programs cannot pay to move up the rubric. The most a program can offer us is to apply for inclusion; whether we cover them, and where they rank if we do, is editorial.

§2 · United Kingdom (FCA · ASA)

Under the FCA's October 2024 finfluencer rule and the ASA's CAP code (rules 2.4 + 3.1), affiliate commercial relationships must be made obvious and prominent in every piece of content. The above-the-fold band and the "¶ affiliate · compensated · does not influence rank" caption on every program card meet that standard. We publish under FintechPays Editorial Co. (UK LLP, Companies House #OC4451x).

§3 · European Union (ESMA · DSA)

EU pages disclose under the Digital Services Act Art. 26 transparency requirements and ESMA finfluencer guidance. The disclosure band on EU routes appends the EU-specific regulator citation; this is automated per market via the routing.

§4 · Gulf Cooperation Council (DFSA · VARA)

GCC pages — currently prop-trading × GCC and crypto-exchange × GCC at P1 — disclose under DFSA Conduct of Business module + VARA Rulebook §V.B.4 where the program touches virtual-asset offerings. Arabic-language disclosures are provided in the /ar/ subtree.

§5 · How we keep rankings independent

• Editorial and commercial teams operate under independent reporting lines (Maren Holst — Senior Editor; commercial via the parent LLP).
• Programs cannot view their ranking position before publication or request changes pre-publish.
• Every reliability_factor adjustment requires a documented editor_note with date + author slug. See any program review's "How we scored it" annex.
• Programs flagged as defunct or do-not-promote are not removed from public history — they move to /defunct/ with the date marked and the reason cited.

§6 · Challenge us

If you spot a conflict we missed, a reliability factor that doesn't match your experience, or a regulator citation we got wrong — write to editorial@fintechpays.com. We publish corrections at /editorial-standards/ with a dated change log.