CHANNEL 01
SecureDrop
For documents and source materials. Routes to a hardened intake, accessible only via the Tor Browser. Our editors never see your IP or device.
fintechly3xqzh7y4.onion
USE THE TOR BROWSER. DO NOT ACCESS FROM A CORPORATE NETWORK.
fintech.infrastructure.media
The journal of record for the people building modern finance.
THE NEWSROOM
Premium readers and serious sources are entitled to know how a publication is built. This page is the public version of our internal standards — the sourcing, the conflicts policy, the corrections log, and the channels that protect people who tell us things.
LAST REVIEWED · 24 APR 2026 · BY THE EDITOR
OUR PROMISES TO READERS
01
We verify before we publish.
If a story is not ready, it does not run. We would rather be second and right than first and sorry.
02
We protect our sources.
We never burn a source. We absorb legal risk before we expose anyone who told us the truth.
03
We tell you when we were wrong.
Corrections are public, dated and named. Significant errors are republished in the next Ledger.
SECTION 01
The eight rules every reporter and editor at Fintechly works to. Read in full, in plain English.
DOWNLOAD THE HANDBOOK (PDF)01
Every piece of original reporting is sourced. We aim for at least two independent, knowledgeable sources on any material claim. We do not run anonymous quotes that exist only to attack named parties. Where we cite documents, we have read them in full ourselves.
02
We grant anonymity to sources who would face professional, legal or personal consequences for speaking on the record. We do not grant it for convenience. We disclose, in plain language inside the story, why a source has been granted it.
03
We honour reasonable embargoes that are agreed in advance. We do not honour retroactive embargoes. We will not embargo information that is materially in the public interest.
04
Reporters and editors cannot own equity in any company they cover, or write about a company in which a spouse, partner or first-degree relative is an employee, board member or material shareholder. Recusals are documented internally and disclosed to readers when relevant.
05
Anything paid for by a sponsor is marked PARTNER CONTENT in the same mono label as our own sections, in equal weight, on every surface. Sponsors do not see editorial copy before publication and have no influence over headlines, framing or selection.
06
We use machine-assisted tools for transcription, translation, code search and visual production. We do not generate quotes, paraphrase sources, fabricate scenes or auto-publish copy. Every published sentence is read and approved by a human editor.
07
Anyone named in a critical piece is contacted in advance with a fair opportunity to comment, with sufficient notice for a considered response. Their position is represented in the published piece, in their own words wherever possible.
08
When we get something wrong, we correct it in the original piece, mark the change clearly, and log the correction publicly on this page. Significant corrections are also republished in the next edition of The Ledger.
SECTION 02
Three credible, defended ways to reach Fintechly with information you would not put in plain email. Pick whichever is operationally safest for you. We respond to most legitimate approaches within 48 hours.
CHANNEL 01
For documents and source materials. Routes to a hardened intake, accessible only via the Tor Browser. Our editors never see your IP or device.
fintechly3xqzh7y4.onion
USE THE TOR BROWSER. DO NOT ACCESS FROM A CORPORATE NETWORK.
CHANNEL 02
For initial contact, on-the-record interviews and quick tips. Disappearing messages on by default. Our reporters publish their handles individually.
tips.fintechly.01 (intake)
VERIFY SAFETY NUMBERS BEFORE SHARING ANYTHING SENSITIVE.
CHANNEL 03
PGP-encrypted email to the central tips desk. The key is published on this page and rotated annually. Plain email is read but not recommended for sensitive material.
[email protected] · PGP key 0xA7C3 F73A 2026
AVOID SENDING SOURCE DOCUMENTS OVER PLAIN SMTP.
A NOTE ON SAFETY
Do not contact us from a corporate device or network if your employer is the subject of the story. Use a personal device on a personal connection. If you are unsure, get in touch first by Signal — do not send any documents until we have agreed how.
SECTION 03
Every correction we have ever made, in date order, with a severity tag and a plain-English description. If something is wrong on Fintechly today, tell us — and watch for the entry below.
Stripe quietly opens Bridge stablecoin rails to its top 200 platforms
An earlier version of this story stated that integration began in Q1 2026. The Bridge integration in fact began rolling out in late Q4 2025; the headline-200 cohort was added in Q1. The piece has been corrected.
FCA finalises permanent open-banking framework - VRPs go mainstream in Q3
An earlier version misspelled the surname of an attributed FCA spokesperson. Corrected at 11:42 BST on 15 April.
Index Ventures closes $2.3B fund, half earmarked for European fintech infra
An earlier version described the fund as Index Ventures' largest to date. It is the firm's largest dedicated fintech vehicle, but not its largest fund overall. Corrected at 09:18 BST on 2 April.
Spotted a factual error? Email [email protected] with the URL and the specific paragraph. We acknowledge every report.
SECTION 04
The named reporters and editors responsible for what Fintechly publishes. Beats are real and held by one person; we don’t pretend to cover what we cannot.
01 · LONDON
EDITOREDITOR-IN-CHIEF
Editorial direction
02 · NEW YORK
PAYMENTS CORRESPONDENT
Card networks · Stablecoins · Acquirers
03 · LONDON
REGULATION CORRESPONDENT
FCA · ECB · CFPB
04 · BERLIN
CAPITAL MARKETS CORRESPONDENT
Venture · Late-stage · IPO desk
05 · AMSTERDAM
INFRASTRUCTURE CORRESPONDENT
Core banking · Ledgers · Identity
06 · TOKYO
ASIA CORRESPONDENT
Japan · Korea · SEA
07 · DUBAI
MENA CORRESPONDENT
Gulf · North Africa · Türkiye
08 · LONDON
PHOTOGRAPHY DIRECTOR
Cover commissions · Portraiture
SECTION 05
Pitch a story, propose an interview, request a correction, or get in touch about commercial partnerships. Each route goes to a named editor — not a triage queue.
PITCH A STORY
[email protected]
Helena Park, Editor-in-Chief
PROPOSE AN INTERVIEW
[email protected]
The interviews desk
REPORT A CORRECTION
[email protected]
The standards desk
ADVERTISING & EVENTS
[email protected]
Commercial partnerships
CONFIDENTIAL TIPS
[email protected]
Encrypted — see Section 02
GENERAL ENQUIRIES
[email protected]
We try to reply within 48 hrs
THE LEDGER · FINTECHLY’S WEEKLY LETTER · FRIDAYS