|
Well... You could have a shared DB of MD5 hashed CC #'s (never store the actual CC #) along with the first 4 numbers and last 4 numbers of the card. You could count the number of merchants in the network the CC # has been used with over a certain period of time, the IP address that the CC # was used from, etc. One could then run some statistics on the CC #'s. If there was too much traffic on a single card or on card sequences, etc. you could alert the merchants and they could void the charges or issue refunds. This would also be a good "single point of contact" for enhanced verification techniques: - Debiting or crediting the account with a few pennies and getting to user to enter the amount in another web site - Calling the user on the phone and getting them to answer a simple math problem (what's 3 + 4) and recording their voice authorizing the charge - Maybe more It could be an interesting project. Any thoughts on how many different folks on this group would be willing to join a merchants group to build something like this? snacktime wrote: Like SPEWS.org, maybe it's time for a CC blacklist for the iMerchant community. |
_______________________________________________ Asterisk-Biz mailing list [email protected] http://lists.digium.com/mailman/listinfo/asterisk-biz
