Payment fails, null value in request.Payment.Order.User

[bsweeney]

Two weeks ago we had a CC payment that failed. The return code from our processor (Paymentech) was "Do Not Honor (05)" with a CVV of "No Match." We currently process all orders on the admin side. The staff member entering the order did not realize the card was rejected and fulfilled the order, changing the status in the process.

We went back to try and process the payment again today and it is failing without ever reaching the stage of communicating with Paymentech (I was able to confirm this because I currently have the gateway debug mode turned on). The payment page displays the following error: Value cannot be null. Parameter name: request.Payment.Order.User

Looking in the app.log I see the following related message:

Code: Select all

ERROR 2010-05-13 11:33:46,453 1392562ms Object                 a                  - Provider threw exception in DoAuthorize.
System.ArgumentNullException: Value cannot be null.
Parameter name: request.Payment.Order.User
   at CommerceBuilder.Payments.Providers.PaymentechOrbital.PaymentechOrbital.DoAuthorize(AuthorizeTransactionRequest authorizeRequest)
   at CommerceBuilder.Payments.PaymentEngine.a(AuthorizeTransactionRequest A_0, Boolean A_1)

We tried both to retry authorization and to enter a new payment, both of which had the same result. In the end we canceled the old order and created a new one so that we could process the payment (which went through without a hitch). I'd like to avoid this problem in the future, anyone have any ideas of what happened?

[bsweeney]

One other thing that may be pertinent. The order number and order ID were out of sync. Usually not a big deal, but due to an issue with which info is passed between AbleCommerce and Paymentech I updated the order number so that it matched the order ID. It was after this that the error occurred.

We haven't had any issues with new orders. Perhaps this problem only affects orders that occurred prior to the order number update.

[mazhar]

I made any entry for this one in our logs. Although I didn't tried to reproduce it locally. You can track progress here.
http://bugs.ablecommerce.com/show_bug.cgi?id=8910

[jmestep]

I just got the error on a site, but I don't think it was a bug in this case. We had a site using the old Paymentech dll where it passed the orderid instead of the ordernumber to Paymentech for about a week. Then we installed the patch that fixed the dll to send the ordernumber and they are no longer able to capture the order from the admin for the orders during the problem week. In order to try to tweak it, I changed one of the ordernumbers in an order to the orderid and tried the capture. Then I got this error message, so the tweak didn't work, but I don't think it is a bug in this case.

[bsweeney]

Sorry to resurrect this old post, but I'm still encountering this problem. I think the point of failure in AbleCommerce is after the credit card authorization failure. We only seem to be experiencing this problem on orders where the payment gateway rejects an order. I wonder if the gateway setting have anything to do with the problem. We're currently set to "Authorize and Capture" instead of just "Authorize (recommended)".

Or perhaps the following bug is related to our issue (we currently process order administratively so it's rare that an account is created):
http://bugs.ablecommerce.com/show_bug.cgi?id=8976

We're currently still on 7.0.4, but I'm planning to upgrade to 7.0.6 soon. Should I go the intermediate route for upgrade (7.0.4 -> 7.0.5 -> 7.0.6) or is it OK to go directly to 7.0.6?

[mazhar]

We're currently still on 7.0.4, but I'm planning to upgrade to 7.0.6 soon. Should I go the intermediate route for upgrade (7.0.4 -> 7.0.5 -> 7.0.6) or is it OK to go directly to 7.0.6?

Read this topic
http://help.ablecommerce.com/upgrades/a ... _tasks.htm

[bsweeney]

The update to 7.0.6 addressed my issue. I believe bug 8976 was related to the problem I was encountering. Would it make sense for you to update bug 8910 so that it indicates the issue is related to bug 8976?

[mazhar]

The update to 7.0.6 addressed my issue. I believe bug 8976 was related to the problem I was encountering. Would it make sense for you to update bug 8910 so that it indicates the issue is related to bug 8976?

Thanks for confirmation. I just updated that 8910 is related to 8976.