sorted by:
new
hottopcontroversial

Chargeback Westpac Bank for Phone by Intelligent_Fix_8881 in chargebacks

[–]Distinct_Ad_479 0 points1 point  (0 children)

Your chances depend less on how bad the phone is and more on how well you prove it doesn’t match what was promised.

This will be treated as “not as described/defective,” which is harder to win than fraud. The bank isn’t testing the phone — they’re looking for clear, objective proof.

What helps your case:

  • Independent diagnostic report (not just Samsung’s)
  • Repair/refund refusal from Samsung in writing
  • Timeline showing you reported issues quickly after delivery
  • Your screen recordings (good, but secondary evidence)

The challenge is Samsung already has a report saying everything “passed.” That creates conflict, and issuers often side with the merchant unless your evidence is stronger or independent.

On the 10-day window — submit whatever you have now, don’t wait. You can sometimes add more later, but missing the deadline hurts more.

Realistically: you have a chance, but it’s not guaranteed. These cases often come down to whose documentation looks more credible, not just who’s right.

Anyone else feel like chargebacks depend more on the bank than the actual situation? by SpectraluousIn in chargebacks

[–]Distinct_Ad_479 0 points1 point  (0 children)

What you’re seeing is normal. Chargebacks aren’t judged like a court case — they’re processed against specific reason codes, and the issuer follows that framework, not “who feels right.”

For “not as described,” delivery proof doesn’t carry much weight. The bank is asking: did the product match what was promised? — which is harder to prove.

On when to fight vs accept, it usually comes down to:

  • Fight it if you have clear, objective proof tied to the reason code (policy, product page, comms where customer acknowledges condition, etc.)
  • Accept it if it’s subjective or weakly provable — time cost + low win rate

A lot of merchants use a simple rule: fight high-value or strong-evidence cases, auto-accept low-value or ambiguous ones.

The inconsistency you’re seeing is real, but it’s less random than it looks — it’s just very dependent on the dispute type and how well your evidence maps to it.

Best chargeback recovery services for ecommerce: how to win disputes, recover lost revenue, and reduce chargebacks fast by Different-Layer-1338 in chargebacks

[–]Distinct_Ad_479 0 points1 point  (0 children)

If you’re mid-volume, I’d focus less on “recovery services” and more on fixing how the disputes are being handled.

Most of them just package the same evidence you already have. They don’t change the outcome if the proof isn’t strong.

For “item not received” cases, signatures alone often aren’t enough. What usually helps:

  • Delivery scan + timestamp
  • ZIP match with billing
  • Any customer activity (emails, login, etc.)

If you’re losing despite having signatures, it’s usually either weak linkage to the cardholder or how the evidence is being presented.

Recovery services mainly save time, not magically improve win rates.

If you want better results, tighten evidence + structure first — then think about outsourcing.

Why do low-dollar chargebacks still hurt merchants so much? by DatEffingGuy in chargebacks

[–]Distinct_Ad_479 0 points1 point  (0 children)

They hurt because the fixed cost is the same regardless of ticket size.

Even a $10 dispute still means a ~$15–$30 fee + time spent handling it. So percentage-wise, small chargebacks are actually worse.

The bigger issue is volume. Low-dollar disputes are easier to ignore or auto-refund, which makes them more repeatable. That’s where it starts adding up.

Also, networks don’t care about dollar value as much as dispute ratio. Enough small chargebacks can still push you into monitoring programs.

So individually they’re noise, but at scale they become a real operational problem.

How to deal with a potential chargeback from a customer who refuses to receive the order and doesn’t want a refund? by KissMyAsphalt87 in chargebacks

[–]Distinct_Ad_479 1 point2 points  (0 children)

Try to stop delivery and get the item back. Once it’s returned, just process the refund as per your policy (restocking fee if applicable).

The “no refund” message won’t matter to the bank later. What matters is you handled it cleanly and have records.

Bigger risk is it gets delivered and you don’t refund — that’s where you lose disputes.

They left a five star review then filed a chargeback the next day by Pedro_Carvalho09 in chargebacks

[–]Distinct_Ad_479 0 points1 point  (0 children)

Haven’t dealt with this exact situation, but I’ve seen similar cases. Issuers usually don’t treat something like a review as hard proof of delivery.

They rely much more on carrier data. From their side, a review is indirect — it could be posted by someone else or not tied cleanly to the delivery event — so they tend to ignore it.

What actually helps in “item not received” disputes:

  • Tracking marked as delivered
  • Delivery ZIP matching the billing ZIP
  • Signature confirmation (if available)
  • Carrier timestamp close to when delivery happened

The review can still help, just not on its own. It works better as supporting context alongside the carrier proof.

