GRA · Fintech Nexus
Spatial financeWhere capital meets hazard, exposure and transition
Published scenarios
Fintech scenarios test what happens when the infrastructure under a digital service fails, when an attack spreads through shared providers or when a run on a stablecoin or an e-money issuer starts. This page sets out the scenario families and the design choices that make them useful. Values shown are design values, never forecasts or measurements of any service.
The order things happen in.
- 01QuestionNational, regional or institutional priority
- 02EvidenceSTEM foundation of the platform
- 03BuildFoundry
- 04OrganiseNexus ecosystem
- 05TestUniverse (independent site)
- 06PublishReports
- 07DecideCompetent authorities and institutions, through NXS-RLS (participants, agreements and handoffs)
- 08RenewCorrections and the next annual agenda
Releases appear as they are reviewed.
Analysis runs in Foundry; reviewed releases are listed here.
Severe but plausible scenarios for fintech services.
| Scenario | What it stresses |
|---|---|
| Loss of a cloud region | Hosting concentration and failover across regions |
| Compromise of a widely used software library | Supply-chain security and patch speed across clients |
| Stablecoin run | Redemption capacity and reserve liquidity under MiCA-style rules |
| Card or instant payment scheme outage | Fallback channels and customer communication |
| Regional disaster cutting power and connectivity | Branchless access to cash and payments for affected households |
How the process runs.
Process explorer · Process
Published scenarios: Public service over DPI
7 steps·4 stages·1 gate
Process
Published scenarios: Public service over DPI
An illustrative service request; the Universal DPI Safeguards Framework 2.0 has 18 principles and five life cycle stages but prescribes no sequence.
01 Person
- 01IdentityDatasetThe person proves who they are to the service. The framework asks that people have a choice of digital and non-digital channels.
- 02ConsentGateThe person decides on sharing their data for a stated purpose. The framework asks that everyone can control their data and choose.
02 Agency
- 03Data exchangeModelThe agency obtains only the data it needs through agreed interfaces. The framework names data minimisation as a privacy-by-design principle.
- 04EligibilityStep · Consumer protection leadThe agency applies its eligibility rules. Whether a person reviews the result is for the agency to set.
03 Rails
- 05PaymentStepWhere the service pays out, it uses a payment rail, for example an instant-payment system. The framework does not name payment systems.
04 Accountability
- 06Grievance redressStep · Consumer protection leadThe framework asks for complaint, redress and appeal routes without reprisal, accessible to all during service delivery.
- 07Independent assessment and auditDecision · Consumer protection leadThe framework asks for independent, transparent and continuous assessments or audits that review evidence and act on heightened risks.
Neutral outline of a published external standard or method, from its issuing body. Not a record of operation. Nexus does not perform, certify or approve any step shown. A gate or decision belongs to the party the source names. The sequence is a sketch, not a prescribed process. Each step is tied to the principle that bears on it, where one exists.
Settlement dependencies, and what fails with a node.
Scenarios are run on a dependency network of services, providers and data centres. Removing one node shows which services lose availability and where their users are. Links in the Global Risks Alliance (GRA) figures are design links, not real dependencies. Methods at GCRI network science; governance at the Global Risks Forum (GRF) cyber and public infrastructure.
Where this page's references lead.
The bodies and documents this page is read against. Status and editions change; each link goes to the issuing body.
Questions and answers.
Can I request a map or model?
Contribute evidence from this page.
Reports is the Consortium's quarterly publication. What you know about this subject can become evidence, a case or a correction in the next edition, credited to you and published under CC BY 4.0 where it is your own work.
- EmailGateway GW-GRASend it from this pageEvidence, a correction, a case, a method, a review, a translation or profile input. It arrives tagged with this page, so the editor who owns it receives it.
- ZenodoOpen depositDeposit it and submit to the communityPublish your own record on Zenodo with your ORCID iD, then submit it to the Reports community there. Curators review it; the DOI stays yours.
- ReportsGlobal Risks AllianceSee every way to contributeThe contribution types, how each is reviewed, what credit you receive, the licence and what is never accepted.
Never send personal data, sensitive infrastructure detail or anything you have no right to share. A contribution is reviewed before use; sending it confers no authorship or editorial rights, and sponsorship never buys a finding.
Bring an exposure or capital question to the Alliance.
Information and enquiries are open today. An enquiry receives a reference and names the next step; applications, payments, compute allocations and registrations open only when their team, terms and review capacity exist.
Legal documents.
Maps, data and figures on this site are shown for context and general information. They are not advice, forecasts or warnings; the limits of the information are set out in the Disclaimers and Data Notices.