Recent submissions

Comment · 2 years ago
can't speak to the actual service, but can confirm they have excellent bananas (not kidding)
Comment · 2 years ago
Sorry about this. Could you forward that email to me at [email protected]?
Comment · 2 years ago
Got it. We've just sent an update. Sorry for all the trouble.
Comment · 2 years ago
Just checking—have you emailed? Happy to take another look.
Comment · 2 years ago
Transaction = only successfully authorized and captured payments.
Comment · 3 years ago
Sorry about that. We're also seeing a small handful of cases like this—it seems like there is some inconsistency in how IRS agents are handling. We're working on updating this guidance. (Ross—we're replying to our email thread now. And for any other Atlas founders who have questions about this in the meantime, you can reach us at [email protected].)
Comment · 3 years ago
You can block by issuer / BIN with Stripe Radar: https://stripe.com/docs/radar/lists#default-lists.

You can also request to receive BIN per transaction if you write into support (https://support.stripe.com/contact/login). This isn't allowed by default because Stripe needs to make sure the setup and use case is secure to ensure PCI compliance.

Comment · 3 years ago
Radar is included for free in the base offering.
Comment · 3 years ago
(Edwin from Stripe here.) Worth noting this is copypasta from an older post from a month ago (https://piotrmierzejewski.com/p/card-networks-exploitation). We've fixed most of these issues since then. This type of card testing has dwindled—Radar should now be catching these types of attacks.

On the chargeback point—we hate chargebacks too and we want to limit them as much as possible (we're actually working on a few things over here that we think will help with this). The banks levy chargeback fees (in varying amounts) and an average of them show in the form of a $20 fee—it's not a Stripe-specific fee and we don't profit from chargebacks.

We've just finished company planning for the rest of the year and reducing this type of fraud is a top priority. So if you think you're seeing something similar, please email me at [email protected].

Comment · 3 years ago
"May have" because OP's HN name is "tempaccount3333", and I did ask them to email me once before, but I don't see anything—so I need them to reach out so I can identify their account and see what's going on.

There's no identifying info here (name or business) and we don't see any emails referencing this thread.

Comment · 3 years ago
(Edwin from Stripe here.) I think we _may_ have chatted? (Hard to tell with tempaccount name.) Could you email me at [email protected] and link to this thread?
Comment · 3 years ago
There are a bunch of factors—we look at your refund and chargeback rates, then your revenue and how much you have in your Stripe balance. For macro factors, the card networks may also sense an uptick in refund requests depending on the product/service you're selling.

That said, I see your email into our support team and we're taking another look at this now.

Comment · 3 years ago
yes

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton