3 ms·
Is there support for whitelisting transactions? E.g. if we are executing a charge for a known-good customer, but using acompletely new card - we'd like to supp
by eps 10y ago
Is there support for whitelisting transactions?
E.g. if we are executing a charge for a known-good customer, but using acompletely new card - we'd like to suppress all automated fraud checks and, ideally, indicate to the client's bank that this is a legit charge.
- zrail 10y agoYou can write your own rules. According to the docs you can only really inspect the current charge, you can't inspect anything about the customer[1]. The ability to look through to the attached customer object at metadata would make a great feature request. [1]: https://stripe.com/docs/radar/rules/reference https://stripe.com/docs/radar/rules/reference
- patio11 10y agoYes. We try to be smart about things. For example, if you use Subscriptions, we assume that subsequent charges of a happily paying customer are also very likely to be good and so we do not block them. Most users won't need to tweak the default behavior, but it is flexible in both directions. You can use the same rule builder interface to whitelist a transaction vis-a-vis Stripe, using boolean logic on a variety of things Stripe knows about the charge. Whether this will work for what you want to do depends a bit on the specifics of it -- we'd be happy to advise. A subtlety: Due to the way credit card payments work, customers' banks already assume that every business running a charge is representing to them "It is our good faith belief that this payment is legitimate" and so they don't expose a way to say "No, really, we're EXTRA SPECIAL sure about this one. Please give us their money." If they come to the conclusion that a payment is likely to not be authorized, they will take action to protect their customer. (Disclaimer: I work at Stripe.)