Introduction
Connect to a real ledger and run payment flows against live infrastructure — wallets, intents, anchors, and real-time settlement.
This section takes you from exploring basic calls to actual real money movements.
In Getting Started, you worked with a mock server to learn the API shape. Here, you connect to a real ledger and run the same flows against live infrastructure — creating wallets, sending payments, and collecting money across institutions and networks.
Every payment is cryptographically signed by the initiating party, so there is no ambiguity about who authorized a transfer or what it was for. Wallets and anchors are scoped to domains, which means your configuration is portable across ledger environments and payment networks without collision.
Payment intents carry structured claims — schema-validated fields that encode business intent directly into the transaction, eliminating the reconciliation gap between what was sent and what was meant.
The same intent structure works whether the payment routes through an ACH, a card rail, a real-time rail, or a cross-border corridor.
Connect
Onboard
Send Money
How to Send a Payment to an Account
Push funds to a bank account with a single intent — no per-rail integration required.
How to Send a Payment to an Anchor
Resolve a phone number or alias to a wallet address, then create the payment in one flow.
Collect Money
How to Collect with a Static QR
Create a permanent QR code for a store counter that routes payments to the right wallet every time.
How to Collect with a Dynamic QR
Generate a per-transaction QR at checkout with the exact amount and reference encoded in the code.
How to Collect with an Alphanumeric Anchor
Register a tax ID or business alias as a payment point reachable from any connected network.
Monitor
Key Concepts
Payments Hub Architecture
The end-to-end model for clients integrating with Ledger, wallets, intents, proofs, bridges, external rails, and webhooks.
About Signers
Cryptographic identity on the ledger — how keys are created, registered, and used to authorize transactions.
About Claims
The structured building blocks inside every payment intent — what they encode and how they carry business intent.
About Domains
How domain-based addressing scopes wallets and anchors to an environment without collision or ambiguity.
About Schemas
How schemas validate and structure custom fields on wallets, anchors, and intents at the protocol level.
Where to start
Start with How to Connect to a Ledger to get your credentials and sandbox access in place. Once connected, follow How to Onboard a Merchant to create the wallet structure you will use in subsequent guides. From there, choose your path based on your use case — the send money guides cover push payments to accounts and aliases, while the collect money guides cover QR codes and alias-based payment points.