Skip to main content
Everything you can build on runs through the same small set of objects — Entity (who) → Account (the product relationship) → Balance (tracked value) → Account Numbers (routable addresses) and Transactions (records of activity) — connected as the Object Model describes and composed differently per program. This section groups the platform by ownership and function: Customers & Accounts — the objects representing your end customers and their products. You are the ledger of record here: these are reporting APIs and files (Executing vs. Reporting) — the user surface on the Object Model page. Start with Entity; Accounts and Balances & Transactions carry the financial picture; Applications and Cards serve credit and card programs. Banking Infrastructure — the real bank accounts behind your program (FBOs, operating and settlement accounts — the core surface, Lead-managed) and the Account Numbers that make balances routable. Payment Rails — six execution APIs that move money: ACH · Wires · Instant Payments · Internal Transfer · Blockchain Payments · Checks. Choosing between them: Money Movement in Core Concepts. Funding & Settlement — funds flows between your program and Lead’s balance sheet or the card networks: Funding & Receivables (extending credit; selling receivables) and Network Settlement. Each product page links its endpoint documentation in the API Reference and, where a file transport exists, its schemas in the File Reference. Which surface each product uses today: Integration Surfaces by Product.