Skip to main content
Business-rule checks let you evaluate each account against rules that matter to your product — for example, a minimum salary or a minimum average balance — as part of the consent journey. Each check is evaluated against an account’s data while the journey runs, and the outcome is returned per account so you can act on it (approve, decline, route the applicant, and so on). Checks are an opt-in feature that is configured per product and layered on top of the AA + PDF flow — the request and response contracts are the same, with checks added wherever accounts appear.
This section builds on the AA + PDF flow. If you have not integrated that flow yet, start with the AA + PDF Enabled section first — it covers the full integration flow, status tracking (webhook, polling, and UI events), data fetch, and the quick reference. Checks simply add a checks object to each account (and an optional checks_overrides field on the Initiate Consent request).

The checks object

Wherever an account is returned — in the webhook, the status polling response, and the raw FI data — it carries a checks object describing the outcome of every check evaluated for that account.

Fields

Pages in this section