Wise Business
Keep Wise Business in step with your orders, invoices and payments without re-keying, with the right person approving what changes.
33 ways to read, 2 ways to write, each write switched on by you.
Quality checks
Built and tested with example responses.
- Ready to connect: doneEvery listed action is built in.
- Built and tested with example responses: doneEach action is built from the provider’s published API and tested against example responses, errors, rate limits and paging.
Connected, approved, proven.
The things teams do most with Wise Business, an example flow with a person in the loop, and what Nexra keeps as proof.
Top actions
- Create quoteApproval by rule
- Get deposit limitRead
Example flow
- Wise Business · Get deposit limitDone
- Wise Business · Create quoteNeeds approval
- Nexra · Record the decision and result in the evidence chainProven
Example workflow. Routine runs go through on their own. Only a change your rules flag, such as one over a limit you set, waits for the right person, who sees the exact change and the rule before it reaches Wise Business.
What gets logged
- Whether it ran on its own or who approved it, and under which rule
- A fingerprint of the exact request sent to Wise Business
- Wise Business's reply: what it created or changed
- One entry in the evidence chain, linked to the one before
Try this in the sandbox
Run the whole flow with test data in your sandbox, then connect a Wise test account before you go live.
For developers
Technical detail
Wise Business profiles, balances, statements, activity, bank details, recipients, quotes, requirements, rates, comparisons, read-only transfers and card disputes.
Wise API docs- Source actions
- 33
- Destination actions
- 2
- Data types
- 26
What you can map
Reads are always available. Writes are off until you switch them on for a connection, and governed writes follow your policies.
Account details orders1
- List bank account details ordersSource
Requests for receiving bank details in one currency and their outstanding requirements.
Account requirements1
- List recipient account requirementsSource
Which recipient account types and fields Wise needs for a quote's currency route (dynamic form definition).
Activities1
- List activitiesSourceIncremental
Profile activity feed (transfers, card spend, conversions, deposits) with cursor paging.
Balance capacity1
- Get deposit limitSource
The regulatory deposit (hold) limit for the profile, in a chosen currency.
Balance currencies1
- List balance currenciesSource
Currencies the profile can hold a balance in or add funds to.
Balances2
- Get balanceSource
One balance by ID.
- List balancesSource
Multi-currency balances (standard balances and jars) with available, reserved and cash amounts.
Bank account details2
- Get bank account detailsSource
One set of receiving bank details by ID: holder name, IBAN or sort code, routing number and institution.
- List bank account detailsSource
Receiving bank details (local and international) for each balance currency, including currencies not yet issued.
Comparisons1
- Compare provider pricesSource
Estimated price and speed of Wise and other providers for a currency route and amount. Moves no money.
Currencies1
- List currenciesSource
Currencies Wise supports for transfers.
Delivery estimates1
- Get delivery estimateSource
Live estimate of when a transfer will reach the recipient's bank.
Disputes2
- Get card disputeSource
One card transaction dispute by ID, with reason and status.
- List card disputesSource
Disputes the business raised on Wise card transactions, with reason and status. Read only.
Incoming transfers1
- Get incoming transferSource
A payment received into a balance: scheme, references, credited time and the payer's name and bank.
Multi currency account1
- Get multi-currency accountSource
The profile's multi-currency account: its ID, the recipient ID used to pay into it, and whether it is active and eligible.
Multi currency eligibility1
- Check multi-currency account eligibilitySource
Whether a profile, or a country (and US state), is eligible for a multi-currency account and which type.
Payin currencies1
- List pay-in currenciesSource
Balance currencies that also support receiving bank account details.
Profiles2
- Get profileSource
One profile, by default the configured business profile.
- List profilesSource
Personal and business profiles the token can act for.
Quotes3
- Create quoteDestinationNot retried automaticallyApproval before production
Prices a conversion or payment for the profile. A quote moves no money; it expires unless a transfer is created from it, which Nexra does not do.
- Get quoteSource
One quote with rate, fees and payment options.
- Update quoteDestinationProvider duplicate protectionApproval before production
Attaches a recipient account or payout method to a quote so its price and options reflect the route. Moves no money.
Rates1
- List exchange ratesSource
Current, historic (time) or ranged (from/to with grouping) Wise mid-market rates.
Recipients2
- Get recipient accountSource
One recipient account by ID.
- List recipient accountsSource
Saved recipient accounts for the profile, optionally by currency and type.
Statement transactions1
- List balance statement transactionsSourceIncremental
Balance statement lines for one balance and period, with fees, running balance and counterparty details.
Total funds1
- Get total fundsSource
Total worth, available funds, cash and overdraft across all balances, converted to one currency.
Transfer payments1
- List transfer paymentsSource
Completed pay-ins that funded a transfer.
Transfer payout info1
- Get transfer payout informationSource
Banking partner reference and delivery mode for a sent transfer, to trace it with the recipient's bank.
Transfer requirements1
- Check transfer requirementsSource
Validates the details a transfer from a quote to a recipient would need (reference length, purpose, source of funds). Creates no transfer.
Transfers2
- Get transferSource
One transfer with status, amounts, rate and reference.
- List transfersSourceIncremental
Transfers for the profile (read-only), filterable by status, currencies and creation date.
Webhook subscriptions2
- Get webhook subscriptionSource
One profile webhook subscription. Read-only.
- List webhook subscriptionsSource
Profile webhook subscriptions and the events they listen for. Read-only.
Access and limits
- Authentication
- Wise personal API token (Bearer)
- Plans and access
- Wise Business accounts can create personal API tokens; partner OAuth access needs a Wise Platform agreement. Personal API tokens act for the business account. Wise documents some endpoints (recipient read and quote create) under user tokens; balance statements need strong customer authentication outside the US, CA, AU, NZ, SG and MY.
- Test environment
- Sandbox lives at api.wise-sandbox.com with separate sandbox tokens and test data; it supports GBP, USD and EUR most reliably.
- Rate limits
- Wise returns HTTP 429 with Retry-After and X-Rate-Limited-By when limits are exceeded; fixed numbers are not published. Nexra honours Retry-After.
- Pagination
- Transfers use limit/offset; activities use size and a nextCursor; recipients use size (max 20) and seekPosition. Other reads return one page.
- Provider events
- Wise webhooks for transfer state changes, balance credits and updates, and profile events (subscriptions are managed by API or in settings). Flows run on demand, on a schedule, or when a scheduled check finds new or changed records.
Before you build a flow
- Transfers are read-only: creating, funding and cancelling transfers, batch groups, conversions between balances, balance create or delete, and recipient create or deactivate are intentionally not automated.
- Requests use the URL-versioned 2026Q4 API; Wise may change behaviour in later quarterly versions.
- Wise's reference lists GET /accounts (recipients) and POST /profiles/{profileId}/quotes under user tokens only, while its personal token guide says tokens can retrieve recipients and create quotes. Confirm against the account; a 401 or 403 means the token type is not accepted.
- Balance statements are protected by strong customer authentication for profiles outside the US, CA, AU, NZ, SG and MY; personal tokens cannot pass SCA, so those requests fail with 403.
- Wise filters transfers by creation date and activities by timestamp; there is no updated-since filter for transfers.
- Quote creation has no idempotency key; each request creates a separate quote that expires if unused.
- Cards, direct debits, batch groups, KYC, SCA and partner (OAuth) onboarding endpoints are not covered. Ordering new bank account details and creating balances are intentionally not automated.
- Bank account details are listed with the 2026Q3 endpoint (documented for personal tokens, all countries); the 2026Q4 get-by-ID endpoint covers GB, US and BE only.
- Several added reads (multi-currency account, eligibility, balance and pay-in currencies, delivery estimates, account requirements, incoming transfers, webhook subscriptions, quote update) are documented for user tokens only; a personal token may receive 401 or 403.
- Quote update attaches a recipient or payout method to an existing quote and moves no money; transfer requirements validation (POST /transfer-requirements) creates nothing.
- Incoming transfers have no list endpoint; the ID comes from Wise's incoming-transfer webhook. Webhook subscriptions are read-only.
- Available and pay-in currency responses are documented only as a list of currencies; Nexra accepts plain codes or objects with a code.
- Payouts and settlements: Wise is a money-transfer account, not a card acquirer, so it has no payouts or settlements. Money in and out of the account is read from balance statement transactions (statement_transactions.list, with fees) and transfers (transfers.list).
- Refunds: Wise is a money-transfer account, not a card acquirer, so there is no refund list. Bounced or cancelled transfers are refunded to the balance: read them with transfers.list and status funds_refunded (filtered by creation date), and the matching CREDIT lines in balance statement transactions. Card refund transactions are only available per card through Wise Platform card endpoints, which are not covered.
- Disputes: Wise has no merchant chargeback API. disputes.list and disputes.get read the disputes the business raised on its own Wise card transactions (documented for user tokens); Wise offers no date filter for them, so they are not incremental.
Developer reference
- Create the Wise credentials described above with the narrowest permissions your flows need.
- In Nexra, open Connect, then Connections, then New connection, choose Wise Business, enter its settings and credentials, and tick only the write actions you need. Connection guide
- Test the connection, then use its actions as flow sources and destinations. Flow guide
Machine-readable detail: GET /api/public/connect/connectors/wise and the Connections API.