Comments on: Tutorial: Integrating the Authorize.Net AIM API with PHP

By: dcolumbus

dcolumbus — Tue, 31 Jan 2012 21:37:28 +0000

John,

I’m running across a new issue. When submitting a credit card on a LIVE account with the credit card number of 4111111111111111, the TRY CATCH isn’t true or false, and just continues on (in my case, creates a user profile) … but once I looked at Authorize.net, I saw “General Error” for unsettled transactions.

I suppose that in this case, even though there is an error code being generated, your AIM class does not deal with this error? I’m not sure how to handle this.

By: Johnny

Johnny — Sat, 05 Nov 2011 03:45:03 +0000

For a credit transaction you should also need the last four digits of the credit card number. If you don’t have it you can get it by using the new Transaction Detail API. Just send the transaction number over and it will return everything about that transaction including the last four digits of the credit card number.

By: otakucode

otakucode — Sat, 05 Nov 2011 00:11:22 +0000

First thing, thank you a great deal for this class, it has made integration of authorize.net a breeze.

Second, I have a quick question: Is the credit card information required for processing a CREDIT transaction? Or is the x_trans_id and amount sufficient?

By: Michael

Michael — Tue, 18 Oct 2011 18:01:43 +0000

It would appear that we’re getting holds on AVS declines which means that all info (except the address) is correct. Apparently, per AUTH.NET, these appear as declined, but a hold still occurs and they’ll settle 3 days later. This makes absolutely no sense.

We’re getting back on the horn with AUTH.NET. I’ll post back what I hear.

Thanks again.

By: Johnny

Johnny — Tue, 18 Oct 2011 17:14:11 +0000

That’s kind of bizarre. Declined transactions shouldn’t hold any funds on the cardholder’s account since it was never approved. This is especially true when the card is declined for insufficient funds. You may want to speak with your merchant account provider and see if they can explain this as it is not how a merchant account is supposed to function.

By: Michael

Michael — Tue, 18 Oct 2011 17:11:55 +0000

I see. Well, the problem we’re experiencing is customers still have a hold on their credit cards (or bank accounts) for the attempted amount, despite the transaction being declined.

What is the recommended mechanism for preventing this from happening or purging/releasing these amounts?

Best.

By: Johnny

Johnny — Tue, 18 Oct 2011 17:01:04 +0000

Only transactions that have been approved can be voided. Declined transactions cannot be voided since they essentially don’t exist anymore.

By: Michael

Michael — Tue, 18 Oct 2011 16:57:05 +0000

Hi,

First of all, awesome stuff. Thanks. That said, I have a problem that’s not so much related to your code as AUTH.NET itself. Basically, I’m getting declined transactions (which is expected) that I can’t VOID. Although they are in the “UNSETTLED REGISTER” when I log in, the error message returned when I try to VOID them is “The transaction cannot be found.”

Any ideas as to what could be happening?

Best.

By: Brad

Brad — Sat, 01 Oct 2011 18:02:14 +0000

Great work john, this makes working with Authorize.net much simpler. Thanks!

By: Matt

Matt — Tue, 01 Mar 2011 02:29:47 +0000

John,

Seriously awesome code.

Good Job.