List of dodgy credit card numbers
#1
Hello,
Can anyone point me in the direction of a list of dodgy credit card numbers, like 4242424242424.
I need this to build a deny list for a web application. I know about the validation checksum but want to add the common workrounds.
I am moving to a propper on-line solution (Datacash) but need this in the interim
Can you help me.
Can anyone point me in the direction of a list of dodgy credit card numbers, like 4242424242424.
I need this to build a deny list for a web application. I know about the validation checksum but want to add the common workrounds.
I am moving to a propper on-line solution (Datacash) but need this in the interim
Can you help me.
#2
chiark
This is only a VERY tempoary solution, we had a real-time on-line system but it kept going wrong so we are moving to Datacash. Its just that our acquirer needs us to re- apply for status just to move the gateway. Re-applying takes 21 days !!!!!
We are doing it off-line at the moment and want to stop people typing in the test numbers as it wastes our time.
I will ask our acquirer but I am not that hopefull.
Can you point me in the direction of the new SET regulations as I sould make sure I know them.
Thanks,
Dave
This is only a VERY tempoary solution, we had a real-time on-line system but it kept going wrong so we are moving to Datacash. Its just that our acquirer needs us to re- apply for status just to move the gateway. Re-applying takes 21 days !!!!!
We are doing it off-line at the moment and want to stop people typing in the test numbers as it wastes our time.
I will ask our acquirer but I am not that hopefull.
Can you point me in the direction of the new SET regulations as I sould make sure I know them.
Thanks,
Dave
#4
GT: your acquirer should be able to provide you a list of valid BINs.
All your transactions *should* be authorised in real time, which should mitigate this.
You should also be building SET support into your site. There's a liability shift coming in June 2001 to move liability to the non-set enabled party if the other supports SET...
All your transactions *should* be authorised in real time, which should mitigate this.
You should also be building SET support into your site. There's a liability shift coming in June 2001 to move liability to the non-set enabled party if the other supports SET...
Thread
Thread Starter
Forum
Replies
Last Post