Transaction activity overview

Transaction activity is a live, unified feed of everything happening on your customers' instrumentsInstrument 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). — transfers, sends, wire transfersWire Transfer A transaction that moves funds between accounts. An incoming wire transfer moves funds from a third-party bank account to a Weavr managed account, while an outgoing wire transfer moves funds from a Weavr managed account to a third-party bank account. Wire transfers require the managed account to have an assigned IBAN (for EUR) or sort code and account number (for GBP)., card payments, fees, and system transactions — in a single, normalized shape. Unlike a statement, it includes in-flight activity: pending, processing, cancelled, and returned transactions, not just settled ones.

Transaction activity and statements

The two are complementary, and designed to line up:

Aspect	Transaction activity	Statements
Purpose	Live feed for in-app screens, operations, and investigation	Authoritative, immutable statement of record
Scope	All activity, pending and settled	Settled transactions only
Balances	No running balance	Opening and closing balances
Mutability	Reflects the current state, so it changes over time	Immutable — the same period always returns the same result

Use transaction activity when you need to show or react to what's happening now. Use statements when you need the record of what settled. A card payment, for example, surfaces here through its whole lifecycle, from authorization to settlement; once it settles, the same payment also appears as a single line in the statement.

Anything delivered by webhook is also retrievable here, and anything here is delivered by webhook, so there are no channel-specific gaps.

The normalized model

Every entry shares the same envelope, whatever the transaction type:

• type: the kind of transaction.
• status: a normalized lifecycle status, consistent across all types.
• direction: whether funds were credited to or debited from 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). (CREDIT or DEBIT).
• amount: the amount in 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).'s currency.
• fee: a summary of any fee charged for the transaction, linking back to the fee transaction itself.
• creationTimestamp and lastUpdatedTimestamp: when the transaction was created and last changed, in epoch milliseconds.
• transaction: the full, type-specific transaction object. Its schema matches the value of type.

You can render a consistent feed from the envelope alone, and drill into the transaction object when you need type-specific detail.

Transaction types

Type	Description
transfers	Internal transfer between instrumentsInstrument 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). of the same customer.
sends	Transfer between instrumentsInstrument 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). of different customers.
outgoing_wire_transfers	Wire transferWire Transfer A transaction that moves funds between accounts. An incoming wire transfer moves funds from a third-party bank account to a Weavr managed account, while an outgoing wire transfer moves funds from a Weavr managed account to a third-party bank account. Wire transfers require the managed account to have an assigned IBAN (for EUR) or sort code and account number (for GBP). to an external bank account.
correspondent_bank_transfers	Wire transferWire Transfer A transaction that moves funds between accounts. An incoming wire transfer moves funds from a third-party bank account to a Weavr managed account, while an outgoing wire transfer moves funds from a Weavr managed account to a third-party bank account. Wire transfers require the managed account to have an assigned IBAN (for EUR) or sort code and account number (for GBP). on behalf of a third-party originator.
incoming_wire_transfers	Wire transferWire Transfer A transaction that moves funds between accounts. An incoming wire transfer moves funds from a third-party bank account to a Weavr managed account, while an outgoing wire transfer moves funds from a Weavr managed account to a third-party bank account. Wire transfers require the managed account to have an assigned IBAN (for EUR) or sort code and account number (for GBP). received from an external bank account.
card_payments	A card payment with its full lifecycle.
fees	A fee charged or reversed 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)..
system_transactions	System-generated transactions, such as balance adjustments, account closures, and dispute outcomes.

Status

The status field is normalized across every transaction type:

Status	Meaning
DRAFT	The transaction id has been created. Further user actions are required before the transaction is a fully submitted, executable instruction. No balance movements have taken place on the target 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). yet.
SUBMITTED	The transaction has been submitted and is awaiting processing. No balance movements have taken place yet. Transactions scheduled for a future date stay in a submitted status.
PROCESSING	The submitted transaction is being processed.
COMPLETED	Executed and processed. Funds have moved and the actual balance has changed.
CANCELLED	The transaction was cancelled before completion. Funds have been returned to the original 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)..
RETURNED	The transaction was previously COMPLETED but has been returned. Funds have been returned to the original 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).. Note that card refunds may be separate transactions rather than purchases in a RETURNED status.

Retrieving transaction activity

You can query the feed three ways — across everything, for a single 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)., or for one transaction by id. See Retrieve transaction activity.