Your first transaction
How sending funds from a Botanary account is built, previewed, signed, and confirmed.
Sending money from a Botanary account follows the same build, preview, sign, relay flow as every other action on the account - here's what that looks like in practice for a simple send.
Build the transfer
Choose a recipient, an amount, and a token. Native ETH is always spendable with no extra setup; other supported tokens work the same way. You can also batch up to five recipients into a single transaction, backed by one signature.
Preview it
Before you're ever asked to sign, the transfer is previewed. If the preview says the transfer would fail, you'll see why - and you won't be asked to sign at all. A transfer declined here usually means one of the account's own rules refused it (an over-limit amount, a recipient not on the allowlist, a frozen account); a failure with no stated reason usually means something more basic, like not being able to cover the network fee.
Sign
You sign the operation client-side. Botanary's backend never sees your key and never signs on your behalf - it only ever relays what you've already signed.
Relay and confirm
The signed operation is submitted to the bundler and tracked until it reaches a terminal outcome: mined (it succeeded), reverted (it was included but execution failed), or rejected (the bundler never accepted it in the first place - no on-chain trace at all). Once it's mined, your balance, activity feed, and available gas methods all update to reflect it.
Where this goes next
Every send here works the same way whether you're moving native ETH or a stablecoin. To hand this same kind of spending power to someone else - a device, a dApp, or an agent - bounded and revocable, see the Accounts and delegations sections.