checks object describing the outcome of each check for that account. This is layered
on top of the AA + PDF flow — the rest of the payload is unchanged.
This section builds on the AA + PDF flow. The
checks object appears on each AA account (under a consent) and on each PDF account. See Overview for the checks object shape and field reference, and AA + PDF → Track Status for the full payloads (including in-iframe UI events).- Webhook (Recommended)
- Status Polling
The terminal webhook is pushed when the journey completes. With checks enabled, each account — whether sourced from AA or from a PDF statement — includes a When AA fails and the journey falls back to a PDF statement upload, the PDF step is The
checks object under checks.indicators[].In the example below, AA delivered the data so the PDF step is SKIPPED. The same check (MIN_SALARY_15000) is evaluated across accounts: the first AA account fails it (salary 12000) and a second AA account passes it (salary 40000). A consent may also have no checks object when no checks apply to it.SUCCESS and the checks object appears on each PDF account instead — using the identical shape.checks object follows the same shape everywhere: read checks.indicators[] for the list of checks, and inspect each entry’s result (PASS or FAILED) along with the metadata values used to evaluate it.