[ic] Authorize.net problem with 5.2

Paul Jordan paul at gishnetwork.com
Tue Mar 28 13:22:59 EST 2006

> [mailto:interchange-users-bounces at icdevgroup.org] On Behalf 
> Of Bob Puff
> Sent: Tuesday, March 28, 2006 8:11 AM
> To: interchange-users at icdevgroup.org
> Subject: [ic] Authorize.net problem with 5.2
> Hey Gang,
> One of my 5.2 carts stopped working with Authorize.net 
> starting 03/15.  The logs
> show:
> NkffEDuf: - 
> [15/March/2006:23:04:43 -0500] store /c gi-bin/store/process 
> Safe: Real-time charge failed. Reason: Authorizenet error:
> This transaction cannot be accepted.. Please call in your 
> order or try again.
>  >
>  >
>  >               die errmsg(
>  >                               "Real-time charge failed. 
> Reason: %s\n",
>  >                               errmsg($Session->{cybercash_error}),
>  >                       );
>  >
>  >
> The website shows basically the same message.  We checked 
> with authorize.net, and they say nothing is wrong with the 
> account, but wanted to know what the error number was that 
> was returned.  Is there another log file that shows this 
> error number?  Has anyone else had a problem recently?
> Bob
> Relevant info from products/variable.txt:
> MV_PAYMENT_HOST secure.authorize.net    Payment
> MV_PAYMENT_PARTNER              Payment
> MV_PAYMENT_ID   (id #)      Payment
> MV_PAYMENT_MODE authorizenet    Payment
> MV_PAYMENT_SECRET       (password)    Payment

You need to post more information This just says "something did not work".

You can track the exact errors somewhere in the catroot/orders/session sub
directories. Depending on what foundation your catalog is based on, you
might have session-id files right in there, open them up and check out the
exact credit card error. If you are on a late version of Foundation, you'll
see directories named after the "transaction_id", then inside those you'll
find a session report.  You are looking for a file named NkffEDuf in your

The exact error will most likely enlighten you to what is going on.
Otherwise, did you changed a config in mid March? Is IC databsing the
orders, or is it failing correctly/completely? Is there any record of the
failed transaction in AuthorizeNet reports, in the Merchant Interface? 


More information about the interchange-users mailing list