The customer says “It wasn’t what I ordered”, “it was defective” or “I was promised a refund”. Zevron builds the answer from your own records, files it through Braintree before the deadline, and a person checks anything unusual.
First 10 disputes free · then 15% of what we recover, you keep 85%
What Braintree’s API sends
PRODUCT_ UNSATISFACTORYCREDIT_ NOT_ PROCESSEDThe card network codes behind it
Required: don’t file without these
Strengthens the case
Argue it in this order
Your Braintree API keys.
Zevron gathers the listing snapshot and store policy from your connected tools. Each claim points to the record it came from, and a checker blocks any that doesn’t.
Categorized text evidence and exhibit files are filed by API, then the dispute is finalized with finalizeDispute.
Anything else? Email [email protected].
Braintree sends PRODUCT_UNSATISFACTORY or CREDIT_NOT_PROCESSED when the customer says “It wasn’t what I ordered”, “it was defective” or “I was promised a refund”. Zevron answers it with its not as described playbook.
Zevron reads the response due date Braintree sets on each dispute and files before it. You get one submission, so the file is complete before it goes.
The listing as it read on the order date, the policy they accepted, and the support thread showing what you offered. Required before filing: listing snapshot and store policy.
Your first 10 disputes are free. After that Zevron takes 15% of what it recovers and you keep 85%. Nothing is charged on a loss.
Your first 10 disputes are on us.
Zevron works with Braintree through its public interfaces. Braintree and its logo belong to their owners, and Zevron isn’t affiliated with or endorsed by Braintree.