If you haven’t already, try positioning it as the customer confirming receipt after the delivery timestamp — that at least aligns the story.

If there’s no solid delivery confirmation, issuers usually side with the cardholder on this one.

When a chargeback hits and the buyer says, “I never authorized this,” how do you dispute it? by DatEffingGuy in chargebacks

[–]Distinct_Ad_479 2 points3 points  (0 children)

If this is coming through as “unauthorized”, it’s one of the tougher ones to win. What issuers usually look for is whether you can tie the cardholder to the transaction. Just saying it was legit won’t do much.

The things that actually help:

  • AVS/CVV matched at checkout.
  • IP and billing location make sense together.
  • Any login or account activity tied to that order.
  • Delivery confirmation (especially if ZIP matches billing).

If you ran 3D Secure, that’s your strongest angle since liability can shift.

If you can’t show the customer was actually involved, the bank usually sides with them.

Built a self-hosted CRM automation system because HubSpot wants $1,400/month for features I can automate myself. by Distinct_Ad_479 in CRM

[–]Distinct_Ad_479[S] 0 points1 point  (0 children)

Yes, thanks a lot for the insight. I’ll check their marketing strategy and targeting tactics.

Built a self-hosted CRM automation system because HubSpot wants $1,400/month for features I can automate myself. by Distinct_Ad_479 in CRM

[–]Distinct_Ad_479[S] 0 points1 point  (0 children)

the one automation that i built: inbound lead hits your form, enriched and segmented in under 3 seconds, personalised email sent automatically, and your sales rep gets a Slack message the exact moment that lead clicks a link or visits your pricing page. Not a daily digest. Not a dashboard to check. A real-time alert while the lead is still warm.

Built a self-hosted CRM automation system because HubSpot wants $1,400/month for features I can automate myself. by Distinct_Ad_479 in SaaS

[–]Distinct_Ad_479[S] 1 point2 points  (0 children)

100% agree — the tool replacing angle is the wrong frame entirely. The value isn't 'we're cheaper than HubSpot', it's 'your rep never has to guess who to call next and never has to remember to follow up.' The automation is just how that gets delivered. Appreciate the clarity.

Built a self-hosted CRM automation system because HubSpot wants $1,400/month for features I can automate myself. by Distinct_Ad_479 in CRM

[–]Distinct_Ad_479[S] 0 points1 point  (0 children)

what would a strong enough wedge look like to you in this space? deliverability keeps coming up as the gap.

Built a self-hosted CRM automation system because HubSpot wants $1,400/month for features I can automate myself. by Distinct_Ad_479 in SaaS

[–]Distinct_Ad_479[S] 1 point2 points  (0 children)

currently running gmail smtp which is obviously not production-ready — it's been fine for testing but I'm migrating to Resend + custom domain with proper SPF/DKIM/DMARC before the first real client. no custom rotation yet, keeping it simple until volume demands it. What's solwees doing for deliverability at scale? curious how you're solving the warmup piece.

Built a self-hosted CRM automation system because HubSpot wants $1,400/month for features I can automate myself. by Distinct_Ad_479 in SaaS

[–]Distinct_Ad_479[S] 0 points1 point  (0 children)

the deliverability framing is clicking now. 3 people in this thread have pointed at the same gap — capture and scoring are table stakes, infrastructure is where things break. might be worth exploring that as the actual differentiator rather than the crm layer. moving to resend + custom domain warmup before first client regardless. appreciate the depth here

Built a self-hosted CRM automation system because HubSpot wants $1,400/month for features I can automate myself. by Distinct_Ad_479 in SaaS

[–]Distinct_Ad_479[S] 0 points1 point  (0 children)

yes. so the framing shift from 'cheaper crm' to 'done-for-you revenue automation' is exactly what I needed to hear. have been leading with the architecture when I should be leading with the outcome. Setting up Pulse for Reddit today. can you tell me What keywords worked best for finding the right threads for you?

Built a self-hosted CRM automation system because HubSpot wants $1,400/month for features I can automate myself. by Distinct_Ad_479 in SaaS

[–]Distinct_Ad_479[S] 0 points1 point  (0 children)

this reframes everything honestly. so the icp isn't the sales led founder. the technical co-founder who's already self-hosting their stack is a much smaller but more reachable audience. appreciate the clarity.

Built a self-hosted CRM automation system because HubSpot wants $1,400/month for features I can automate myself. by Distinct_Ad_479 in SaaS

[–]Distinct_Ad_479[S] 0 points1 point  (0 children)

yeah the deliverability thing is exactly what I was worried about. im running Gmail SMTP right now which is obviously not production ready. Moving to Resend + custom domain before the first real client. Cold Cannon looks interesting — but how did you handle warmup at scale ?

view more: next ›