Build on FinP2P: a field guide.

How to connect an app, a ledger, a custody service or a data feed to Ownera's FinP2P network, written by people who have done it, with every step linked into Ownera's own documentation.

Pick your path

Ownera's docs split builders into two kinds, plus the institutions that run the network and the people who only need to read it. Find yourself below.

The model in seven terms

Router

The FinP2P node each institution runs. Routers talk to each other peer to peer; there is no shared ledger in the middle. ISVs usually connect to their clients' Routers rather than running one. Router fundamentals ↗

SuperApp

Any application or service connected to a Router. Ownera's store lists 35 of them today. Integration paths ↗

Profile

A global identity for an owner (investor) or an asset. Owner identities are secp256k1 keys. Profiles are shared explicitly with other organisations.

Intent

A declarative statement of what should happen: a primary sale, a buying or selling intent, a loan, a transfer, a redemption. It says what, never how on any particular chain. Intent-based orchestration ↗

Orchestration plan

The step-by-step workflow the Router generates from an intent and proposes to the other participants' Routers, who approve and execute it together. You submit intents and watch plans; you rarely write plans.

Adapter

The bridge between a Router and a ledger, custody provider or data source. Adapters are where chain-specific code lives.

Certificate

A signed attribute attached to a profile: KYC, AML, accreditation, company info, NAV. Schemas are public in finp2p-certificates-spec.

Resource IDs look like organization:resource-type:uuid, so an ID tells you which organisation's Router owns it.

How a call flows

1. Something happens in your app: an investor clicks buy, a desk books a repo, a rebalancer fires.
2. Your integration creates an intent and submits it to your local Router over REST.
3. The Router builds an orchestration plan and proposes it to every participating Router.
4. The Routers execute it peer to peer, step by step, with full consensus; adapters move the asset and the cash on whatever ledgers they live on.
5. Results and proofs come back. Most calls are asynchronous: you get a correlation id (cid) and poll the operation, or read the plan over GraphQL.

The How it works page draws this end to end with a repo trade.

Authentication

Every request to a Router carries a fresh, single-use JWT signed RS256 with your own private key. Onboarding: generate an RSA key pair, send Ownera the public key, receive an API key and your organisation ID, then sign a new token for every call (it expires 30 seconds after issue, and the nonce cannot be reused).

openssl genrsa -out prv.key 4096
openssl rsa -in prv.key -RSAPublicKey_out -out pub.key   # send pub.key to Ownera

// JWT payload, one per request, signed RS256
{
  "aud": "<ORGANIZATION_ID>",
  "apiKey": "<API_KEY>",
  "nonce": "<24 random bytes + 8-byte epoch, hex>",
  "iat": 1760380800,
  "exp": 1760380830
}

Heads-up: the Hello World sample puts the API key in an apiKey claim. The Authorization reference calls it sub in its prose but uses apiKey in its own code sample. In our own testing with Ownera's engineers (Sep 2026) the auth service read apiKey; setting both sub and apiKey to the API key works. The same reference sets a 5-second default clock-skew tolerance for the nonce, so keep server clocks in sync.

Hello world, in order

Ownera's sandbox comes with a simulated custody service, a simulated payment service and at least one test asset shared with you. The Hello World sample walks through it with full request and response bodies:

There is also a dry-run endpoint that predicts the plan for an intent without executing it. Use it while you build.

Adapters: plugging in a ledger, custody or data

If other apps will consume what you build, you implement one of these APIs and the Router calls you. The official skeletons are the fastest start.

Chains already reached by adapters, per public sources: Ethereum and all EVM L1/L2, Hyperledger Besu, Canton, Corda, Hedera, XRP Ledger, Tezos, Stellar, Kadena, Solana, Polygon, 150+ chains via LayerZero. Full list with sources on the network page.

Getting listed on the SuperApps store

Ownera publishes the process at superapps.ownera.io/onboarding-howto. In short:

1. Sign up to the SuperApp Portal.
2. Create your company profile: legal entity, registration, jurisdiction.
3. Submit a draft SuperApp: name, description, use case, asset classes, optional demo.
4. Review and agreements: Ownera due diligence (KYC), then NDA, Platform Terms, Partnership and Commercial agreements. You are listed in development status.
5. Connect to the sandbox Router and validate connectivity.
6. Go to production once testing and agreements are done.

Ownera publishes no fees for listing. Once you are listed, tell us and you will show up on this site's map with the next data refresh.

Open code and public endpoints

Recent changes in Ownera's open code (checked 6 Nov 2026): the EVM adapter v0.29.0 shipped on 12 Oct; the Node.js skeleton now maps swap and move execution-plan instructions and keeps the Router's EIP-712 type definitions on signing templates (20 to 22 Oct); the certificates spec added collateral-terms v3, with the haircut method set on the agreement (18 to 20 Oct); and the Tezos adapter was archived on 1 Nov.

Shipped something, or found a mistake here?

If you built on FinP2P, tell us: we will add it to the map, and if you are a founder, Draper Goren Blockchain may want to back it. If this guide has drifted from the official docs, email alon@dgb.vc and we will fix it the same week.