Paystack StrawberryFrom the customers to the virtual terminals, in one Paystack pass
One sentence in, and a companion has been through the Paystack customers, put them where you can read them, and marked the ones it was not sure about.
Open the customer. Check it against something else. Write the change. Move to the next one. That is the Paystack afternoon nobody can hand off, and a companion does the whole pass and gives you back the batch, with nothing landing on a customer until you approve it.
What it can do is exactly what Paystack exposes to an account you authorise and nothing beyond it: 25 operations, 14 reads and 11 writes. In practice that means it can update a virtual terminal, update a customer and set a customer risk action, and work across the customers, virtual terminals and transactions.
The Paystack API stops at Paystack. 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.
What does it already know about your virtual terminals?
14 of the 25 operations are reads.
Your account, not a guess at it: a companion can verify a transaction, validate a customer and unassign destination from virtual terminal, and the full list below is the whole list, with nothing inferred from Paystack's documentation.
The customers are what most of this inventory is about, alongside the virtual terminals. A companion can hold all 25 of these operations and forty open tabs in the same pass, which is how an afternoon of Paystack admin becomes a queue you review.
- Verify Transaction
- Validate Customer
- Unassign Destination from Virtual Terminal
- List Virtual Terminals
- List Transactions
- List Customers
- Initialize Transaction
- Initialize Direct Debit
- Fetch Virtual Terminal
- Fetch Transaction
- Fetch Mandate Authorizations
- Fetch Customer
- Export Transactions
- Direct Debit Activation Charge
What happens before it can update virtual terminal?
All 11 write operations wait for you.
A companion can update a virtual terminal, update a customer and set a customer risk action, and each one is staged on an approval card first: you see the customer, the field and the new value before it lands in Paystack.
Nothing in Paystack is sent, changed or deleted on your behalf without that click, and a rejected card leaves the customer exactly as it was. The gate is the same one on every surface, described at security.
- Update Virtual Terminal
- Update Customer
- Set Customer Risk Action
- Remove Split Code from Virtual Terminal
- Deactivate Virtual Terminal
- Deactivate Authorization
- Create Virtual Terminal
- Create Customer
- Charge Authorization
- Assign Destination to Virtual Terminal
- Add Split Code to Virtual Terminal
Can it verify transaction every morning by itself?
Yes.
Saved as a routine, the Paystack customers 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 Paystack customers 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