The Core Transactions API is in beta. Beta APIs can change without a version increment. Changes are announced in advance, and your Technical Account Manager works with you on them. See Versioning and backwards compatibility.
posted. It exists only once it has affected the balance. There is no pending state and no status field.
Types at a glance
type names the rail or mechanism that created the entry. ACH, checks, wires, instant payments, blockchain payments, internal transfers, fundings, and receivable sales each have a matching payment object on the Lead platform. Interest, fees, sweeps, Lead-generated entries, and legacy banking activity are posted by Lead and have no payment object. The Core Transaction Object lists every value.
From a payment to its ledger entries, and back
The join works in both directions.- Payment to ledger. Once a payment posts, the payment object carries the IDs of the core transactions it produced, in a shape that fits the rail.
- Ledger to payment. Read
type, then call that rail’s list endpoint withcore_transaction_id={id}. One core transaction can map to many payments, for example one settlement entry covering a batch of ACH entries.
Reading core transactions
List entries for one balance, filtered bytype and a created_at window, or retrieve one by ID. Core transactions do not emit webhooks today, so poll the list with a created_at window at whatever cadence your reconciliation runs. A suite of core transaction webhooks is planned; see Banking Infrastructure.

