GRA · Fintech Nexus
Spatial financeWhere capital meets hazard, exposure and transition
Research and industry programmes
Fintech Consortium programmes follow where digital finance is governed: global standards for payments, crypto-assets and third-party risk, regional regimes for open banking, digital assets and operational resilience, and national payment systems, identity schemes and licensing. The Global Risks Alliance (GRA) holds no role in any of them.
The workspace for research and industry programmes.
Programme portfolio
Fintech · Research and industry · Example interface, not a record
Where the work sits
example geography
Portfolio
| Fintech F1 | Regtech reporting pilot | Scoping | On track |
| Token platform | AI credit scoring audit | Scoping | Blocked |
| Digital wallet | Open finance consent flows | Test | On track |
| Agent network | Operational resilience | Test | Blocked |
Decisions waiting on owners
- D-1Regtech reporting pilotChief compliance officer · decision record5 d
- D-2AI credit scoring auditChief compliance officer · decision record11 d
- D-3Open finance consent flowsBank partner · decision record11 d
Fintech Nexus · Programme portfolio. Programme portfolio: example names and illustrative values, not a record.
Three levels of work.
What each level examines.
| Level | Questions | Evidence owners |
|---|---|---|
| Global | Crypto-asset and stablecoin standards, payment transparency, third-party risk, post-quantum migration | FSB, BCBS, CPMI, FATF, standards bodies |
| Regional | Operational resilience and digital-asset regimes such as DORA and MiCA, fast payment and open banking schemes | Regional regulators and payment authorities |
| National | Payment system structure, mobile money and agent networks, identity systems, licensing perimeter | Central banks, supervisors, identity authorities |
How the process runs.
Process explorer · Process
Research and industry programmes: Programme through eight gates
11 steps·4 stages·8 gates
Process
Research and industry programmes: Programme through eight gates
The Global Risks Forum (GRF) records eight yearly gates, each a programme decision; a gate not passed stops its work, and the competent authority decides outside.
01 Q1 · Planning
- 01G0 · Annual programme authorisedGate · The Global Risks ForumGRF authorises the annual mandate. It never sets a national agenda.
- 03Route the candidate mission to standardsStep · Nexus StandardsNexus Standards routes each candidate mission to the standards and profiles that apply.
02 Q2 · Readiness and build
- 04G1 · Missions admittedGate · The Global Risks ForumGRF admits missions with reasons recorded. It cannot admit a mission without an accountable owner.
- 05G2 · Data and resources qualifiedGate · The Global Risks ForumReadiness preparation closes when data, people and resources are qualified.
- 06G3 · Build accepted for exerciseGate · The Global Risks ForumGRF records whether the build is accepted for exercise. A gate not passed stops the work it governs.
03 Q3 · Action Week
- 07G4 · Controlled live operation authorisedGate · The Global Risks ForumGRF authorises controlled live operation for Action Week.
- 08G5 · Evidence sealed and stand-down recordedGate · The Global Risks ForumThe evidence is sealed with its provenance and the stand-down is recorded.
04 Q4 · Reporting and renewal
- 02Competent authority decides and actsActor · The competent authorityThe competent authority decides and acts under its own rules. The programme informs it and never decides for it.
- 09Scientific and editorial reviewStep · Reviewers and the publisherQualified, conflict-managed reviewers and the publisher decide what is accepted. Institutions cannot decide a scientific conclusion.
- 10G6 · Publication authorisedGate · The Global Risks ForumGRF authorises publication of results that have passed scientific and editorial review. It cannot publish personal data.
- 11G7 · Renewal reviewedGate · The Global Risks ForumGRF reviews renewal and sets the next cycle's mandate.
The programme year · The Global Risks Forum · Decision rightsDesigned programme process, not a record of operation. No cycle has run and every programme is at service level R0. A gate is a programme decision, never a public-authority approval, certification or deployment authorisation.
With an owner's question.
Programme work starts when a central bank, supervisor or national consortium brings a question it owns, such as how a cloud-region outage would affect its instant payment system. Fintech Nexus frames evidence; the project owner decides. See country readiness contexts and regional exposures.
Every programme shows where it stands.
A programme is shown as exploring, forming, constituted, active, paused or archived, according to its record. A plan is never presented as an activity.
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.
- CPMI-IOSCO Principles for Financial Market Infrastructures (2012) and cyber resilience guidance (2016)
- FATF Recommendations, including revised Recommendation 16 on payment transparency (June 2025; implementation by end-2030)
- EU Digital Operational Resilience Act, Regulation 2022/2554 (applies from 17 January 2025)
Pages in Research and industry programmes.
Questions and answers.
How does a country take part?
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.