Flutterwave StrawberryHand the Flutterwave transactions to a companion
A companion works the 2 operations your Flutterwave account exposes. It can create a transfer, and every one of those waits on an approval card showing the transaction before it changes.
Open the transaction. Check it against something else. Write the change. Move to the next one. That is the Flutterwave afternoon nobody can hand off, and a companion does the whole pass and gives you back the batch, with nothing landing on a transaction until you approve it.
What it can do is exactly what Flutterwave exposes to an account you authorise and nothing beyond it: 2 operations, 1 read and 1 write. In practice that means it can create a transfer, and work across the transactions and transfers.
The Flutterwave API stops at Flutterwave. 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.
Where do the transactions come from?
1 of the 2 operations is a read.
Your account, not a guess at it: a companion can verify a transaction, and the full list below is the whole list, with nothing inferred from Flutterwave's documentation.
The transactions are what most of this inventory is about, alongside the transfers. A companion can hold all 2 of these operations and forty open tabs in the same pass, which is how an afternoon of Flutterwave admin becomes a queue you review.
- Verify Transaction
Which transactions wait for your approval?
The one write operation there is waits for you.
A companion can create a transfer, and each one is staged on an approval card first: you see the transaction, the field and the new value before it lands in Flutterwave.
Nothing in Flutterwave is sent, changed or deleted on your behalf without that click, and a rejected card leaves the transaction exactly as it was. The gate is the same one on every surface, described at security.
- Create Transfer
What does the recurring transactions pass look like?
Yes.
Saved as a routine, the Flutterwave transactions 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 Flutterwave transactions 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