Integration Surfaces by Product - Lead

Lead’s platform is completing a transition to a fully API-based integration model. This page describes the recommended integration path for new partners: how each product and workflow is integrated today. Where an API exists, it is the path we support and recommend. A blank cell means that column does not apply to that row. See the Platform Evolution page for details on the upcoming changes.

Product / workflow	Create & manage	Move money	Reporting & reconciliation
BUILD ON LEAD
Deposit accounts	`API` Accounts API	`API` ACH, Wire, Instant Payments, and Internal Transfer APIs	`File` Daily Balances and Transactions files
Credit & lending accounts	`API` Applications API, Accounts API, Create Subledger Balance API, Funding API	`API` Funding API to originate; disburse over any payment-rail API	`File` Daily Balance and Transactions files
Cards	`API` Cards API `Beta`	Card transactions settle through your issuer processor and network settlement, not a Lead payment surface.	`File` Daily Transactions file from Lead, plus settlement files from the card networks
Receivables purchase (daily sale)		`File` Sales Request / Response exchange over SFTP. API planned — see Platform Evolution.
MOVE MONEY
ACH	`API` Originators API	`API` ACH API	`File` ACH Cash Recon report
Wires (domestic and USD international)		`API` Wires API. A version migration is in progress.
Instant Payments		`API` Instant Payments API. FedNow is live.
Internal Transfers		`API` Internal Transfer API
Blockchain Payments		`API` Blockchain Payments API `Beta`
Checks		`File` X9 file exchange, the industry clearing format for check images	`File` X9 files
SUPPORTING OBJECTS
Customers (Entities)	`API` Entity API
Account Numbers	`API` Account Number API
Originators (ACH origination parameters)	`API` Originators API
WHAT YOU REPORT TO LEAD
Balances and transactions (your customers’ ledger)			`File` Daily Balances, Transactions, and Non-Posted Transactions files over SFTP
Receivables purchase (daily sale)		`File` Sales Response file confirming each day’s purchase; settlement from your operating account. `API` Sale API arriving — see Platform Evolution
Compliance documents			`File` SFTP delivery. Also referenced in Accounts and Applications payloads.
WHAT LEAD SENDS YOU
Daily reports			`File` Daily Balance, Daily Activity, ACH Cash Reconciliation, Platform Reconciliation, network settlement reports, and the daily Sales Request — delivered over SFTP

Where Files Remain Today

Everything you build is created over APIs, and every payment rail except checks is an API. Files remain in three places: Daily reporting to and from Lead. Daily balances, transactions, and the daily report set travel over SFTP. This is one pipeline, shared across every product, and it is the same whether you are building deposits, lending, or cards. The receivables sale (API planned). Lending and card-credit programs confirm each day’s receivables purchase through the Sales Request/Response exchange today. A Sale API is in flight (Platform Evolution); the daily cycle is unchanged across the transition. Industry clearing formats. X9 for checks and card network settlement files are how those networks work. They are not part of the API transition. If you are scoping file infrastructure for a new integration, the answer is one SFTP consumer for the daily file set, plus X9 only if you are doing checks.

​Where Files Remain Today

Where Files Remain Today