OK. You probably selected other service of Authorize.net with Card Present. It uses a protocol which implements reading data from a magnetic stripe if the merchant does not use expiration date etc. This is not the best suited protocol for eshops. Satchmo on the contrary implements recurring payments etc.
P.S.: I only googled variable names suggested by you and second time used by Satchmo. I expect that you can know more about authorize.net than I. -- Hynek On 11 bře, 08:00, Malcolm MacKinnon <[email protected]> wrote: > Thanks for replying, and yes authorize.net has so many API methods it's > difficult to know how to proceed. I forgot to mention: > > 'x_device_type':'8', #8 ==website > 'x_market_type':'2', #2 ==Retail > 'x_response_format': '1', #1== delimited response, default is > 0==XML > > I don't understand why the API 1 would require and 2 would not. In any > event, including them in my trans['configuration'] dictionary eliminated > my error message. > > > > > > > > On Sat, Mar 10, 2012 at 6:56 PM, hynekcer <[email protected]> wrote: > > It looks that you compare different API and documents for different > > authorize.net services CP/CNP [1] [2] > > The second one should be implemented in Satchmo or it looks very > > similar. (I do not know authoruze.net, can't say more.) > > Autorize.net supports now so many methods [3] that I can not guess the > > right. > > > [1]http://www.authorize.net/support/CP_guide.pdf > > [2]http://www.authorize.net/support/ARB_guide.pdf > > [3]http://developer.authorize.net/api/ > > > -- Hynek > > > On 10 bře, 23:24, Mac <[email protected]> wrote: > > > Hi, > > > > I'm relatively new at programming, and I'm not sure whether the fix > > > below is correct or not. The problem was I kept getting errors when I > > > submitted a test transaction to the authorize.net url. > > > > When I went to process a test transaction in Satchmo, I received an > > > error that said my market type was not valid for this transaction. I > > > looked at the processor.py code and found that under the function def > > > get_standard_charge_data (this is the particular function for my test > > > transaction), for the trans['configuration'] dictionary, the following > > > key:value pairs were missing: > > > > 'x_device_type':'8', > > > 'x_market_type':'2', > > > 'x_response_format': '1', > > > > Under the authorize.net API, I believe these key:value pairs are > > > required; otherwise, you'll fail the test. I'm no expert, but I think > > > we need to add these to the other functions in processor.py too. Once > > > I added them to the dictionary in the code for this particular > > > function in processor.py, I now get a response code 1, which means the > > > test transaction is approved, and all is well as far as the test is > > > concerned. > > > > My question is has anyone else experienced this problem or a similar > > > one? Can someone update authorize.net processor.py to include the > > > above key:value pairs? > > > -- > > You received this message because you are subscribed to the Google Groups > > "Satchmo users" group. > > To post to this group, send email to [email protected]. > > To unsubscribe from this group, send email to > > [email protected]. > > For more options, visit this group at > >http://groups.google.com/group/satchmo-users?hl=en. -- You received this message because you are subscribed to the Google Groups "Satchmo users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/satchmo-users?hl=en.
