ifthenpay StrawberryHand the ifthenpay payment references to a companion
Hand a companion the outcome. It reads the ifthenpay payment references, does the 2-operation version of the job, and stops for your click on anything that changes a record.
Open the payment reference. Check it against something else. Write the change. Move to the next one. That is the ifthenpay afternoon nobody can hand off, and a companion does the whole pass and gives you back the batch, with nothing landing on a payment reference until you approve it.
What it can do is exactly what ifthenpay exposes to an account you authorise and nothing beyond it: 2 operations, no reads and 2 writes. In practice that means it can issue a refund and create a payment reference, and work across the payment references and refunds.
The ifthenpay API stops at ifthenpay. 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 payment references come from?
In the tab.
ifthenpay exposes no read operation to a connected account, so a companion opens ifthenpay in the session you are already signed into and reads the screens you would.
The payment references are what most of this inventory is about, alongside the refunds. A companion can hold all 2 of these operations and forty open tabs in the same pass, which is how an afternoon of ifthenpay admin becomes a queue you review.
Which payment references wait for your approval?
All 2 write operations wait for you.
A companion can issue a refund and create a payment reference, and each one is staged on an approval card first: you see the payment reference, the field and the new value before it lands in ifthenpay.
Nothing in ifthenpay is sent, changed or deleted on your behalf without that click, and a rejected card leaves the payment reference exactly as it was. The gate is the same one on every surface, described at security.
- Issue Refund
- Create Payment Reference
What does the recurring payment references pass look like?
Yes.
Saved as a routine, the ifthenpay payment references 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 ifthenpay payment references 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