Participation

The Spike Network operates through coordinated interaction between participating institutions and connected infrastructure.

Each participant performs a defined role within the network, while execution, custody, and compliance remain within their respective environments.

Participants include:

  1. 01

    Platforms

    Platforms provide the user interface and define how the network is used. They initiate instructions, configure supported institutions and flows, and manage the user relationship.

  2. 02

    Banks and EMIs

    Banks and EMIs hold fiat accounts and execute payments and transfers. They retain responsibility for custody, execution, and regulatory compliance within their own systems.

  3. 03

    Exchanges and Trading Venues

    Exchanges execute conversions and digital asset transfers. They provide trading and conversion infrastructure while maintaining custody and execution responsibility.

  4. 04

    Spike Network

    Spike operates as an orchestration layer. It captures and routes instructions, coordinates interactions between participants, and maintains lifecycle state across workflows.

    Spike does not execute transactions, hold funds or digital assets, or provide liquidity.

Network

The Spike Network is a neutral orchestration layer connecting regulated financial institutions, exchanges, infrastructure providers, and DLT networks.

It provides a technology-enabled environment for the transmission, routing, and coordination of instructions between network participants across traditional financial systems and distributed ledger-based systems.

The network enables participants to coordinate value movement through standardised interfaces and defined operational processes across connected institutions.

Spike does not hold funds or digital assets, execute transactions, or provide liquidity. Execution remains with regulated participants.

  1. 01

    Coordinated Liquidity

    Structured coordination of value movement across institutions and defined corridors, without requiring direct bilateral integration.

  2. 02

    Instruction-Based Coordination

    All activity is driven by non-executable instructions representing end-user intent, enabling routing and coordination without execution by Spike.

  3. 03

    Unified Integration

    Access to banking, exchange, and digital asset infrastructure through a single integration model, reducing the need for bespoke connections.

  4. 04

    Operational Control

    Participants retain full control over accounts, execution, custody, and compliance within their own environments.

Documentation

The Spike Network documentation defines the architecture, frameworks, and operational models that govern participation in the network.

It provides detailed coverage of how instructions are processed, how value moves across institutions, and how participants integrate and operate within defined frameworks.

  1. 01

    System Overview

    Structure of the Spike Network, including core layers, execution environments, and instruction-based coordination across institutions.

  2. 02

    Network Frameworks

    User Access Layer, On/Off-Ramp Infrastructure, and Corridor Orchestration frameworks defining how value is initiated, routed, and coordinated.

  3. 03

    Participation Model

    Roles, responsibilities, and interaction models for platforms, institutions, and infrastructure providers within the network.

  4. 04

    Integration & Deployment

    API integration, configuration of institutions and flows, and deployment of orchestrated workflows across connected systems.

  5. 05

    Governance & Compliance

    Responsibility allocation, regulatory boundaries, and operational principles ensuring execution, custody, and compliance remain with regulated participants.

Access

Access to the Spike Network is available to institutions seeking to integrate and operate within the network.

Engagement is structured around defined use cases, participating institutions, and supported workflows.

  1. 01

    Define Use Case

    Identify the intended use case, including on/off-ramp flows, corridor-based transfers, treasury operations, or liquidity coordination.

  2. 02

    Select Institutions

    Define participating banks, EMIs, exchanges, and infrastructure providers involved in execution and routing.

  3. 03

    Configure Flows

    Specify supported assets, currencies, routing paths, and corridor structures in accordance with network frameworks.

  4. 04

    Integrate and Deploy

    Integrate via API or enable access through supported interfaces, then deploy and operate network-defined workflows.

Participation is subject to review and alignment with the network’s operational and participation frameworks.