I've had this working for months on four different development servers, but
now that I'm setting it up in production with memcached I'm seeing this:
INFO (Extra logging) Capturing payment on order #14
>
> INFO (Extra logging) Capturing payment for Order #14:
>
> INFO (Extra logging) Using test connection.
>
> INFO (Extra logging) standard charges configuration: {'x_login':
>> u'[deleted even though it's not a real account]', 'x_version': '3.1',
>> 'x_delim_char': '|', 'x_method': 'CC', 'x_type': 'AUTH_CAPTURE',
>> 'x_delim_data': 'TRUE', 'x_relay_response': 'FALSE', 'x_tran_key':
>> u'[deleted even though it's not a real account]', 'x_test_request': 'FALSE'}
>
> INFO (Extra logging) standard charges configuration: {'x_city':
>> u'Anytown', 'x_address': u'123 Any Street', 'x_country': u'US', 'x_state':
>> u'MD', 'x_first_name': u'', 'x_last_name': u'', 'x_zip': u'20817',
>> 'x_email': u'[email protected]', 'x_phone': u'1234567890'}
>
> INFO (Extra logging) standard charges transactionData: {'x_exp_date':
>> '1/2014', 'x_card_num': u'1111', 'x_amount': Decimal('205'), 'x_card_code':
>> 'REDACTED', 'x_invoice_num': '14_4_test_032813_404533'}
>
> INFO About to send a request to authorize.net:
>> https://test.authorize.net/gateway/transact.dll
>
> x_login=[deleted even though it's not a real
>> account]&x_version=3.1&x_delim_char=%7C&x_method=CC&x_type=AUTH_CAPTURE&x_delim_data=TRUE&x_relay_response=FALSE&x_tran_key=[deleted
>>
>> even though it's not a real
>> account]&x_test_request=FALSE&x_exp_date=1%2F2014&x_card_num=1111&x_amount=205&x_card_code=REDACTED&x_invoice_num=14_4_test_032813_404533&x_city=Anytown&x_address=123+Any+Street&x_country=US&x_state=MD&x_first_name=&x_last_name=&x_zip=20817&x_email=speed.rob%2Btest1038%40gmail.com&x_phone=1234567890
>
> INFO (Extra logging) Authorize response: 3|2|33|Credit card number is
>> required.||P|0|14_4_test_032813_404||205.00|CC|auth_capture|||||123 Any
>> Street|Anytown|MD|20817|US|1234567890||[email protected]||||123
>> Any
>> Street|Anytown|MD|20817|US||||||DBC10C13887CEA489BB3B54334A3569A||||||||||||||||||||||||||||||
>
>
I can successfully set and read values via the django cache API (and I've
confirmed that it's using Memcache). What's even more strange is
"x_card_num=1111", which is correct (that's the last 4 digits of the card
number). I have no idea why Authorize.net isn't getting the card number.
Can anyone shed some light on this?
--
You received this message because you are subscribed to the Google Groups
"Satchmo users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/satchmo-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
