Re: Showif Error Generated...
This WebDNA talk-list message is from 2003
It keeps the original formatting.
numero = 46995
interpreted = N
texte = > > >I think you may be onto something here. Although I don't use [validcard], I >do have the following: > > [purchase cart=[cart]&card=visa+mc+amex&paymethod=cc... > >My guess is that using these variables within [purchase] will produce the >same effect, however it generates the following: > > Error: we do not accept that type of credit card >Each CC company has its own checksum to determine if a number is entered correctly. With millions of people entering CC numbers into machines and forms, someone is bound to make a mistake sooner or later. That's the reason for unique checksums.You're evidently telling the cc processor that you have no idea what kind of cc is being used. It could be any of those you put in the purchase cart string. I suspect, but don't know, that the last one in the string is the one the processor sees. If a customer is using Visa, the processor thinks it's Amex. The checksum for Amex won't work for Visa.You also need to be sure the processor accepts Amex. Not all do, because of their high rates. And also make sure your client can accept Amex along with the more common cards.Glenn------------------------------------------------------------- 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:
> > >I think you may be onto something here. Although I don't use [validcard], I >do have the following: > > [purchase cart=[cart]&card=visa+mc+amex&paymethod=cc... > >My guess is that using these variables within [purchase] will produce the >same effect, however it generates the following: > > Error: we do not accept that type of credit card >Each CC company has its own checksum to determine if a number is entered correctly. With millions of people entering CC numbers into machines and forms, someone is bound to make a mistake sooner or later. That's the reason for unique checksums.You're evidently telling the cc processor that you have no idea what kind of cc is being used. It could be any of those you put in the purchase cart string. I suspect, but don't know, that the last one in the string is the one the processor sees. If a customer is using Visa, the processor thinks it's Amex. The checksum for Amex won't work for Visa.You also need to be sure the processor accepts Amex. Not all do, because of their high rates. And also make sure your client can accept Amex along with the more common cards.Glenn------------------------------------------------------------- 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/
Glenn Busbin
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:
Re:1 cent answer? (1998)
PIXO support (1997)
Where is Typhoon 3.x? (2000)
RE: Languages (1997)
Help name our technology! I found it (1997)
(2003)
international time (1997)
Dumb Question about Docs (1997)
Template Security error (1997)
Calendar Snippet Problems (1998)
Verifying and adding new users (1997)
frustrated with search (2001)
[ShowNext] (1997)
TemplateCacheSize preference! (1998)
Comments in db? (1997)
searching a range -still don't get it (2000)
E-mailer error codes (1997)
Re(6): Small Bug: ErrorLog.txt/[FORMVARIABLES]/[ORDERFILE] (1998)
Re:HELP - NONE STOP DIGESTS. Digest for 4/24/97) (1997)
OT: Amazon Patents (2000)