Authorize.net and CACHE_TIMEOUT

[Julie Shum]

Hi,

I'm using Authorize.net with my site, and I've been encountering a
problem in testing where users get an error from time to time.
Sometimes credit cards go through fine and sometimes we get this
error:

"The following error was returned while trying to process your card.
Please correct and resubmit Credit card number is required. "

I saw this thread: http://groups.google.com/group/satchmo-users/browse_thread/thread/c3ab1019bc2a468b/d339c71900950472?,
so I increased CACHE_TIMEOUT in local_settings.py from 300 to 1800
seconds, but we still see this error on occasion. We're using
memcached for our store.

If I restart lighttpd and fcgi, the error goes away. Restarting
memcached doesn't seem to make a difference.

Any ideas what might be causing this? Should I increase the
CACHE_TIMEOUT? Is there another setting somewhere that I should
change?

Thanks,
Julie

[Chris Moffitt]

CACHE_TIMEOUT should be the only thing you need to change. 1800 seconds should be plenty.

If you look at the log files, do you see any info regarding the errored out transactions?

-Chris

[Julie Shum]

I just see the following (I've removed the user info):
2009-10-28 00:51:54,213 payment.authorizenet: INFO (Extra logging)
Authorize response: 3|2|33|Credit card number is required.|000000|P|0|
133||359.20|CC|auth_capture|
2009-10-28 00:51:54,215 payment.authorizenet: INFO (Extra logging)
Returning success=False, reason=2, response_text=Credit card number is
required.

which seems to indicate that Authorize.net just isn't getting the
credit card number. I'm not seeing any errors in my other server logs.

Payments are going through at the moment and I can't recreate it on
demand. It really seems to be sporadic. We're just concerned that
customers will come up against that error and give up on their
purchases.

On Oct 28, 10:36 pm, Chris Moffitt <ch...@moffitts.net> wrote:
> CACHE_TIMEOUT should be the only thing you need to change. 1800 seconds
> should be plenty.
>
> If you look at the log files, do you see any info regarding the errored out
> transactions?
>
> -Chris
>

> On Wed, Oct 28, 2009 at 9:28 PM, Julie Shum <julie.r.s...@gmail.com> wrote:
>
> > Hi,
>
> > I'm using Authorize.net with my site, and I've been encountering a
> > problem in testing where users get an error from time to time.
> > Sometimes credit cards go through fine and sometimes we get this
> > error:
>
> > "The following error was returned while trying to process your card.
> > Please correct and resubmit Credit card number is required. "
>
> > I saw this thread:

> >http://groups.google.com/group/satchmo-users/browse_thread/thread/c3a...
> > ?,

[Chris Moffitt]

It seems like the cache is expiring. It's an interesting issue and I agree one we should look at. We should probably make sure the processor doesn't return a blank cc #. If it's not there, then we should go back and require the user to re-enter. I'm sure that's preferable to a strange error message.

The other is to temporarily store the cc in the database but that has it's own issues. Sounds like something to discuss in django-bursar ;)

-Chris

[Julie Shum]

Hmm..we haven't seen the issue again in a while, but I'll keep an eye
out for it.

Thanks!

On Oct 28, 11:20 pm, Chris Moffitt <ch...@moffitts.net> wrote:
> It seems like the cache is expiring. It's an interesting issue and I agree
> one we should look at. We should probably make sure the processor doesn't
> return a blank cc #. If it's not there, then we should go back and require
> the user to re-enter. I'm sure that's preferable to a strange error message.
>
> The other is to temporarily store the cc in the database but that has it's
> own issues. Sounds like something to discuss in django-bursar ;)
>
> -Chris
>