Return Specific Results from Gateway

Moving this to the Authorize.Net integration module, as the core modules really have no say in this. Each module will interact with the checkout form for its own payment method. Right now this one just outputs a user-friendly message combined with the actual reason message from Auth.Net. It would probably be good to handle the messaging in a separate submit handler so it can be overridden by the site developers if required.

If that tests out as a good pattern, we can recommend it as a general pattern for payment method module development.

So I was doing some troubleshooting for a client and I realized there were a few things that have to happen for proper testing.

According to the AIM guide, testing has to happen against the test server (https://test.authorize.net/gateway/transact.dll) and the 'x_test_request' parameter has to be set. Then you can use the test credit card (4222222222222) and set the amount to the result code you would like returned.

For example, if you just want it to return the error 'Credit Card is Expired', that reason code is 8, so you would set the credit card as noted above, and the amount to $8.00.

Now, that being said, there is a bug in the commerce_authnet.module where the x_test_request parameter is incorrectly set. As it stands, the x_test_request is set to TRUE if the transaction mode is set to AUTHNET_TXN_MODE_LIVE_TEST. This however, tries to test against the live server (https://secure.authorize.net/gateway/transact.dll), not the proper test server (https://test.authorize.net/gateway/transact.dll). Therefore, we need to update the module, line 289 to:

'x_test_request' => $payment_method['settings']['txn_mode'] == AUTHNET_TXN_MODE_DEVELOPER ? 'TRUE' : 'FALSE',

I will run a patch when I get a chance, but right now I can't.

markie

Now that I think about it.. what's the point of AUTHNET_TXN_MODE_LIVE_TEST anyway?

@markie: AUTHNET_TXN_MODE_LIVE_TEST is for final testing against a live (not test) account. No payments actually get processed when x_test_request has that value. In view of that, the code you thought contains a bug in #3 seems fine.

Here's a patch that goes along with with Ryan's suggestion in #1. It creates a hook_commerce_authnet_aim_error_messages_alter() that allows you to override the messages displayed to a user when a transaction fails. The hook is passed an array of $error_messages as well as the full $response array. This patch does not fully address the feature request in this issue, but is a partial fix.

Here's an example of how to override the default messages:

function MODULENAME_commerce_authnet_aim_error_messages_alter(&$error_messages, $response){
   $error_messages[0] = 'We were unable to process your credit card';
   if ($response[3] == 'This transaction is currently under review.') {
     $error_messages[1] = 'We are need to review your transaction please contact us';
   }
}

If we're going to make the messages list alterable, I don't see any reason to force the dual error messages. May as well just loop over the array to display them. However, this code is in use for CIM transactions it seems for Card on File support, so I'm not sure the hook name is going to work. Otherwise we might just need two hooks; one for AIM and another for CIM. That's probably the best idea.

We'll also need a .api.php file to document these hooks before committing.

Forgot to add my follow-up patch that supports variable length error messages arrays.