Parry gathers the evidence, writes the rebuttal, and asks you only for the decisions that matter. Nothing is submitted without your approval.
Paystack tells Parry the moment a customer disputes a payment. Every message is signature-checked.
Parry builds the checklist, scores your case, and flags what is missing.
Review the drafted rebuttal in chat. Nothing is sent or accepted without you.
Parry helps merchants defend payment chargebacks. When a customer disputes a Paystack payment, Parry opens a case with its deadline, lists the evidence you have and what is missing, scores how strong the case is, and drafts a rebuttal from approved evidence. You make the decisions.
Each piece of evidence has a weight. The score is the total weight of the evidence you have approved. A packet needs at least 60% before it can be submitted.
No. Submitting a packet pauses for your explicit approval, and that rule lives in the action itself, not only in the chat. Claims without approved evidence are left out of the packet.
Not yet. Submitting prepares the packet and locks the case inside Parry, and you then answer the dispute in your Paystack dashboard. A direct send is being built, and it will show you exactly what it would send before anything leaves Parry.
No. The demo opens with sample disputes. Paystack’s test mode cannot create real disputes, so the Send a test dispute button inside Parry creates a simulated one, and the activity log labels it as simulated.
You paste your secret key once. It is stored encrypted and never shown again, and Parry uses it to check that incoming dispute messages really come from Paystack. A Paystack secret key is powerful, so please use your test key while Parry is this young. You can replace the key any time, and rolling it in your Paystack dashboard cuts off access.
Other Parry accounts cannot see them. Each account’s disputes are private to it. The person running Parry can technically reach the database to operate the service, which is one more reason to use test mode for now.
The chat agent runs on the Builder.io Agent-Native platform. You connect a free Builder.io account once, inside the chat. The Disputes screens work without it.
Email verification and password reset need an email service, which isn’t set up yet, so don’t reuse an important password. There are no Terms or Privacy pages yet. Parry is an early project built for the Builder.io Agent-Native hackathon.