Financial Events Triggers

Understand financialEvents in VIEW Insights and how they differ from Feezback Co-agent trigger detection.

Use financial event data to identify meaningful account events inside VIEW Insights and distinguish them from business trigger detection.

Feezback exposes two distinct trigger-related mechanisms: structured financialEvents returned in VIEW Insights, and Feezback Co-agent, a higher-level sales and marketing trigger layer. Treat them as separate concepts when designing your integration.

Trigger mechanisms

MechanismWhere it appearsUse it for
financialEventsInside the VIEW Insights API responseStructured financial analysis, underwriting, review, and risk workflows.
Feezback Co-agentBusiness or marketing layer bundled with a Feezback View licenseSurfacing sales, advisory, or marketing opportunities.

financialEvents in VIEW Insights

The financialEvents object is returned inside the privateInsights[] object of the Insights API response.

Use it when your product needs to detect financial events such as insufficient funds, bank warnings, delayed repayments, unemployment payments, or bounced checks.

See View Report – Financial Report for the full VIEW flow.

Financial event types

Event typeMeaning
nsfEventsNon-sufficient-funds or bounced-payment events.
warningEventsBank warning notices on the account.
loanPaymentDelayEventsDelayed loan repayments.
closedLoanPaymentDelayEventsDelayed repayments on loans that are now closed.
unemploymentPaymentEventsUnemployment-benefit payments detected in the transaction stream.
technicalCheckBounceEventsBounced checks.

Typical use cases

Use financialEvents for workflows such as:

  • Credit underwriting
  • Affordability checks
  • Risk review
  • Customer financial analysis
  • Manual underwriter review
  • Internal compliance review

For example, a credit workflow can use loanPaymentDelayEvents and nsfEvents as inputs into a manual or automated review process.

How to retrieve financial events

  1. Create a VIEW consent link with srv: "view_ais/user".
  2. Wait for the user to grant consent.
  3. Wait for the triggers that will arrive via Webhooks


Did this page help you?