We're using Authorize.net for payment processing, and using the Authorize Only option. The initial authorization was sent out and received when an order is placed, but when the shop administrator goes in and marks the order as shipped and saves the record, there's nothing going to Authorize.net. Nothing showing in the event log after marking the order as shipped, but there is a note in the event log from the initial order, showing a post to Authorize.net, and our account at Authorize.net shows the unsettled transaction pending. What's preventing the settlement command from being sent?

Using version 2.91, the settle credit card button is available and does send the capture order to authorize.net. A few questions, though:

When the shop administrator goes to the order, and they make a change to the order that causes a change to the total and click to recalculate the total, clicking the "Settle Credit Card" button sends the original amount for capture, not the recalculated total. Clicking the "Print Invoice" or "Send Email" button appears to include a "Save" action, but looks like the "Settle Credit Card" button doesn't include that same "Save" action. Shouldn't the behavior be the same on all three? This would save the shop admin the need to save the record before settling the credit card.

Along the same lines, once I realized that the original amount had been sent, I went back to the order, saved the new total, and clicked "Settle Credit Card" again. Now there are two capture orders at authorize.net pending settlement. They each have different transaction id, but they each have the same authorization code. I'm surprised the 2nd settle order was accepted, as now there are two captures on one authorization! At the point that authorize.net settles the transaction, will these resolve themselves, and accept only the 2nd capture, assuming it's a correction of the 1st? Or have I just run the card twice?

Cheers,

Ken

1. Sure would make everything easier for the user if this weren't the case. And it would help avoid the issue of submitting the capture order twice.

2. Well, when I open up the order, change an amount, print an invoice, then click "back" without saving, and then enter the order again, the changed values held. Same thing if I send email. It definitely SEEMS like it's saving it!

3. Both captures were processed by authorize.net.

In reviewing what went to authorize.net, there were three different transactions, all with the same authorization codes, but all with different transaction ids. The first was the authorization, which was (and still is) unsettled and listed as "authorized/pending capture". The next two were the different captures, which have now gone from "captured/pending settlement" to "settled successfully". I thought there would be only one transaction, which would progress from "authorized/pending capture" to "captured/pending settlement" and finally to "settled successfully". Because now, ignoring the inadvertent re-run of the card, there's an unsettled transaction just hanging out in our account. Shouldn't it work this way???

Ken