Payment Status Displays "Captured" or "Authorized"

[SkylineTech]

We have some orders where the payment status is set to "Captured" or "Authorized" versus being set to "Paid". We are using Authorize.net and have done no customization to the payment processes.

The payment process that the end user claims to have followed the same process to capture the funds on these orders as those that are in a status of "Paid".

The funds have settled properly in Authorize.net.

Anyone have any ideas on what I'm missing.

Thanks!

[WebDev7]

From my experience, sometimes it takes a couple of days for Authorize.net to post back as Paid.

Which version of ABLE are you running?
Inside of the Payment details for that order (Order Admin) , is it marked PAID?

[page8workaholic]

I know this is an old post, but we are experiencing the same issue. We are also using Authorize.net and I have one order that's payment was captured on 5/12/2011 (today being 6/17/2011) that is still showing CAPTURED as the payment status. We are using AbleCommerce 7.0.6 build 14312.

[AbleMods]

In the old days, this was caused by a rounding issue. Able looks for the balance of the order to be exactly 0.00 - if it's not, the status doesn't shift to Paid like it should.

If your are altering the math of the order with any customizations or a percentage is being applied, it's possible something is getting carried out to 3 or 4 decimals instead of rounding at 2. Again this was an issue in old AC7 versions but it's been fixed for a long time.

Best way to check is to look at the data in SQL table. See if any of the dollar amounts for the line items or on the ac_Order record itself carry out beyond 2 decimals. If they do, that's your culprit. Be sure to check ac_Payments as well.

I've run Authorize.Net for over 3 years on multiple sites. The longest I've seen it take to post a payment was around 3 seconds. I've never seen it miss one. Unlike PayPal that misses entirely every 6-8 orders. You won't find a more rock solid payment gateway than Authorize.Net.