Skip to main content
Tesouro emits the following event types for embedded banking. Every delivery uses the common envelope; each event type below documents the attributes shape and includes an example payload.
attributes.rawData is a verbatim pass-through from the upstream banking core. Tesouro doesn’t control or guarantee its structure, field names, or stability - it can change without notice. Use the documented attributes fields for business logic. Treat rawData as opaque except for debugging and audit.

LEDGER_TRANSACTION

A monetary transaction posted to the ledger.

Attributes

Example

A LEDGER_TRANSACTION delivery for a $50 ACH incoming credit:

LEDGER_POSTING_EXCEPTION

Posting a transaction raised an exception.

Attributes

Same shape as LEDGER_TRANSACTION, with one difference: eventType is always "LEDGER_POSTING_EXCEPTION". rawData carries the upstream exception payload instead of a successful posting.

Example

LEDGER_ACCOUNT_EXCEPTION

A ledger account raised an exception.

Attributes

Same shape as LEDGER_TRANSACTION, with two differences: eventType is always "LEDGER_ACCOUNT_EXCEPTION", and routingNumber may be empty. rawData carries the upstream exception payload.

Example

ACCOUNT_STATUS_CHANGED

A ledger account’s status changed (for example, opened, closed, dormant, or charged off).

Attributes

Same shape as LEDGER_TRANSACTION, with two differences: eventType is always "ACCOUNT_STATUS_CHANGED", and routingNumber is empty. rawData carries the upstream status-change payload, including the new primary and secondary status values.

Example

ACCOUNT_RESTRICTION_CHANGED

A ledger account’s restrictions changed (for example, an account freeze was added for suspected fraud).

Attributes

Same shape as LEDGER_TRANSACTION, with eventType always "ACCOUNT_RESTRICTION_CHANGED". rawData carries the upstream restriction payload, including the action (actnCde is ADD, CHANGE, or DELETE) and the restriction detail.

Example