> This page is for Financial Rider Flow. > For clean Markdown of any page, append .md to the page URL. > For a complete documentation index, see https://infonite.dev/llms.txt. > For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://infonite.dev/_mcp/server. # Features A Financial Rider session reads the **features** you name in `settings.executions_features` when you [create it](https://infonite.dev/flows/financial-rider/api-reference/financial-rider-api/sessions-management/flows-financial-rider-v-1-session-create): each one is a family of your customer's finances, read from every bank they connect, and what the banks return is merged into one **Financial Position**. The feature model itself — the same codes in every product — is in [Features](/guides/features), in Platform. --- ## What a session can read | Feature | What it reads | Where it comes back | | :-------------------------- | :-------------------------------------------------------------------------------------------------------------------- | :------------------------------------------------------------------------ | | `customer_information_read` | Your customer as the bank knows them: name, document, contact details and addresses. | [Customer Profile](/flows/financial-rider/data-models/customer-profile) | | `accounts_read` | Current and savings accounts, with their balances — and, when you configure it, their holders and their transactions. | [Accounts](/flows/financial-rider/data-models/banking/accounts) | | `cards_read` | Debit, credit and prepaid cards, with their limits — and, when you configure it, their transactions. | [Cards](/flows/financial-rider/data-models/banking/cards) | | `deposits_read` | Term deposits and savings products. | [Deposits & savings](/flows/financial-rider/data-models/banking/savings) | | `loans_read` | Loans and mortgages. | [Loans & mortgages](/flows/financial-rider/data-models/banking/credit) | | `investment_accounts_read` | Securities accounts. | [Investments](/flows/financial-rider/data-models/banking/investments) | | `stocks_read` | The stocks your customer holds. | [Investments](/flows/financial-rider/data-models/banking/investments) | | `funds_read` | Investment funds. | [Investments](/flows/financial-rider/data-models/banking/investments) | | `pensions_read` | Private pension plans. | [Investments](/flows/financial-rider/data-models/banking/investments) | | `direct_debits_read` | Direct debits. | [Direct debits](/flows/financial-rider/data-models/banking/direct-debits) | Any other feature code is refused when the session is created: `422`, on its position in `executions_features`. --- ## Asking for them Name a feature by its code, or as an object when you configure it — and mix both forms in one list: ```json { "settings": { "executions_features": [ "customer_information_read", { "code": "accounts_read", "configurations": { "read_transactions": true, "read_holders": true, "from_date": "60 days ago" } }, { "code": "cards_read", "configurations": { "read_transactions": true, "from_date": "60 days ago" } }, "loans_read" ] } } ``` Leave `executions_features` out and the session reads your application's default; with neither, it is refused. ### Which banks a session offers * **A bank is offered when it reads at least one of the features you ask for.** So one bank may return less than another: `retrieved_features`, in the results, says what some connection actually delivered. * **`customer_information_read` never decides on its own.** Every bank returns it, so it never makes a bank worth offering — unless it is all you ask for. * **A named engine must read one of them.** With `engine_reference`, an engine that reads none of the features you ask for is refused: `422`, `engine_serves_no_requested_feature`, on `settings.engine_reference`. --- ## Transactions: accounts and cards `accounts_read` and `cards_read` read the products alone unless you ask for more. Their `configurations` say what else, and over which window of time: | Setting | Default | What it does | | :------------------ | :------------ | :------------------------------------------------------------------------------------------------------------------------------------------------ | | `read_transactions` | `false` | Reads the movements of each account or card, within the window below. | | `read_holders` | `false` | `accounts_read` only: reads who holds each account. | | `from_date` | `30 days ago` | The first day of the window: a date (`2026-09-01`) or an expression such as `60 days ago`. | | `to_date` | `today` | The last day of the window. | | `limits_behaviour` | `error` | What happens to a window beyond the limits: `error` refuses the session when it is created, `adapt` moves the dates to the nearest limit. | | `filter_by_type` | every type | `cards_read` only: the card types to read — `financial_card:credit`, `financial_card:debit`, `financial_card:prepaid` and `financial_card:mixed`. | **The limits.** A window reaches back at most **two years** for accounts and **one year** for cards, and never past today. > **Note** > > The window is fixed when the session is created: `60 days ago` means sixty days before that moment, whenever your customer connects. --- ## Next #### [What comes back](/flows/financial-rider/data-models/overview) Every family a session returns, field by field. #### [Choosing the banks](/flows/financial-rider/overview#choosing-the-banks) Letting your customer choose, or naming the bank.