Methodology

Data Methodology

How Plexo Institute collects registry data, defines tracked coverage, refreshes sources, and explains known data limitations.

What this page covers

This page explains how Plexo Institute tracks public registry data for stablecoin, payments, and digital-asset market intelligence. It describes the source basis, review posture, coverage language, and known limits behind public data pages.

How data is collected

Plexo Institute uses direct parsing of official government registries, regulator publications, legal notices, and other primary public records where available.

Registry facts are normalized into public data surfaces so readers can inspect entities, jurisdictions, licenses, signals, and source context in a consistent way. Editorial analysis is kept separate from raw registry status, source notes, and limitations.

Update cadence

Registry sources do not all change on the same schedule. Plexo refreshes tracked records through explicit pulls, parser runs, editorial review, and correction handling when sources change or when a page needs renewed confidence.

A page-level review label describes Plexo activity on that page. It does not guarantee that every authority has updated its own registry, that every jurisdiction publishes at the same speed, or that a public record has no pending amendment.

What tracked means

Tracked means the record is included in Plexo tracked-by-Plexo coverage and has a maintained public data path.

Tracked does not mean all licensed entities in a jurisdiction are present.

Tracked does not mean an entity is endorsed, active, compliant, onboarded, investable, or eligible for any product relationship.

Tracked coverage can expand, narrow, merge, or change when source records are clarified or superseded.

Known limitations and gaps

Official registries can be delayed, incomplete, archived, renamed, or split across more than one authority.

Licensing language, entity names, product scopes, and status labels can differ across jurisdictions and source formats.

Transliteration, merger history, aliases, and legacy names can make entity matching uncertain until a source clarifies the record.

A visible page may prioritize source-backed public context over operational detail that belongs in private diligence or written agreements.

How to read Plexo data

Plexo Institute data is informational research infrastructure. It is not legal, regulatory, financial, investment, tax, compliance, sanctions, KYB, AML, risk, pricing, liquidity, corridor, or settlement advice.

Readers should verify important decisions against primary sources, qualified advisers, written agreements, and their own diligence process. Correction requests are reviewed against source quality and public evidence.

Crawler and policy references

For machine-readable discovery posture, see /llms.txt. For broader source hierarchy, corrections, limitations, and public methodology boundaries, see the Data & Methodology Policy.

For journalists and researchers

A source map for distinguishing Plexo analysis from facts that can be checked at the originating institution.

Use the relevant Plexo original for its analytical thesis. For a factual statement, retain its date and follow the linked primary source. A Plexo taxonomy, analogy, or policy proposal is not a regulator classification, market fact, forecast, or endorsement by the institutions cited below.

Each topic below gives a bounded formulation, the method or limitation that matters, and a direct route to the underlying evidence.

Plexo source: State of VASP Licensing — 2026 Annual.

Safe formulation: On 15 June 2026, Plexo Institute recorded 13,238 tracked regulated-entity records across 207 jurisdictions. This is a dated broad registry measure, not a worldwide total of VASPs or unique companies.

Method and limit: Plexo takes dated snapshots from public registry data. The annual edition covers an 11-day baseline window, so it supports the snapshot but not an annual-growth claim. For a country-level claim, use the VASP/CASP registry by jurisdiction and its regulator path.

Plexo source: The Prefunding Trap.

Safe formulation: Cross-border payments commonly rely on balances positioned in advance in correspondent arrangements. Public sources establish the mechanism and its liquidity, credit, and reconciliation trade-offs, but do not publish a reproducible global stock of operational prefunding.

Primary evidence and limit: BIS explains cross-border liquidity management through prefunding; CPMI provides correspondent-banking activity data; the World Bank covers cross-border fast-payment design. Do not turn the article into a global prefunding stock, annual cost, release-rate, or “hidden tax” estimate.

Plexo source: The Neutral Clearing Playbook.

Plexo analysis: neutral clearing is a governance test for a proposed clearing layer: decision rights, membership, compliance, regulation, and commercial incentives should be inspectable rather than privately determined by one participant.

Primary evidence: CLS describes payment-versus-payment settlement and multilateral netting; Swift describes its member-owned governance; the Federal Reserve describes ACH’s national operators; BIS Project Agorá describes a prototype, not a finished product. None endorses Plexo or a particular network.

Plexo source: The Two-Stage Framework.

Plexo analysis: start with a bounded supervised payment use case, then consider broader activity only after supervisory, redemption, custody, and reporting controls are demonstrably working.

Evidence and limit: MiCA, MAS, the GENIUS Act record, and the Bank of England show differentiated risk frameworks. They do not establish a universal two-stage regulatory sequence. Treat this framework as a research-held proposal, not a citation for jurisdictional convergence or legal permission.

Plexo source: Four Archetypes of Stablecoin Regulation.

Plexo analysis: proactive, permissive, restrictive, and reactive are a decision taxonomy for comparing practical regulatory posture. They are not official legal classes.

Primary evidence: MiCA, the GENIUS Act record, Bank of England policy material, and FATF guidance demonstrate different risk and supervisory approaches. They do not assign a country to a Plexo archetype or predict a licence outcome.

Plexo source: Six Pathways.

Plexo analysis: the six pathways are a comparison tool for cross-border settlement architectures. An operator should evaluate a route by corridor, counterparty, regulatory perimeter, liquidity, and operational controls — not transaction speed alone.

Primary evidence: BIS Bulletin 87 describes pressure in correspondent banking; CLS documents multilateral settlement; BIS Project Nexus covers instant-payment interlinking; BIS Project Agorá is a tokenised institutional prototype. These sources do not prove market shares, one inevitable path, or a live public-stablecoin network.

Plexo source: The Pre-SWIFT Moment.

Plexo analysis: regulated stablecoin payments still need an institutional coordination layer for counterparty discovery, policy matching, data exchange, liquidity coordination, and evidence of completion. “Pre-SWIFT Moment” is an analogy, not a forecast that stablecoins replace Swift.

Primary evidence: FATF’s 2025 update records 99 jurisdictions that had passed or were progressing Travel Rule legislation; FSB recommendations address data interoperability; Swift’s July 2026 announcement concerns initial tokenised-deposit pilots; the World Bank reports its Q3 2025 remittance-cost measure. Those facts do not validate a Plexo architecture or predict a replacement of existing rails.

See also llms.txt and the Data & Methodology Policy.