About Railflows

Railflows is a managed RFQ workspace for sourcing institutional payment infrastructure. We help companies with complex payment flows find, compare and build redundancy across global payment providers — confidentially, and without the noise of public listings or broker outreach.

Why this exists

Payment rail sourcing is broken. Most teams either reuse the relationships they already have or run an ad-hoc RFP by email — and neither produces a real apples-to-apples view. Provider responses arrive in different formats with inconsistent metrics; sensitive volumes leak before any trust has been established; the "right" provider is often missed because the team didn't know they existed.

We've watched this happen repeatedly across cross-border payouts, marketplace settlement, payroll, treasury FX and stablecoin flows. The structure of the problem is the same every time. So we built the structure.

Why now

The market moved into 2026 with four shifts that, together, make a managed RFQ workspace for payment infrastructure inevitable rather than novel.

• 01MiCA full enforcement reshaped the European stablecoin layer

  Crypto-asset service provider licensing under MiCA became fully enforceable in January 2026. A small number of EU-compliant euro stablecoin issuers now serve a market where ~30 smaller platforms have exited. Buyers need help sourcing the surviving compliant rails — directory listings can't tell them which providers actually have MiCA exposure ready today.

• 02BaaS and PSP partnerships have become single-points-of-failure

  Public BaaS retrenchments and PSP outages in 2024–2025 left fintechs and marketplaces structurally exposed to provider concentration. Treasury teams now plan for redundancy as a default. That requires sourcing multiple providers in parallel — which is exactly what an unstructured RFP by email is bad at.

• 03Treasury teams want benchmarks, not anecdotes

  Public statements from FX brokers and treasury platforms confirm what every operator already knew: spreads are opaque, settlement assumptions vary, and 'we got a good rate' is no longer good enough for procurement. Structured comparison data is now a procurement requirement, not a nice-to-have.

• 04Banks are retreating from commodity trade finance

  Western banks have been actively debanking commodity traders with indirect Iran exposure. A 2T USD market is shifting to non-bank lenders who themselves need a regulated, structured way to settle. That is exactly the audience an RFQ workspace can serve — and the audience that an ad-hoc directory cannot.

Each on its own would be a soft tailwind. Together, they make structured sourcing the path of least resistance for institutional buyers rather than a forced choice between the relationships they happen to have and the RFPs nobody enjoys running.

Operating principles

Four commitments shape every product decision and every commercial decision:

• Confidential until consented

  Providers see anonymised summaries by default. Buyer identity, documents and contact details are disclosed only after the buyer explicitly approves a reveal — per provider, per document, audit-logged. There is no server-side fallback to 'show everything' in any code path.

• Fit over paid placement

  Placement on a buyer's comparison is a function of structural fit and response quality. Ranking is not for sale. It will not be for sale. We will not run tier-up-for-visibility schemes.

• Structured data over sales theatre

  Free-text gets sanitised. Pricing gets normalised. Risk gets categorised. The comparison output is a directional benchmark with twelve dimensions and explicit weights — not a popularity contest, not a pitch deck.

• Directional intelligence, not provider endorsement

  Railflows scores fit; the buyer runs the due diligence. We do not perform KYB/KYC on providers' behalf and we do not imply regulatory endorsement of any licence. The output of the platform is a warm, consent-based introduction. The commercial relationship is yours.

Who's behind it

Railflows is built by a small, focused team out of Stockholm with operator and product backgrounds in the payments and consumer-trust space. The platform is a separate venture from any prior work — focused specifically on the institutional payment infrastructure problem — but the obsession with making opaque markets legible carries over.

If you're an institutional buyer or a regulated payment provider who wants to be part of how this gets built, we'd love to hear from you.

What we're not

Railflows is not a payment provider. We do not hold, transmit, settle or process funds. We do not perform KYB or KYC for any party. All payment services are delivered directly by the licensed or otherwise authorised providers buyers engage with through the platform.

We're also not a public PSP directory, a broker, or an outbound sales channel for providers. We're a sourcing workspace. The output is a structured comparison and a warm, consent-based introduction — the commercial relationship is yours.