credit card # checker ???

This WebDNA talk-list message is from

2004


It keeps the original formatting.
numero = 58370
interpreted = N
texte = One of my clients does their credit card processing 'semi-manually'... that is they want to accept all orders when they are submitted and they want to stash the order in the database. But they do not charge the credit card until sometime later and then then do it through their CC payment gateway by cutting and pasting the CC number from one (WebDNA) screen to another (the CC Gateway screen)... Once in a while, they have an instance where the CC number that the person enters is not a valid number. We're not talking about a valid number that is declined.... we're talking about the number itself not being valid. I know that there is a mathematical way to inspect the entered CC number and tell whether it's valid or not... and I even wrote a webDNA routine to do just that. However every once in a while my routine reports an invalid number when it's really a valid number. Does anyone have their own routing that I can use instead of my broken one? Thanks, ~joe ------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://webdna.smithmicro.com/ Associated Messages, from the most recent to the oldest:

    
  1. Re: credit card # checker ??? ( Jesse Proudman 2004)
  2. Re: credit card # checker ??? ( Donovan Brooke 2004)
  3. credit card # checker ??? ( Joe D'Andrea 2004)
One of my clients does their credit card processing 'semi-manually'... that is they want to accept all orders when they are submitted and they want to stash the order in the database. But they do not charge the credit card until sometime later and then then do it through their CC payment gateway by cutting and pasting the CC number from one (WebDNA) screen to another (the CC Gateway screen)... Once in a while, they have an instance where the CC number that the person enters is not a valid number. We're not talking about a valid number that is declined.... we're talking about the number itself not being valid. I know that there is a mathematical way to inspect the entered CC number and tell whether it's valid or not... and I even wrote a webDNA routine to do just that. However every once in a while my routine reports an invalid number when it's really a valid number. Does anyone have their own routing that I can use instead of my broken one? Thanks, ~joe ------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://webdna.smithmicro.com/ Joe D'Andrea

DOWNLOAD WEBDNA NOW!

Top Articles:

Talk List

The WebDNA community talk-list is the best place to get some help: several hundred extremely proficient programmers with an excellent knowledge of WebDNA and an excellent spirit will deliver all the tips and tricks you can imagine...

Related Readings:

Createfolder OSX WC3.08 (2001) Images (2000) Images in the page without using separate image files ... (2003) Unauthorized User trouble (1998) This list needs a digest: rant, rave... (1997) Opinion: [input] should be called [output] ... (1997) WebCat Refrence problem (2000) Creating main- and sub-category search (1997) [WebDNA] Case-insensitive URLs (2011) Database Connectivity (1999) WebCat2 beta 11 - new prefs ... (1997) RE: path hierarchy notation (1998) WC2.0 Memory Requirements (1997) [group] ? (1997) Base64 encryption limitations? (1999) [fullPath] bug? (1998) Problem with Setheader (2001) WebCat2final1 crashes (1997) tracking variables across a site... (2000) Date fun with MySQL (2004)