A FinP2P Router can be used to build financial applications — often referred to as SuperApps — that are agnostic to the underlying ledger technology. Whether assets are managed on Ethereum, Corda, Canton, or any other DLT, applications built on the router work seamlessly across the FinP2P network.

Available APIs at a Glance

The transactional APIs

Use this to write data into the FinP2P ecosystem. It enables operations like creating Owners and Assets, uploading documents, sharing access, and performing trade orchestrations.

The Query API

A friendly GraphQL interface for reading data across the FinP2P network—whether it’s local DLT data or shared data from external routers.

Together, these APIs abstract the complexity of application and blockchain integrations, letting developers focus on building applications while the router manages interoperability across ledgers and institutions.

Extending with Adapters: Plug into Issuers, Payments, and Custody Services

Ledger Adapter

Ledger Adapter API introduction

Integrates your application with Issuers or Payment Hubs using the FinP2P network.

The Ledger Adapter API forms the contract between the FinP2P router and the external ledger or payment system. You implement this to connect tokenization platforms or payment services. Typical API groups you’d implement:

Asset Management (e.g., create asset, issue, redeem)
Transactions (e.g., transfer, balance, receipts)
Escrow (hold, release, rollback) and other operations
Payments (deposit instructions, payouts, orchestrations plans)

Custody Adapter

Custody Adapter API introduction

Used when integrating Custody Providers into the FinP2P network.

This adapter allows financial institutions to manage signing and approval workflows via their own key management platforms. You’ll implement:

Account Management (create accounts tied to FinID Signing Keys)
Signature Workflows (signing requests, approval of orchestration plans)
Orchestration Plan Notifications (approve, reject, status updates)

Operational API — Advanced Operational Controls

Operational API

The Operational API enables backend operational control and resilience for SuperApps, enabling functions such as ledger reconciliation, execution plan management, workflow control, and trading policy enforcement.

How the Pieces Work Together

SuperApps typically use the Transactional API and Query API to interact with the FinP2P network. In addition, depending on the use case, they may also need to implement one or more adapter interfaces to integrate with external systems (issuers, payments, custody).

Transactional & Query APIs → Provide the standard interface to express intents (e.g., issue, transfer, redeem, deposit, withdraw) and to query network data.
Ledger Adapter → Required if your SuperApp needs to connect an Issuer Hub or Payment Hub to an external ledger or payment system.
Custody Adapter → Required if your SuperApp provides custody services and must integrate with key management/signing systems.

Please follow the API references for more information.