Account settings
Every toggle you can change on an account and what it controls.
Account settings
Every account in Reconbanker has its own settings page. This page lists each toggle, what it does, and what the default is.
You can change settings either from the dashboard's Settings tab on an account, or by calling PUT /accounts/:accountId/config (see Reference → Accounts).
The settings
| Setting | What it controls | Default |
|---|---|---|
| Session type | one-shot (Reconbanker opens, scrapes, and closes on a schedule) or persistent (long-lived browser monitor that stays connected). See Sessions. | one-shot |
| Login mode | simple (Reconbanker logs in unattended) or assisted (Reconbanker pauses and waits for a human to complete 2FA inside the bank's page). | simple |
| Pending orders endpoint | URL Reconbanker calls to fetch the payments you are expecting. Required when your user is in reconcile mode. Ignored in passthrough. | empty |
| Polling method | GET or POST - the HTTP method Reconbanker uses to call your pending orders endpoint. | GET |
| Polling body | JSON body sent when polling method is POST. Ignored otherwise. | empty |
| Polling auth type | bearer (Reconbanker sends Authorization: Bearer <token>) or api_key (sends Authorization: Api-Key <token>). | bearer |
| Polling auth token | The token Reconbanker attaches to the polling request. | empty |
| Webhook URL | URL Reconbanker calls when there is a result to deliver. Required. | empty |
| Webhook auth type | Auth scheme for the webhook. Falls back to the polling auth type when empty. | empty |
| Webhook auth token | Token attached to webhook calls. Falls back to the polling auth token when empty. | empty |
| Notification endpoint URL | URL for the operational notification webhook — OTP requests, login failures, scrape failures. Separate from Webhook URL, which carries reconciliation results. | empty |
| Notification auth type | Auth scheme for the notification endpoint: bearer or api_key. | empty |
| Notification auth token | Token attached to notification calls. | empty |
| Notification events | Which events to send: any of assistance_required, login_failed, scrape_failed. | empty |
| Retry limit | How many times Reconbanker will retry matching before marking a request as failed. | 3 |
| Notify on expired | When on, Reconbanker fires the webhook with status: "expired" for requests that timed out after 5 days. | off |
| Extra webhook fields | A JSON object merged into every webhook payload. Cannot override the reserved keys external_id, status, amount, currency, name, id, received_at. | empty |
| Silent ingestion (passthrough only) | When on, Reconbanker records bank transactions but does not call the webhook for them. Useful for backfills. | off |
| Bank credentials - username | The username for your online banking site. | empty |
| Bank credentials - password | The password for your online banking site. Stored encrypted. Leave both fields blank to keep current credentials. | empty |
Operation mode (reconcile vs passthrough) is not on the account — it is a single user-level setting. Change it from the user settings dialog or via
PUT /me/operation-mode. See Operation modes.
Required versus optional
The only setting that is always required is Webhook URL.
If your user is in reconcile mode, Pending orders endpoint is also required on every account.
If the account scrapes a real bank, you must provide Bank credentials the first time. After that, leave the fields blank to keep what is stored.
Token resolution for webhooks
If you set a dedicated Webhook auth token, Reconbanker uses it. If you leave it blank, Reconbanker uses the Polling auth token as a fallback. If both are blank, Reconbanker sends the webhook without an Authorization header.
The same fallback applies to Webhook auth type: webhook value first, polling value as backup.
What changes when you switch operation mode
Operation mode is a user-level switch, so changing it affects every account at once. See Operation modes → Switching modes for what happens to existing orders and bank transactions.