Re: [WebDNA] [BULK] Web Merchant Authorize net issues
This WebDNA talk-list message is from 2011
It keeps the original formatting.
numero = 106496
interpreted = N
texte = Art, I have a couple accounts set up with Auth.net. You have to go into the = setup for the account and do two things: First is enable the ability for the account to accept connections from = your web server. I think it's 'webconnect' or something like that.=20 Second is to generate a set of security codes that have to be entered in = the WebDNA setups for the store. 'Generate Passcodes' or 'Generate = Security keys', I can't remember, it's been a long time since I set one = up.=20 You also have to make sure the paths to the Sandbox and other prefs are = all set correctly.=20 I use the CC-Auth Capture setting also and it works flawlessly - once = you get all the pieces in place.=20 I'll try to log in to my Auth.net account and get a better description = of the settings you have to configure to get it to work. I also had one = account where the bank did not set up the account so it COULD accept = connections from an ecommerce site, so they had to scrap that account = and set up one that could.=20 Tony Miller tmiller@thehawkeye.com On Apr 6, 2011, at 12:38 PM, Arturo Vargas wrote: > I have created a store with store builder and I am trying to setup > authorizenet with it and I am not able to get the transactions over to > authorizenet. >=20 > As a Payment Authorization Method I am using: CC-Auth Capture >=20 > I have tried these two things: >=20 > Payment Processor: AuthorizeNet - Direct Connect Method=20 > I get this as a response Text when viewing the orders: >=20 > This transaction cannot be accepted. > Hash: EF1C72BD6F66C2C5D2156D6607E1EB4B >=20 > And Status: Error > = --------------------------------------------------------------------------= -- > ----------------------------- >=20 > Payment Processor: AuthorizeNet > I get no response Text when viewing the orders >=20 > And Status: Waiting_734598.0739 >=20 > Any help would be greatly appreciated. >=20 >=20 >=20 > Art >=20 >=20 >=20 > -----Original Message----- > From: Chris Wik [mailto:chris@anu.net]=20 > Sent: Wednesday, April 06, 2011 12:41 AM > To: talk@webdna.us > Subject: Re: [WebDNA] TCP HTTP/1.1 questions >=20 > On 06.04.2011, at 05:28, Aaron Michael Kaczmarek wrote: >=20 >> I reviewed the protocol and it seems that chunked transfer-encoding = is > probably the source of this problem. I don't imagine webDNA supports > persistent connections, so a "Connection: Close" header must be = included. > I'll try this out tomorrow and let ya know what I get. >=20 >=20 > It sounds like both ends are using KeepAlive (which is assumed to be > supported by HTTP/1.1), and neither end is closing the connection = until the > keepalive timeout is reached. >=20 > Connection: close in the HTTP header informs the other end that you = will not > be sending any further requests and wish to close the HTTP connection = as > soon as the request is complete. >=20 > -- > Chris Wik > Anu Internet Services Ltd > www.cwik.ch | www.anu.net >=20 > --------------------------------------------------------- > This message is sent to you because you are subscribed to the mailing = list >
. > To unsubscribe, E-mail to: > archives: http://mail.webdna.us/list/talk@webdna.us > Bug Reporting: support@webdna.us >=20 > --------------------------------------------------------- > This message is sent to you because you are subscribed to > the mailing list . > To unsubscribe, E-mail to: > archives: http://mail.webdna.us/list/talk@webdna.us > Bug Reporting: support@webdna.us
Associated Messages, from the most recent to the oldest:
Art, I have a couple accounts set up with Auth.net. You have to go into the = setup for the account and do two things: First is enable the ability for the account to accept connections from = your web server. I think it's 'webconnect' or something like that.=20 Second is to generate a set of security codes that have to be entered in = the WebDNA setups for the store. 'Generate Passcodes' or 'Generate = Security keys', I can't remember, it's been a long time since I set one = up.=20 You also have to make sure the paths to the Sandbox and other prefs are = all set correctly.=20 I use the CC-Auth Capture setting also and it works flawlessly - once = you get all the pieces in place.=20 I'll try to log in to my Auth.net account and get a better description = of the settings you have to configure to get it to work. I also had one = account where the bank did not set up the account so it COULD accept = connections from an ecommerce site, so they had to scrap that account = and set up one that could.=20 Tony Miller tmiller@thehawkeye.com On Apr 6, 2011, at 12:38 PM, Arturo Vargas wrote: > I have created a store with store builder and I am trying to setup > authorizenet with it and I am not able to get the transactions over to > authorizenet. >=20 > As a Payment Authorization Method I am using: CC-Auth Capture >=20 > I have tried these two things: >=20 > Payment Processor: AuthorizeNet - Direct Connect Method=20 > I get this as a response Text when viewing the orders: >=20 > This transaction cannot be accepted. > Hash: EF1C72BD6F66C2C5D2156D6607E1EB4B >=20 > And Status: Error > = --------------------------------------------------------------------------= -- > ----------------------------- >=20 > Payment Processor: AuthorizeNet > I get no response Text when viewing the orders >=20 > And Status: Waiting_734598.0739 >=20 > Any help would be greatly appreciated. >=20 >=20 >=20 > Art >=20 >=20 >=20 > -----Original Message----- > From: Chris Wik [mailto:chris@anu.net]=20 > Sent: Wednesday, April 06, 2011 12:41 AM > To: talk@webdna.us > Subject: Re: [WebDNA] TCP HTTP/1.1 questions >=20 > On 06.04.2011, at 05:28, Aaron Michael Kaczmarek wrote: >=20 >> I reviewed the protocol and it seems that chunked transfer-encoding = is > probably the source of this problem. I don't imagine webDNA supports > persistent connections, so a "Connection: Close" header must be = included. > I'll try this out tomorrow and let ya know what I get. >=20 >=20 > It sounds like both ends are using KeepAlive (which is assumed to be > supported by HTTP/1.1), and neither end is closing the connection = until the > keepalive timeout is reached. >=20 > Connection: close in the HTTP header informs the other end that you = will not > be sending any further requests and wish to close the HTTP connection = as > soon as the request is complete. >=20 > -- > Chris Wik > Anu Internet Services Ltd > www.cwik.ch | www.anu.net >=20 > --------------------------------------------------------- > This message is sent to you because you are subscribed to the mailing = list > . > To unsubscribe, E-mail to: > archives: http://mail.webdna.us/list/talk@webdna.us > Bug Reporting: support@webdna.us >=20 > --------------------------------------------------------- > This message is sent to you because you are subscribed to > the mailing list . > To unsubscribe, E-mail to: > archives: http://mail.webdna.us/list/talk@webdna.us > Bug Reporting: support@webdna.us
Tony Miller
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:
How to search for fields with 10 or more characters? (2004)
PCS Frames-Default page is solution! (1997)
WCS Newbie question (1997)
IP Shows Server (2003)
Three new problems, maybe a fourth (1997)
Dashes and dots in credit card (1998)
Reloading Shopping Carts (1998)
RE:It just Does't add up!!! (1997)
WebCatalog2 Feature Feedback (1996)
Problems with webcat 2.01 for NT (1997)
Tax Troubles (2003)
[Sum] function? (1997)
RE: [WebDNA] Forum Module Made In WebDNA (2020)
Search multiple fields (1997)
[WebDNA] Searching Possible Bug (2009)
TCPconnect in a DB? (1999)
Processing all html files through WebCat or Typhoon (1998)
SMSI FTP - calander system (2002)
WebCatalog and WebMerchant reviewed by InfoWorld (1997)
Field name-subcategory (1997)