When an iBanFirst wallet is read
Pulls each iBanFirst wallet the workspace holds with its currency and balance.
Trigger·Account
Integrations · Business bankingConnect iBanFirst to Well
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.
What Well pulls from iBanFirst
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 |
- Sync mode
- incremental polling
- Refresh
- scheduled
- Direction
- iBanFirst → Well
4 triggers from iBanFirst.
When a financial movement posts in iBanFirst
Captures debit and credit movements across all iBanFirst wallets with value date and counterparty.
Trigger·TransactionWhen an iBanFirst beneficiary is read
Pulls the external beneficiary bank account so the counterparty IBAN can be matched to a payment instrument.
Trigger·Payment methodWhen an iBanFirst document is available
Picks up downloadable iBanFirst documents such as account statements and RIBs.
Trigger·Document
What Well does with your iBanFirst connection
Connect
Connect iBanFirst over WSSE: you generate a iBanFirst key and paste it into Well, where it is stored encrypted at rest and never returned in responses.
Sync
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.
Enrich
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.
Available
Your data from iBanFirst lands in the workspace as currency-converted line, vendor, and outgoing transfer you can search, chart, and automate.
Questions iBanFirst unlocks
Ask in plain language. Well answers from your connected iBanFirst connection, resolved against the rest of your stack.
Ask Well
Ask anything about your iBanFirst connection
Summarise this month
What needs attention?
Find unmatched records
Ask about your iBanFirst connection…
Connect iBanFirst in three steps
- 01
Provide your iBanFirst WSSE credential
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.
- AuthWSSE (username + secret)
- TransportWell-hosted MCP
- Validationchecked against /api/wallets
- 02
Map your entities
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.
- Mappingpreconfigured by Well
- 03
Use the data
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.
- First syncstarts as soon as connect completes
The credential is held encrypted and never shown back. Existing movement history backfills in the background after the first connect.
How iBanFirst stays secure with Well
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.
WSSEEncrypted at restGDPR compliant
Read the full privacy and security policyScopes Well requests
- granted
Read iBanFirst records
Resources the iBanFirst MCP server exposes, scoped by your OAuth approval.
- granted
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.
- refused
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.
- refused
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.
Disconnect any time from Well settings or iBanFirst’s admin panel.
Frequently asked questions about iBanFirst and Well
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.
Pairs well with iBanFirst
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
Ready to connect iBanFirst?
Connect once. Every FX transfer, counterparty, wire from iBanFirst becomes searchable, queryable, and ready for your agents and tables. Disconnect any time.