Open Payments + ILP Animated Collaboration

Analysis: Architecture Flow

Discovery & Resolution

Client queries the Wallet Address Server using a Payment Pointer (e.g., $wallet.com/alice) to resolve endpoints for Authorization and Resources.

Auth Server & IdP Consent

Client requests a GNAP grant from the Authorization Server, which seamlessly delegates to the Identity Provider (IdP) for cryptographic user consent validation.

Resource Server Access

Armed with an access token, the Client calls the Resource Server (the ASE's API gateway). This component initiates incoming or outgoing payments and bridges to the ILP node.

ILP Accounting Ledger

As ILP packets route through the Resource Server, the internal Accounting Service Entity continuously increments or decrements the peer's Accounts Payable/Receivable balances.

Automated Settlement

The Settlement Engine monitors the Accounting thresholds. Upon breach, it executes a deterministic, irrevocable value transfer on the underlying Core Ledger.

Hover over any architectural phase to isolate the data flow and active components.

Request Origination

Open Payments API / ASE

ILP Backend Engine

Client Application

Transaction Initiator

Wallet Address Server

Metadata & Endpoint Resolution

Authorization Server

GNAP Token Issuance

Identity Provider (IdP)

Cryptographic User Consent

Resource Server (ASE Gateway)

Payment Execution & ILP Node

Accounting Service Entity

High-Speed AP/AR Ledger

Settlement Engine

Threshold Clearing execution

Core Ledger Layer

e.g. Programmable Stablecoins