What's "booking"? I read elsewhere that tripactions does something like this, with virtual CCs. Maybe all the booking services do that. It makes sense, because

What's "booking"? I read elsewhere that tripactions does something like this, with virtual CCs. Maybe all the booking services do that. It makes sense, because small hotels aren't going to have some kind of API where the booking agent can actually reserve the room, and they also aren't going to be able to give you the customer's actual CC safely. So from Stripe POV, they aren't identifying or able to identify all these cards as being produced by the booking agent as part of their normal modus operandi. To them, it's just a high number of prepaid cards that trips up their fraud sensor. It just feels like it is what it is to me. I'm not sure why the post on the orange site, nor why it made it to the front page. Why didn't you use your existing processor, rather than Stripe? Presumably your existing processor has seen lots of real cards from you and you are an established customer, so the mix of real + the agent's virtual would be fine for them? Whereas Stripe was just seeing 100% prepaid cards. I don't quite understand if you are actually out of pocket any money? Why wouldn't the booking agent be able to cut you a check at this point, if the Stripe charges were all reversed?