Re: Problem with CC problem ?

This WebDNA talk-list message is from

1997


It keeps the original formatting.
numero = 13727
interpreted = N
texte = > >What I'm wondering is if the occasional failures are due to the CC >processing network being down rather than other causes. I could easily >imagine that Sun's CC processing network would be the same as ours since >we are in relative geographic proximity. That would explain my problems >and the simultaneous problems experienced by our customer. Problem is normally the 'credit card network' are independant ie: if you go through one credit card processor most likely Sun might not be. But I do know that they all are still passing that 80bytes or so of info (including address verification if your card processor supports it, all via 300 baud, no error correcting. We were writing custom credit card processing software about 9 months ago in a company I was working for. A random small percent of the charges would get screwed because of a bad line from the phone company, you could see when we captured the text being sent by us, the ack from their side, the wait, then the info coming back from them we would get random info interjected into the stream, ie: the good old 300 baud modem days with non-error correcting modems. So unless so Massive revolution by the credit card processing companies has happend and all of their equipment has changed its all still 300 baud. (we even had to move back to a few non-error correcting 2400 baud modems because we would get stranger results using even 14.4k modems) We had this same problem with ICVerify's actual DOS based software for doing manual and batch processing of cards not related to instant processing, we had to use a 2400 baud modem non-error correcting. I am not saying this is the cause, or a anything, but just the fact to keep in mind that funny things can happen at low, non-error correcting speeds. (also it is true that alot of credit card processing companies use Compuserve's National X.25 network (usually via 800 numbers) to get the info from you to them. Nevin Lyne Rendered Visions Associated Messages, from the most recent to the oldest:

    
  1. Problem with CC problem ? (Sven U. Grenander 1997)
  2. Re: Problem with CC problem ? (N. Lyne 1997)
> >What I'm wondering is if the occasional failures are due to the CC >processing network being down rather than other causes. I could easily >imagine that Sun's CC processing network would be the same as ours since >we are in relative geographic proximity. That would explain my problems >and the simultaneous problems experienced by our customer. Problem is normally the 'credit card network' are independant ie: if you go through one credit card processor most likely Sun might not be. But I do know that they all are still passing that 80bytes or so of info (including address verification if your card processor supports it, all via 300 baud, no error correcting. We were writing custom credit card processing software about 9 months ago in a company I was working for. A random small percent of the charges would get screwed because of a bad line from the phone company, you could see when we captured the text being sent by us, the ack from their side, the wait, then the info coming back from them we would get random info interjected into the stream, ie: the good old 300 baud modem days with non-error correcting modems. So unless so Massive revolution by the credit card processing companies has happend and all of their equipment has changed its all still 300 baud. (we even had to move back to a few non-error correcting 2400 baud modems because we would get stranger results using even 14.4k modems) We had this same problem with ICVerify's actual DOS based software for doing manual and batch processing of cards not related to instant processing, we had to use a 2400 baud modem non-error correcting. I am not saying this is the cause, or a anything, but just the fact to keep in mind that funny things can happen at low, non-error correcting speeds. (also it is true that alot of credit card processing companies use Compuserve's National X.25 network (usually via 800 numbers) to get the info from you to them. Nevin Lyne Rendered Visions N. Lyne

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:

[isfile] ? (1997) Paradata/Moneris Gateway (2005) WebCat editing, SiteGuard & SiteEdit (1997) [WebDNA] Acceleratin Search / Index Performance in a Formum Service (2013) [SearchString] problem with [search] context (1997) RE: Which [index]? (1997) [WebDNA] uploading videos (2018) No Wanna Duppys (1998) Don't know if this is a sily question... (2003) Slow applescript context ... (2000) [Webcat 2]Next (1997) Sort Order on a page search (1997) Was code to phantom spacing -- now BBEdit [!][/!] (2001) [ListFiles] context & alias (1997) [WebDNA] Replace / Append only unique data (2013) AutoCommit Preference? (1998) WebCat2 - many [carts] on one template page? (1997) practicing safe queries.. (2000) Re[2]: Shopping Cart Directory (2000) Quickie question on the email templates (1997)