Section 08

The evidence

32 research documents, 271 findings, 1489 data points and 668 sources. The complete set is downloadable — including both review passes and everything that supports or contradicts either interpretation in section 07.

The analysis pack

All 32 research documents in full, the synthesis, the open-gaps register, both independent review passes with a point-by-point comparison, and the extracted claim graph as machine-readable JSON. Anyone wanting to work with this, check it, or dispute part of it should start here rather than with the pages above.

Download the analysis pack (.zip)

How solid is this?

The honest way to judge a piece of analysis is not to read its conclusions but to count what they rest on. Every number in this work carries a label recording how it is known, and those labels are counted below rather than asserted.

The distinction that matters most is between a figure somebody published and a figure somebody estimated. Both look identical in a slide. Only one survives being checked.

Basis of the underlying dataCountShare
Sourced to a named party99967.1%
— of which primary documents21514.4%
Measured directly231.5%
Inferred, with the derivation shown19212.9%
Analyst, vendor or survey533.6%
Estimated — judgement, no source241.6%
No basis, or not published19813.3%

2% of the data behind these conclusions is judgement with no source behind it. That is the number to hold this work to, and it is the reason the labelling exists at all — an unlabelled body of research cannot tell you this about itself.

Two caveats on the count. It is generated automatically from the research documents, so a figure mislabelled inside a document is counted as labelled here. And a label is a claim about provenance, not about correctness: a number can be perfectly sourced to a party who was wrong.

Evidence outside the original claim graph

The counts above describe the structured research briefs. The comparison in section 07 also uses current external evidence and Atlas product material that are not encoded as brief findings, so they are listed separately rather than silently added to the denominator.

EvidenceSourceWhat is establishedWhat is not
Stablecoin-network orchestrationCircle Payments NetworkParticipant vetting, compliance rules, service levels and fiat payout are sold as an assembled networkCustomer volume, realised pricing and Atlas’s ability to differentiate above it
Programmable bank moneyCiti Token Services; KinexysInstitutional bank deposits already provide continuous and programmable settlement functionsReach into Atlas’s target customers and corridors
Trade invoicing currencyEurostat metadataPublished invoicing-currency statistics aggregate partner countries into regionsThe invoice currency and routable payment volume of any named bilateral corridor
Software-provider obligationsDigital Operational Resilience ActRegulated customers must contract for ICT resilience, audit, incidents and exitAtlas’s exact classification, contract burden and sales-cycle effect
Trade-platform precedentTradeLens; Contour; KomgoBoth failed network scale and live embedded multi-bank workflow exist in the categoryAtlas-specific willingness to pay
Atlas banking-platform capabilityPlatform code and internal documentationRelevant transfer, beneficiary, approval, provider, compliance and reconciliation concepts existIndependent production status, implementation gap and paid buyer demand

How to read a research document

Every one follows the same structure. The question states what the document was commissioned to answer and what decision it informs. The bottom line is a short list of conclusions, each written to be argued with rather than agreed with. The key numbers table carries every figure with its basis, its confidence and the date it was true. Then the findings themselves, the variance and tail risk, what is still open, and finally an explicit statement of what would change the author's mind.

That last section is the most useful part of any of them. If you want to know whether a conclusion here is fragile, read what its author said would overturn it.

The documents

A Thesis

DocumentFindingsData pointsExternal sourcesConfidence
Is the revised position defensible, and for how long?10 24— medium-high qualified
Who actually buys this, and why would they pay?7 3424 medium
Is the thesis strictly cross-border? Where the scope boundary actually sits8 27— medium-high qualified
iGaming as a core vertical — what operators need from a payments partner, what they pay, and what serving them costs us8 4228 medium-high qualified
High-risk verticals beyond gambling — FX/CFD brokers, nutraceuticals & peptides, adult/creator platforms7 3413 medium-high qualified

B Competition

DocumentFindingsData pointsExternal sourcesConfidence
Direct consumer/SMB-facing comparables — Augustus, Wise, Revolut10 6862 high
Cross-border infrastructure incumbents — own vs broker, economics, and whether "orchestration" is already their product7 3248 medium
Stablecoin-native payment infrastructure — competitors and counterparties7 5240 medium-high
Does the rail layer absorb orchestration from below?8 6631 medium-high
The card-orchestration precedent — how the last orchestration wave ended7 3440 high qualified
The acquisition record — what buyers in cross-border payments actually pay for7 4418 medium

C Rail economics

DocumentFindingsData pointsExternal sourcesConfidence
Fiat correspondent banking / SWIFT leg — the incumbent baseline8 8826 medium-high
Instant & domestic scheme rails — operating economics and behaviour7 3735 medium-high
The FX leg — how spreads are formed, what they cost, and whether the FX book is the business7 4024 medium
Stablecoin leg — real all-in economics of on-ramp, chain hop, off-ramp8 013 medium-high
Push-to-card payout rails — where they genuinely win, and whether we route over them8 8321 medium-high
EM local collection & payout rails — cost, timing, prefunding, licensing9 6516 medium
KYT, Travel Rule, sanctions screening and compliance holds — what they cost in money and in latency, per leg10 7823 high qualified

D Regulatory

DocumentFindingsData pointsExternal sourcesConfidence
EU licence perimeter — what authorisation does an orchestration layer actually need?9 4827 high qualified
MiCA in practice — what a stablecoin-touching orchestration layer actually has to hold12 5616 high qualified
Digital euro & the e-money question — how do we remain relevant in the EU?6 4225 medium-high
Corridor licensing — what it takes to be principal on the conversion in the corridors that matter10 5022 high qualified

E Build-vs-partner

DocumentFindingsData pointsExternal sourcesConfidence
Counterparty tier map — who sells unbundled single-leg wholesale, and at what tier7 2913 medium
Vertical integration scoring — per rail and per leg, own / partner / broker10 47— medium
The value-add test — where does this business beat a sophisticated buyer going direct?9 21— medium-high
Treasury as a product — what a cross-border treasury function buys, from whom, at what price7 5722 medium
The Swedish listed vehicle — reverse listing, take-private, or paper as acquisition currency?10 11026 high qualified

F Corridors

DocumentFindingsData pointsExternal sourcesConfidence
Corridor economics — does the routing decision move all-in cost by >30 bps, repeatably?6 392 medium-high qualified
South Africa (ZAR) and the CEE / Nordic cross-currency pocket — do either beat Mexico?8 5210 medium
The Gulf and China — two corridors the programme never analysed10 913 high qualified
Underserved corridors as acquisition bait — where supply scarcity, flow and named acquirer intent actually overlap14 8123 medium-high qualified

G Gap closure

DocumentFindingsData pointsExternal sourcesConfidence
Validating the comparison panel against published provider coverage10 07 high qualified

A dash in the source column marks an analysis document — one that reasons over the other documents rather than gathering external sources of its own. “Qualified” means the author gave different confidence to different parts of the conclusion; the full wording is in the document.