
When an iBanFirst wallet is read
Pulls each iBanFirst wallet the workspace holds with its currency and balance.


Read iBanFirst wallets, financial movements, and beneficiaries into Well over its WSSE-authenticated MCP server. A cross-currency transfer arrives as a converted line that keeps both sides, so multi-currency activity reconciles without redoing the foreign-exchange math.
iBanFirst feeds FX transfer, counterparty, wire into Well as a source. The connection is read-only; disconnect at any time from your workspace settings to revoke iBanFirst’s access.
| From iBanFirst | In Well | Relation | |
|---|---|---|---|
| FX transfer | Currency-converted line | Becomes | |
| Counterparty | Vendor | Resolves to | |
| Wire | Outgoing transfer | Categorizes as |


Pulls each iBanFirst wallet the workspace holds with its currency and balance.

Captures debit and credit movements across all iBanFirst wallets with value date and counterparty.

Pulls the external beneficiary bank account so the counterparty IBAN can be matched to a payment instrument.

Picks up downloadable iBanFirst documents such as account statements and RIBs.
Connect iBanFirst over WSSE: you give Well your iBanFirst username and secret, which it stores encrypted at rest and never returns in responses.
Well brings FX transfer, counterparty, and wire in from iBanFirst on a recurring poll that fetches only what changed since the last read. The first sync backfills history in the background and the connection stays live after.
Well resolves each iBanFirst entity into currency-converted line, vendor, and outgoing transfer, assigns categories, and links every record to an audit trail across the rest of your connected tools.
Your data from iBanFirst lands in the workspace as currency-converted line, vendor, and outgoing transfer you can search, chart, and automate.
Ask in plain language. Well answers from your connected iBanFirst connection, resolved against the rest of your stack.
Ask anything about your iBanFirst connection
Ask about your iBanFirst connection…
Each one answers a question from live iBanFirst data. The required ones return nothing until a source like it is connected.
Needs a source like iBanFirst
Know how many months of cash you have at your current burn, with both sides of the division shown.
See how long your cash lasts if a customer pays late, leaves, or you hire.
Know how much cash you hold right now, with the accounts counted and the ones left out both stated.
See a company's or household's spend by category, supplier and trend; not for savings: use Subscription spend.
Find the double charges and price rises in your bank debits, each with the dates and amounts your bank shows.
Know if payroll is safe, and which vendor bills to push if it is not.
Find what payment settled an invoice, or catch every payment that never got one.
Know what you spend in an average month over a window you can see, with the months that carried no spend counted.
See the settled month-end cash series and where the line goes from the last complete month.
See how the month moved from opening cash to closing cash, with whatever does not reconcile named as its own step.
See which suppliers owe you paperwork, in each of your files, for a month, a quarter or this week.
Put a name on every settled expense that still has no invoice.
Walk the whole month-end sweep in one prompt.
Drive the month-end close from open to sent to your accounting tool.
Work through your open accounting items by category.
Close the category gaps behind your spend before you close a month.
The board numbers in one pass, each with its scope and its window stated.
See what you paid a supplier, how its price moved, and get the negotiation email drafted.
See what each scheduled supplier costs a month and a year, how it moved, and where your workspaces can save.
Act on a subscription you name or pick by number from a list: cancel, renegotiate or contest a double debit.
See what you spent on one category, such as groceries, this month and how that compares to a usual month.
See what in a month has not reached the ledger, and which pile each item sits in.
Compare your bank with your books, list the gaps, and re-run what missed rows.
Answers better with iBanFirst
See how much of your cash and receivables sit outside your reporting currency.
Find the bills with no paperwork attached, before an auditor does.
See exactly which agents would run, before any of them does.
Turn mixed currencies into one number you can actually audit.
The measures you name, arranged on one board that stores the question rather than the answer.
Claim a refund or a compensation with the evidence in hand, and know what to say when you call.
Find money owed back to you: refunds, credit notes, VAT credits, double debits, then unpaid customer invoices.
Read a month of payslips, or each of several months, and state, per person, gross pay plus the employee deductions and the employer charges the payslip printed, then list the payroll related bills paid from the bank that no payslip carries.
For each supplier that looks like a freelancer, read the purchase invoices, the payment rail and any contract Well holds, and state the facts a requalification question turns on, next to the papers your country expects you to keep.
Uses iBanFirst when it is there
Connects and checks iBanFirst
iBanFirst authenticates with a WSSE credential, not an OAuth redirect. Open iBanFirst in Well's Connections panel and enter the username and secret iBanFirst issues you. Well validates them against your wallets through the Well-hosted iBanFirst MCP server and the connection goes live once they check out.
Well reads your wallets, the financial movements across them, the external bank accounts you pay, and the supporting documents, mapping a wallet to an account, a movement to a transaction, and a foreign-exchange transfer to a currency-converted line that keeps both sides.
Use it to reconcile multi-currency transfers against the settled amount, table beneficiaries for a wallet, or ask an agent what moved through an account last month. The connection is read-only, so iBanFirst stays the live banking surface.
The credential is held encrypted and never shown back. Existing movement history backfills in the background after the first connect.
iBanFirst uses a WSSE credential rather than an OAuth redirect: you supply a username and secret that Well validates against your wallets through the Well-hosted iBanFirst MCP server. The secret is encrypted at rest, never logged, and never returned. Access is read-only over your wallets and movements, and rotating the secret on iBanFirst's side cuts off the old credential at once.
Read iBanFirst records
Resources the iBanFirst MCP server exposes, scoped by the username and secret you paste into Well.
Resolve FX transfer, counterparty, and wire across your stack
Match identifiers in iBanFirst against the same entities your other connected tools expose, so each record carries cross-tool context.
Modify or delete iBanFirst records
Not granted; iBanFirst is read-only in Well. Write-back is opt-in per connector when a write surface exists.
Read API keys from iBanFirst's settings
Well only sees the keys you paste in. The keys never leave Well's secret store back to iBanFirst's admin surface.
iBanFirst authenticates with a WSSE credential rather than an OAuth redirect. In Well's Connections panel, open iBanFirst and provide the username and secret iBanFirst issues you; Well validates them against your wallets through the Well-hosted iBanFirst MCP server and the connection goes live once they check out. The secret is held encrypted and never shown back.
iBanFirst is a multi-currency and foreign-exchange provider, so Well reads your wallets, the financial movements across them, the external bank accounts you pay, and the supporting documents. A wallet becomes an account in the workspace, a movement becomes a transaction, an external bank account becomes a payment means, and each document is kept as the audit attachment for the transfer it belongs to.
A foreign-exchange transfer arrives as a currency-converted line that keeps both the sent and the received side, so a EUR-to-USD payment shows the conversion rather than a single flattened figure. The counterparty on the transfer resolves to the vendor it represents, and an outgoing wire is categorised as the outbound transfer it is, which lets the workspace reconcile against the settled amount in either currency.
Yes. Each wallet carries its movements and the external bank accounts it has paid, so a question like which beneficiaries a wallet has sent to, or what moved through it last month, answers from the workspace. Every movement keeps its iBanFirst identifier and the document behind it, so a converted line always traces back to the original transfer record.
Well reads wallets and financial movements through the iBanFirst MCP connection and folds new movements in as they settle, with the first connect pulling existing history in the background. iBanFirst stays the live banking surface; Well keeps a queryable copy so multi-currency balances and transfers sit alongside the rest of your financial records.
Disconnect iBanFirst in Well and Well stops reading through the MCP server immediately; rotating the WSSE secret on iBanFirst's side guarantees the old credential can no longer be used. The wallets, movements, and documents already read stay in your workspace for reporting, and you can ask Support to purge them if your compliance flow requires it.
More in Business banking

Anytime
Connect Anytime to Well to sync business bank accounts and transactions.

Blank
Connect Blank to Well to sync business bank accounts and transactions.

Bourso Business
Connect Bourso Business to Well to sync business bank accounts and transactions.

Husk
Connect Husk to Well to sync business bank accounts and transactions.
Popular cross-category

Connect once. Every FX transfer, counterparty, wire from iBanFirst becomes searchable, queryable, and ready for your agents and tables. Disconnect any time.