March 18, 2010 at 7:30 pm
Comments posted to this topic are about the item Credit Card Number Validation Escalar Function
March 24, 2010 at 2:38 am
This does make the assumption that the Credit Card number is unencrypted (If stored in the Database) and as the PCI/DSS regulations strictly forbids this, I would be very careful about the use of using any form of un-encrypted credit cards. This will cause you major headaches with PCI DSS - also in practice Credit Card encryption has to be performed to the Payment Card Industry standard (so you can't generally use your own encryption methods)
Reference: Requirements 3 and 4 of the PCI DSS version 1.2
https://www.pcisecuritystandards.org/security_standards/pci_dss.shtml
The Standards document as a PDF: https://www.pcisecuritystandards.org/security_standards/download.html?id=pci_dss_v1-2.pdf
March 24, 2010 at 2:42 am
Hi Thor,
Give some examples
Output is not coming!.....
Only 0 returns what ever the credit card no. given it returns only 0 not 1.
One more Query, Why u are asking for 16 digit no. for credit card. Ther are many cards with 12 digit no.
Try Try Try Again,
One Day u vl succeed..................
March 24, 2010 at 6:46 am
this works for everything but american express ... in any case my impression was that PCI DSS allows encrypted storage untill it is processed, once processed you must purge it asap.
March 24, 2010 at 7:14 am
I was really expecting to see a set-based approach to this formula.
May 19, 2016 at 7:21 am
Thanks for the script.
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply