I'm having a strange issue with regards to the credit card number becoming "missing" which occurs only when 'Save Credit Card Numbers' is True and 'Accept real payments' is True for both my custom payment module and the payment settings. This issue does not exist if 'Accept real payments' is False even if 'Save Credit Card Numbers' is False.
This is best explained with an example, note that I have debug_toolbar turned on so that I can intercept redirects, which I have listed below. Note I have tested with debug_toolbar turned off, results are the same; 1) User adds items to cart 2) Redirect to /shop/cart/ 3) User click checkout 4) Searches for existing customer, selects customer * 5) Redirect to /shop/pos/shop/checkout/#tabs-existing * 6) Confirms customer details, clicks Continue Checkout * 7) Redirect to /shop/checkout/eway/ 8) Redirect to https://example.com/shop/checkout/eway/ 9) User enters card details, clicks confirm 10) Redirect to /shop/checkout/eway/confirm/ 11) User is presented with confirmation page, on the page is the last 4 digits of the credit card entered in step 9 12) User clicks Purchase Items 13) Up until this point, it makes no difference if 'Save Credit Card Numbers' is True or False. 13.1) If 'Save Credit Card Numbers' is True; 13.1.1) Redirect to /shop/checkout/eway/success/ 13.1.2) Success, thanks... 13.2) If 'Save Credit Card Numbers' is False; 13.2.1) Comes back to confirmation page with message 'Card Number required' Now, I know exactly where this error message is coming from. Its coming from a Python eWAY client that I have modified, see http://github.com/alexhayes/python-eway or specifically http://github.com/alexhayes/python-eway/blob/master/eway/validate.py#L30 However, I am quite certain that this is not the cause of the issue because in my get_standard_charge_data() for processor.py I am logging out order.credit_card.decryptedCC and its blank. Does anyone have any ideas of where I could start to look for this? I really can't be storing credit card numbers as there is no way I have the resources to meet pci compliance. I'm using Django 1.1.1, Satchmo 0.9 (updated less than a week ago) with Apache/fcgi * Background Info: For anyone who has been following previous posts about what it is that I'm trying to do with Satchmo, basically I've built a POS frontend which includes things like a dashboard for store staff etc. Most of the work is just modifying templates and redirecting views under certain conditions, for instance, the entering of contact details doesn't map the entered details against the logged in user, because the logged in user of course will be the store assistant, not the person buying the products. The customer that I'm am building this for is in the rental business and when someone purchases a product they need to perform two transactions, the first (which is mapped to the LINKED transaction) is a pre-authorization which is essentially insurance against the product not being returned. The 2nd transaction is for the actual daily hire. Note that even with this functionality turned off I still have the issues as outlined above. I have also managed to build into the dashboard the ability for a user to either complete or void a pre-authorisation so that if the item is returned then the pre-authorisation is voided however if its not returned or is damaged, the pre-auth can be completed. As this happens after the actual sale this has no bearing on the outcome above (tested). --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
