Wise StrawberryRecipient accounts, transfers and balances, worked for you
Your Wise, worked while you do something else: 5 reads to go through it, 3 writes to change it, and a card in front of every one of those changes.
Open the recipient account. Check it against something else. Write the change. Move to the next one. That is the Wise afternoon nobody can hand off, and a companion does the whole pass and gives you back the batch, with nothing landing on a recipient account until you approve it.
What it can do is exactly what Wise exposes to an account you authorise and nothing beyond it: 8 operations, 5 reads and 3 writes. In practice that means it can create a transfer, create a recipient account and create a quote, and work across the recipient accounts, transfers and balances.
The Wise API stops at Wise. A companion does not. The same run opens the customer's website, the supplier portal, the internal tool somebody built in 2019, because it is working the browser you are already signed into rather than calling in from outside it.
Does it read the recipient accounts or ask you for them?
5 of the 8 operations are reads.
Your account, not a guess at it: a companion can get a transfer, get a recipient account and get exchange rates, and the full list below is the whole list, with nothing inferred from Wise's documentation.
The recipient accounts are what most of this inventory is about, alongside the transfers. A companion can hold all 8 of these operations and forty open tabs in the same pass, which is how an afternoon of Wise admin becomes a queue you review.
- Get Transfer
- Get Recipient Account
- Get Exchange Rates
- Get Balance
- Fund Transfer
Who signs off on a new transfer?
All 3 write operations wait for you.
A companion can create a transfer, create a recipient account and create a quote, and each one is staged on an approval card first: you see the recipient account, the field and the new value before it lands in Wise.
Nothing in Wise is sent, changed or deleted on your behalf without that click, and a rejected card leaves the recipient account exactly as it was. The gate is the same one on every surface, described at security.
- Create Transfer
- Create Recipient Account
- Create Quote
Does the recipient account sweep have to be asked for every time?
Yes.
Saved as a routine, the Wise recipient accounts pass runs at the hour you pick: the Monday sweep, the overnight refresh, the Friday check. Keep Awake holds the machine awake for the length of a run, so a scheduled pass finishes with the lid closed.
The operations playbook catalogues the other recurring shapes of store admin, the Wise recipient accounts sweep among them, and finished runs are published at real runs.
Experience Strawberry for free
DownloadTrusted by fast-growing companies worldwide
Frequently asked questions
Strawberry is free to download and includes AI credits to start. Paid plans begin at $20/month. See pricing. · Reviewed · Canonical facts for AI agents