Authorize.Net Authorization Code / Transaction ID

[rpb3]

I have a store that does not do their own payment capturing. Currently we pass the payment info to a fulfillment house and they authorize and capture the payment against the card.

We'd like to change that so we can do the authorization at checkout but still allow the fulfillment house to capture the payment. I have two thoughts on that.

One, we might be able to pass the Authorize.Net Transaction ID to the fulfillment house and then they can settle the transaction and it is truly one transaction.

Or I can go back and void our initial transaction when I pass the info to the fulfillment house and they can still do their own authorize and capture. By voiding the initial auth transaction I will avoid double encumbering the card for the amount of the transaction.

Either way, I need the Transaction ID from the Authorize.Net authorization at check out. I see on the admin page for the payments there is field named Transaction ID and Authorization value in the notes area. Mine are all zeros, I assume that is because our gateway is in test mode.

Does anyone know if once we go live with the gateway if AbleCommerce actually stores the Authorize.Net transaction ID and if so where? I assume it is somewhere in the ac_Transactions table but since I don't have live data to see I can't tell.

Any guidance or direction would be appreciated.
Rick

[nickc]

By voiding the initial auth transaction I will avoid double encumbering the card for the amount of the transaction.

That's not always the case. Last time I checked on this, there was limited support for an Auth Void transaction. Check with authorize.net to be sure.

To be clear - this is the fulfiller's merchant account, not yours, that the original auth happens with?

[rpb3]

I talked to our Authorize.NET rep and he thinks the void will work. We are doing live orders now and the store does retain the 6 digit authorization code, I'll just have to figure out how to do the void. It would be nice to use the built in iPaymentProvider interface but I may have to use the code from Auth.net's developer center.

The deal with the merchant account is kind of strange, it is some kind of umbrella account the fulfillment house has for the store. We did get it to work after some configuration issues were corrected.

I'll try to remember to post my results of the transaction void implementation. I guess further down the road it would be nice if we could pass the transaction to the fulfillment house for capture but they can't accept that at this time.