Posted: April 5, 2014 at 8:57 am
|
I’m running in to an error and need to know if an adjustment can solve our issue. When testing transactions I’m getting an error that basically says that our authorize.net account is looking for physical swipe types of transactions. I’ve spoken with the support folks at authorize.net and they say that currently our account is looking for “card present” types of transactions, as opposed to web transactions. They mentioned that adjusting this “x_market_type” would be a potential solution instead of having to create an entire different account for these transactions, so before we go looking for a different processor for this stuff I wanted to see if there is something that can be done in Event Espresso to adjust this value so that we can use it for our website? I’ve searched the source code of our plugin but didn’t see anything matching the “x_market_type” value. |
|
Here is the link they directed me to during our conversation: https://support.authorize.net/authkb/index?page=content&id=A597 |
|
hello? |
Hi Rob, The API from AIM that Event Espresso uses doesn’t set “x_market_type”, but you can try adding fields to what gets sent. For example if you’re using the AIM gateway, you can open up gateways/aim/aim_ipn.php and add try adding the following after line 50: $transaction->market_type = '2'; You might also need to add “market_type” to the list of fields validated by the API since the AIM API class that Event Espresso uses doesn’t include market_type. This is set in AuthorizeNetAIM.php starting on line 82 which is located in /gateways/aim/lib/shared/AuthorizeNetAIM.php. |
|
|
Are you guys using the “Card present” integration? I’m assuming not. |
|
And is this safe? |
|
Just to update – I’ve added:
to line 51 in aim_ipn.php and added “market_type” to the array starting on line 82 in AuthorizeNetAIM.php. and I’m still running in to the same error. |
Hi Rob, Event Espresso uses the Advanced Integration Method (AIM) and can also use the Server Integration Method (SIM). Did Authorize.net give you documentation that says that either of the above integrations can be modified to be used with x_market_type or a Card Present account? |
|
|
I showed them what you mentioned and they didn’t have any issues with it. They didn’t comment on the code, but I added it anyway to test, and it’s not working. |
Hi Rob, There are some additional troubleshooting steps in this guide: http://support.authorize.net/authkb/index?page=content&id=A597&actp=LIST |
|
The support post ‘Authorize.net gateway problem "X_market_type" value’ is closed to new replies.
Have a question about this support post? Create a new support post in our support forums and include a link to this existing support post so we can help you.