| ▲ | codingdave 3 hours ago |
| I have no knowledge specific to Stripe or your case, but do I know that the pattern you just described - a small 1 dollar payment followed by a large payment - is the exact pattern that criminals use to test stolen credit cards numbers. My bank will automatically reject anything following that pattern, put a hold on my card, and call me to confirm whether or not I have my card. So yeah, if your business model calls for pattern matching with how stolen cards are used, that could very well be unacceptable risk to Stripe. |
|
| ▲ | matheusmoreira 44 minutes ago | parent | next [-] |
| I don't get it... I've had plenty of actual corporations test my credit card in that exact manner. PayPal for example literally turned this into second factor authentication mechanism: they charged me some random amount and demanded to know the value they charged me. Apparently this is proof that I have access to the associated bank account. |
|
| ▲ | pstuart an hour ago | parent | prev | next [-] |
| Out of idle curiosity, how might such a business such as the OP's be able to arrange payments to use Stripe without getting shut down? |
| |
| ▲ | alwa an hour ago | parent | next [-] | | Be upfront about the plan when you do the initial authorization. Stripe lets you signal a “set up a card on file” intent for this purpose, which doesn’t involve actually charging it $1. IIRC it either provides or expects you to provide user-facing language like “you’re putting this card on file with this merchant, you know they’re going to charge it in the future according to their policies, right?” https://docs.stripe.com/payments/cards/save-and-reuse https://docs.stripe.com/payments/save-and-reuse Or, like, send a fresh invoice for the $1500. But charging a sale for $1 as a way to make sure the card is good is not the way. It sure used to be the way in the low-fi days of physical terminals, but not today. Either way I imagine you might earn more benefit-of-the-doubt once you’ve established a track record of smooth transactions. | |
| ▲ | accountrequired 6 minutes ago | parent | prev | next [-] | | wild guess, but, if you can get the customer to click a fresh invoice link, maybe Stripe can analyze the browser/connection be more confident the charge is legitimate. it can then also be an interactive invoice with confirmation text message, for example. | |
| ▲ | rtpg an hour ago | parent | prev [-] | | Don't charge $1 first? API-wise you can attach a card to a customer without charging it. Maybe the $1500 thing still fails anyways but it won't look as much like fraud? Or, y'know, just send the $1500 invoice after the fact and have that involve the client put in the card details there as a first shot. You _should_ (IIRC) be able to charge + capture the card in one go. |
|
|
| ▲ | ShinyLeftPad an hour ago | parent | prev | next [-] |
| Criminals? I think AWS (or something similarly large) used to hold a dollar to make sure the card works, it's a pattern that is used |
| |
| ▲ | anonymous908213 44 minutes ago | parent [-] | | Amazon does a small precharge on all of my grocery deliveries. This pattern is universal. I suppose it's easier for "engineers" to come up with pants-on-head idiotic solutions and special-case exemptions for large partners than it is to use their noggin and implement any kind of system capable of actually working. |
|
|
| ▲ | anonymous908213 an hour ago | parent | prev [-] |
| It's also the pattern that millions of businesses use. It's like pattern matching against transactions on days that end in "y". You certainly will capture all fraudulent transactions that way, but... |