Accounts and banks

Bank

A bank is a financial institution that Reconbanker knows how to log into. Reconbanker maintains the integration with each bank, so you do not have to build it yourself.

If your bank is not on the list, contact support so the team can add it.

Account

An account is a configuration record that represents one bank connection. It groups together everything Reconbanker needs to read that bank and act on what it finds:

• Bank credentials — the username and password used to log in. Stored encrypted.
• Session type — one-shot (periodic open→scrape→close) or persistent (long-lived monitor).
• Login mode — simple (unattended) or assisted (waits for a human to complete 2FA).
• Webhook URL — where results are delivered.
• Polling settings — when your user is in reconcile mode, the address of your pending-payments endpoint and the auth token to use.
• Optional extras — extra JSON fields to attach to every webhook payload.

The account is the unit of configuration. When you change the webhook URL, change session settings, or update credentials, you do it on the account.

Operation mode (reconcile vs passthrough) is not on the account — it is a single user-level setting that applies to every account you own. See Operation modes.

Multiple accounts

There is no limit on how many accounts you can have. A typical setup looks like one of these:

• One bank, one account.
• Multiple currencies — one account per currency.
• Multiple banks — one account per bank.
• A reseller managing several customers — one account per customer's bank connection.

Each account is configured independently. Two accounts can use different webhook destinations, different credentials, and different session types. They share only the user who owns them — and the user's operation mode applies to all of them.

Next

• Sessions — one-shot vs persistent, simple vs assisted login.
• Reconciliation — how matching works.
• Operation modes — reconcile versus passthrough.
• Account settings — every setting an account has.