How to Verify Credit Card Numbers and Expiration Dates in Microsoft Access

[@LHPottery]

One caveat: If you store credit card numbers, you are required to certify that you comply with the Payment Card Industry Data Security Standards (PCI DSS). That means annual evaluations and can be seriously confusing and onerous. in most cases (as you note) it's better to use offline mode with a credit card processor. It'll save you a lot of headaches.

[@599CD]

Indeed!

[@katerinaz8140]

Do I need the algorithm that checks all digits and dates also? If yes, how much does it cost?

[@599CD]

That's available for the members. $5.99 / month to join. Or, you can try finding it yourself online. Just Google "Luhn algorithm." It's out there. I didn't invent it. I just show you how to implement it in Access.

[@IamChevalier]

Hi Richard, Being in the Card and Payments business for the better part of 30 yrs (with quite a few yrs in Pricing and Compliance) - DO NOT under any circumstances store the card numbers in the clear - they MUST be masked when viewing in any form. There are quite a few rules that any merchant needs to be aware of when accepting cards - the very basic is to comply with PCI. Card #'s should stored masked - even at rest - i.e. in the DB. TBH, the merchant should not store the cards - IN ANY FORM - at all, period... Once entered into the payment supplier's system - i.e. Square, paypal, Local Bank's system, etc...) the card details should be destroyed - NOT thrown away, destroyed - as in shredded, etc. Sorry to be over the top on this - but I've seen merchants get into the type of trouble that they have no concept of - including financial risk. CVV values - as you state - cannot under any circumstances be retained. The ONLY time a CVV is not required for a subsequent txn is IF the merchant is classified as a Subscription / Recurring business - otherwise, not including it in the txn violates the Scheme (Visa MasterCard AX Discover) rules. AND will subject the merchant to a very high dispute / chargeback likelihood. Be happy to provide more information related to this area - it's been my bailiwick for a very long time. Also, just so you know - AX and Diner's Club (yes, there are still Diner's Club cards out there) both begin with "3" There are no DC issued cards in the States. So, it may not be all that relevant regarding to what you are trying to do

[@599CD]

Thanks for all the input. Yes, I'd very much like to converse with you on the subject. Email me at [e-mail]. I'm going to put together a followup video - if not edit and reupload this video - and make it plainly clear that you should NOT store unencrypted numbers in an Access database. I personally encrypt numbers and store them in a very safe SQL Server database. And that's ONLY for recurring memberships.

[@599CD]

The purpose of my video initially was to show people how to VERIFY that the number was valid - not to discuss storing them, which I understand is a whole other ballgame. Most vendors should GET the number, PROCESS the transaction, and then DELETE the number completely.

[@sofieneloghmari6814]

but I can't figure out how to turn those softs into softs you know what I an

[@599CD]

I have no idea what you're talking about

[@ssdusd]

Nice i like it 👌

[@599CD]

Thanks 😊

[@ssdusd]

How can we prevent Apeend query from creating duplicate records?

[@599CD]

Index, no duplicates.

[@599CD]

599cd.com/Indexing