(no title)
smca_ | 3 years ago
We don’t typically comment in detail on individual cases, but we do think it’s important for onlookers to know that we take every single case like this seriously. It looks like what happened here was an edge case involving SEPA payments that resulted in a dispute rate that’s far in excess of what’s generally permitted by financial partners. When we do this, our interventions are partly to protect financial partners/Stripe, partly to protect end customers, and in part to protect the businesses themselves. (For example, Visa will fine businesses that maintain high dispute rates.) This case is actually a bit more complicated still, since you said that you’re using Connect. In these cases, we also take seriously the importance of defending the platform (i.e. you) against users who are trying to defraud you.
More broadly, we work hard to balance the rules of the financial ecosystem, ease of use, protection against fraudulent businesses, consumer protection, and continuity for businesses. We support millions of businesses across dozens of countries and payment methods, and we discover new scenarios every day. We plan to blog about our work here in more detail before too long (including some of our key metrics). If any HNers have suggestions as to what we should include, feel free to reply here. We’ll try to share anything helpful that’s not too sensitive.
nottorp|3 years ago
This is all fine when your clients have 1 million sales per month. But in this case they have umm... "To put this into context, we are talking about a small local gym, with 33 active memberships."
You need a better metric than 0.1% or 1% or just turn down small clients? They're just disproportionate support costs anyway so they shouldn't be allowed to run a business online :)
Brian_K_White|3 years ago
gommm|3 years ago
Maybe the issue is a fraud system designed for cards that's not well thought out for other forms of payments.
nerder92|3 years ago
This can also happen due to insufficient funds, or as it happens if the mandate you (Stripe) send them is wrong. We previously have an issue with this exact same account where the reason for the disputes was an incorrect mandate and we were refunded for those.
Xylakant|3 years ago
unknown|3 years ago
[deleted]
joering2|3 years ago
BOA implements First Data gateway by default these days, so most likely your previous processor is utilizing same solution as well, so less work to switch.
joshxyz|3 years ago
unknown|3 years ago
[deleted]