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

In this Microsoft Access video tutorial, I will teach you how to verify that a credit card number has been entered in a valid format. In addition, we will check the expiration date to make sure that it is also valid and not expired.
Harlan from Williston, North Dakota (a Gold Member) asks: We do a lot of business at farmer's markets and other rural areas without great cell service. I bring my laptop and get folks' credit card numbers and enter them in manually, then process them when I get back home. Sounds old-fashioned, I know. Not much else we can do. Everyone pretty much knows everyone so I'm not worried about fraud. One of my major problems, however, is entering in credit card number or expiration dates wrong. There are three of us using the database (myself, my wife, and my son) and sure enough every week we get a handful of card numbers where we have to call the customer and ask them to verify their number for us. It's a pain. Any way you can help cut this down?
Silver Members and up get access to an Extended Cut of this video. Members will learn how to make combo boxes for the expiration month and year. The year box will only be filled with valid years. We'll make a custom format based on the card type. We'll perform an checksum using the Luhn algorithm to make sure the card number is valid.
Gold Members will learn how to encrypt the credit card number in the table so in case anyone gets access directly to the table database, all they'll see is garbage. We'll make encrypt/decrypt buttons and add a password.
SILVER MEMBERS VIDEO:
• Verify Credit Cards - ...
GOLD MEMBERS VIDEO:
• Verify Credit Cards - ...
BECOME A MEMBER:
KZbin: / @599cd
or My Site: 599cd.com/THMe...
LEARN MORE:
Assign Email: 599cd.com/Veri...
PRE-REQUISITES:
Input Mask: 599cd.com/Inpu...
Format: 599cd.com/Format
String Functions: 599cd.com/Stri...
Intro to VBA: 599cd.com/Intr...
AfterUpdate: 599cd.com/Afte...
Year End Sales Report: 599cd.com/YearEnd
BeforeUpdate: 599cd.com/Befo...
If Then: 599cd.com/IfThen
RECOMMENDED COURSE:
Data Encryption Seminar: 599cd.com/Encrypt
FREE TEMPLATE DOWNLOADS:
TechHelp Free Templates: 599cd.com/THFree
Blank Template: 599cd.com/Blank
Contact Management: 599cd.com/Cont...
Order Entry & Invoicing: 599cd.com/Invo...
More Access Templates: 599cd.com/Acce...
ADDITIONAL RESOURCES:
FREE Access Beginner Level 1: 599cd.com/Free1
$1 Access Level 2: 599cd.com/1Dollar
Donate to my Tip Jar: 599cd.com/TipJar
Get on my Mailing List: 599cd.com/YTML
Contact Me: 599cd.com/Contact
TechHelp: 599cd.com/Tech...
Consulting Help: 599cd.com/DevNet
Twitter: / learningaccess
en.wikipedia.o...
products.offic...
microsoft.com/...
KEYWORDS:
access 2016, access 2019, access 2021, access 365, microsoft access, ms access, ms access tutorial, #msaccess, #microsoftaccess, #help, #howto, #tutorial, #learn, #lesson, #training, #database, credit card verification, luhn algorithm, luhn check, validate credit card, verify credit card number, verify expiration date, validate expiration date, pci compliance, dont save cvv cvc codes, payment methods
QUESTIONS:
Please feel free to post your questions or comments below. Thanks.

[@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.

[@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!

[@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]

How can we prevent Apeend query from creating duplicate records?

[@599CD]

Index, no duplicates.

[@599CD]

599cd.com/Indexing

[@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.

[@ssdusd]

Nice i like it 👌

[@599CD]

Thanks 😊