Overview

High-level flow

BlockPeer Trade APIs
        ↓
IntegratingSystem
        ↓
EndUser (Authorized Signer)

• The Integrating System calls BlockPeer APIs
• The End User approves actions via redirect and passkeys
• BlockPeer orchestrates TradeTrust workflows without custody

Two distinct steps: Authentication & Approval

BlockPeer intentionally separates:

Authentication

• Confirms the identity of an End User
• Issues a session token
• Allows the Integrating System to initiate workflows

Approval

• Required for every eBL / ETR issuance or management action
• Performed only by the End User
• Happens only via redirect URL
• Uses End User passkeys

Authentication does not imply approval.

Non-custodial by design

• BlockPeer does not hold or access private keys
• BlockPeer cannot approve or sign actions
• End Users retain full control and responsibility

This design aligns with:

• TradeTrust framework principles
• UNCITRAL MLETR requirements
• Bank and regulator custody expectations

Where approvals always happen

All approvals happen outside the Integrating System UI, via a secure redirect flow hosted by BlockPeer.

This ensures:

• Explicit end user consent
• Clear audit trail
• No hidden or programmatic signing