Overview
A dispute (also called a chargeback) happens when a customer contacts their bank to reverse a charge. When this happens, the disputed amount plus a $20 dispute fee is deducted from your store’s available balance immediately. Most disputes never reach you. Pandabase’s fraud network blocks the majority of fraudulent transactions before they complete — and for the ones that do get through, we automatically build most of the evidence package on your behalf.How Pandabase protects you
As the merchant of record, Pandabase sits between you and the card networks. This means our fraud systems work on your behalf at every stage of the payment lifecycle.Network-level fraud blocking
Every transaction passes through Pandabase’s fraud network before it completes. The network evaluates signals across all stores on the platform — not just yours — which means patterns that would be invisible to a single merchant are caught early.- Card testing detection — rapid low-value authorization attempts from the same source are identified and blocked before a charge goes through.
- Device and behavioral fingerprinting — checkout sessions are scored based on device signals, browser behavior, and session patterns. High-risk sessions are blocked at payment time.
- Velocity checks — unusual spikes in purchases from the same card, email, or IP across any store on Pandabase trigger automatic blocks.
- Network-wide blocklists — cards and emails involved in confirmed fraud on any Pandabase store are blocked platform-wide. A fraudster who hits one store can’t move to another.
- BIN and issuer risk scoring — card ranges and issuing banks with elevated fraud rates are flagged for additional verification or declined outright.
Early fraud alerts
Even after a payment completes, card networks sometimes send early warning signals before a customer files a formal dispute. Pandabase acts on these automatically:- Low-value orders (under $20) are automatically refunded to prevent a costly dispute. You’ll receive an email notification.
- Higher-value orders are flagged for manual review so you can decide whether to refund or wait.
Automatic evidence collection
When a dispute does occur, Pandabase automatically compiles evidence from the transaction since we’re the merchant of record:- Customer name, email, and billing address
- IP address and geolocation at checkout
- Payment method details and AVS/CVV match results
- Timestamp of purchase and fulfillment
- Transaction and order identifiers
Dispute lifecycle
Dispute opened
The customer’s bank notifies us of the dispute. The order moves to CHARGEBACK status and the funds are held. You’ll receive a
PAYMENT_DISPUTED webhook and an email notification.Submit evidence
You have a limited window to submit evidence that the charge was legitimate. Pandabase attaches transaction-level evidence automatically — you provide the product usage evidence.
Dispute reasons
| Reason | Description |
|---|---|
| Fraudulent | Customer claims they didn’t authorize the charge |
| Product not received | Customer claims they didn’t receive the product |
| Product unacceptable | Customer claims the product wasn’t as described |
| Duplicate charge | Customer was charged more than once |
| Unrecognized | Customer doesn’t recognize the charge on their statement |
| General | Other or unspecified reason |
How to win a dispute
The single most important factor in winning a dispute is proving the customer received and used the product. Pandabase handles the payment-side evidence automatically — your job is to show the product was delivered and accessed.What to submit by dispute reason
Fraudulent / Unrecognized
Fraudulent / Unrecognized
The customer claims they didn’t make the purchase. This is the most common dispute type.What wins these:
- Access or activity logs showing the customer logged in, downloaded, or used the product after purchase
- IP address correlation between checkout and product access (Pandabase provides the checkout IP — you provide the access IP)
- Email correspondence where the customer discussed or acknowledged the purchase
- Screenshots showing the customer’s account activity in your product
Product not received
Product not received
The customer claims they never got what they paid for.What wins these:
- Delivery confirmation — download logs with timestamps, email delivery receipts, or license key activation records
- Screenshots of the fulfillment event (webhook delivery success, email sent confirmation)
- If the product was accessed via a URL, server logs showing the customer visited that URL after purchase
Product unacceptable
Product unacceptable
The customer claims the product wasn’t as described.What wins these:
- Your product description at the time of purchase showing accurate representation
- Evidence the product functions as described (screenshots, demo, or documentation)
- Any communication with the customer where they acknowledged the product worked or where you offered support
- Refund policy that was visible at checkout
Duplicate charge
Duplicate charge
The customer claims they were charged more than once.What wins these:
- If the charges are for separate orders, show that different products or quantities were delivered for each charge
- Order IDs and distinct fulfillment records for each transaction
- If it was genuinely a duplicate, accept the dispute — fighting a legitimate duplicate charge damages your dispute rate
General tips for strong evidence
- Submit evidence quickly. The sooner you respond, the more time the bank has to review. Don’t wait until the deadline.
- Be concise and factual. Banks review hundreds of disputes. Clear, organized evidence with timestamps and screenshots wins over long explanations.
- Show the timeline. A clear sequence — purchase, delivery, access — is the strongest evidence pattern.
- Include screenshots, not just logs. Raw server logs are harder for bank reviewers to interpret. Annotated screenshots of dashboards or activity feeds are more compelling.
- Don’t fight disputes you’ll lose. If the customer has a legitimate complaint, accepting the dispute preserves your dispute rate. A high dispute rate is more expensive than any single loss.
Preventing disputes
The best dispute is one that never happens. Most disputes are preventable with clear communication and fast fulfillment.Before the sale
- Write accurate product descriptions. Overpromising is the top cause of “product unacceptable” disputes. Show exactly what the customer will get.
- Display your refund policy clearly. Customers who know they can get a refund are less likely to go straight to their bank.
- Use a recognizable statement descriptor. “Unrecognized” disputes happen when customers don’t recognize the charge. Make sure your store name is clear on their bank statement.
After the sale
- Deliver immediately. Digital products should be fulfilled within seconds of payment. Delayed delivery is the most common trigger for “product not received” disputes.
- Send a confirmation email. A clear receipt with the product name, amount, and your store name helps customers remember the purchase.
- Log access and activity. Keep records of when customers download, activate, or use your product. This is your most valuable evidence if a dispute occurs.
- Respond to support requests fast. Many disputes start because a customer couldn’t reach the merchant. A quick reply with a refund offer is always cheaper than a $20 dispute fee plus lost funds.
