Statements overview

A statement is an authoritative, immutable record of the settled activity on an instrumentInstrument A financial product owned by an Identity. There are two types: Managed Accounts (stored-value accounts that hold balances and can receive wire transfers) and Managed Cards (prepaid cards - virtual or physical - used for purchases). over a period. It reports the opening and closing balances for the period, every transaction that posted to the instrumentInstrument A financial product owned by an Identity. There are two types: Managed Accounts (stored-value accounts that hold balances and can receive wire transfers) and Managed Cards (prepaid cards - virtual or physical - used for purchases)., and the regulatory footer required to present it to an end customer.

Weavr exposes two complementary ways to retrieve the financial activity on an instrumentInstrument A financial product owned by an Identity. There are two types: Managed Accounts (stored-value accounts that hold balances and can receive wire transfers) and Managed Cards (prepaid cards - virtual or physical - used for purchases).:

Endpoints	What they're for
Statements	Authoritative, immutable statement of record — for compliance, audit, and end-customer statements. Documented in this section.
Transaction activity	Live feed of all transaction activity, pending and settled — for in-app screens, operational tooling, and investigation. Documented under Transaction activity.

Why statements and transaction activity are separate

The two use cases pull in opposite directions. A statement is a record: it has to be stable, repeatable, and verifiable, because end customers and auditors rely on it. A live activity feed is the opposite: it has to surface in-flight activity the moment it happens, including authorizations that may never settle.

Serving both from a single endpoint forces compromises on both, so we provide a dedicated set of endpoints for each:

• Use the statement endpoints when you need the record of what settled in a period — the view you put in front of an end customer.
• Use the transaction activity endpoints when you need the live, filterable feed of everything happening on an instrumentInstrument A financial product owned by an Identity. There are two types: Managed Accounts (stored-value accounts that hold balances and can receive wire transfers) and Managed Cards (prepaid cards - virtual or physical - used for purchases)., including pending activity. See Transaction activity for details.

This page and the rest of this section cover statements. Transaction activity is documented separately, and the two are designed to line up: a completed transaction shown as a single line in a statement is the same transaction you can follow through its lifecycle in the transaction activity feed.

What you can rely on

• Posted activity only: every entry represents a transaction that has settled and where the actual balance of the instrumentInstrument A financial product owned by an Identity. There are two types: Managed Accounts (stored-value accounts that hold balances and can receive wire transfers) and Managed Cards (prepaid cards - virtual or physical - used for purchases). has changed. Pending authorizations and in-flight transfers don't appear.
• Immutable: requesting the same period twice returns the same result, so you can cache it.
• Authoritative balances: opening and closing balances are computed by Weavr against the entries in the period. You don't need — and shouldn't attempt — to reconstruct them client-side.
• Organized by type: every entry declares its transaction type, and the fields specific to that type appear in well-defined places on the entry, rather than bundled into a generic, untyped map.
• Compliance content built in: the footer carries the regulatory text and any card-scheme content required for digital statements.

Retrieving a statement

Statements are retrieved per instrumentInstrument A financial product owned by an Identity. There are two types: Managed Accounts (stored-value accounts that hold balances and can receive wire transfers) and Managed Cards (prepaid cards - virtual or physical - used for purchases).. The two endpoints share the same contract:

• A statement for a managed account.
• A statement for a managed card.

You can retrieve a statement as JSON for programmatic use, as a PDF for download and presenting to end customers, or as CSV. The PDF is our curated, out-of-the-box rendering of the statement, including the regulatory footer.

To see how a statement and its individual records can be presented to an end customer, use our open-source UI reference implementation.

Migrating from the previous statement endpoints

The statement endpoints described in this section supersede the previous statement behaviour, which is now deprecated. The new behaviour is opt-in during the migration window, and migration is non-breaking — existing integrations keep working unchanged. The per-instrumentInstrument A financial product owned by an Identity. There are two types: Managed Accounts (stored-value accounts that hold balances and can receive wire transfers) and Managed Cards (prepaid cards - virtual or physical - used for purchases). statement pages explain how to opt in.