Banking
Everything an engine reads from a bank, a card issuer or a consumer-finance provider
Where it lives: the whole family arrives in one object from the Financial Position endpoint, and each part of it is also served on its own. In a widget flow the same models travel inside the session results.
A banking extraction answers three questions about a person or a company at one institution: what they hold (accounts, cards, deposits, investments), what they owe (loans, mortgages, credit), and what moves (transactions and standing charges). It is the raw material for affordability, income verification, solvency and account-ownership checks — read from the institution itself rather than from a document somebody typed.
Reading any of these models
Every product in this family shares the same envelope, so once you can read one you can read all of them:
A missing product is not an empty product. If a feature was not requested, its key is absent from the global position and its endpoint answers 204. If it was requested and the customer has none, you get an empty list. The two mean very different things — see Reading the results.
The pages in this family
Current and savings accounts, their balances, their holders, and the transactions behind them — categorised.
Debit, credit and prepaid cards, their limits and their movements.
What is owed to this institution: amount granted, outstanding, instalment and rate.
Term deposits and savings goals — money set aside, and what it is being set aside for.
Securities accounts, stocks, funds and private pension plans, with valuations and performance.
The standing charges against an account: who charges, how much, how often.