- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I'm currently trying to integrate customer profiles with our back end system. I've mostly gotten everything working, but I'd like to test the scenario where the customer profile fails validation.
Well, I've previously been told that it's impossible to force the customer profile to fail validation in sandbox. So that means the only way I have to test the system is to generate a mock response that shows a customer failing validation.
The documentation says that validation results are returned in the validationDirectResponseList key, but it doesn't give any description whatsoever of what items are in the list. I need documentation about the validationDirectResponseList, and what each item in the list means. If no documentation exists, then how am I supposed to do this?
Solved! Go to Solution.
โ07-08-2017 12:30 PM
Accepted Solutions
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi @skyhijoseph1,
My apologies; this one field is not up to the standards we've set for ourselves both in how the API works and how things are documented. Sorry you've been struggling with it.
The "validationDirectResponse" field is a response as you would get it back if you tried the validation transaction through our old AIM API. That API had the concept of "Direct Response" strings which were the delimited strings containing all of the response fields.
This string is one of those direct response strings, so the format of it is as documented in the AIM documentation (chapter 4).
If you need to change the delimiter or encapsulating character, you can do that in the Authorize.Net merchant interface. Navigate to Account -> Settings. In the section "Transaction Format Settings", subsection "Transaction Response Settings", click on "Direct Response".
Again, not the most elegant part of our interface. since the AIM interface is deprecated and we prefer people to use our new API, it's challenging to introduce a string out of the old API in the middle of the current API. If it helps any, here's a sample response string for a declined transaction:
2,1,2,This transaction has been declined.,,Y,60026409053,,,10.00,CC,auth_capture,,,,,,,,46282,,,,,,,,,,,,,,,,,,FCA9792E28B2BE42BAAC0504F94E82B4,P,2,,,,,,,,,,,XXXX1111,Visa,,,,,,,,,,,,,,,,,74263FBF0925674F4FF785E012E8140352AE241BCED519478485FB4211A9549F5F54501CC20524C74D2D4906E49C5A355E53E487D806615707F0723F5350F7F3
โ07-10-2017 12:11 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi @skyhijoseph1,
My apologies; this one field is not up to the standards we've set for ourselves both in how the API works and how things are documented. Sorry you've been struggling with it.
The "validationDirectResponse" field is a response as you would get it back if you tried the validation transaction through our old AIM API. That API had the concept of "Direct Response" strings which were the delimited strings containing all of the response fields.
This string is one of those direct response strings, so the format of it is as documented in the AIM documentation (chapter 4).
If you need to change the delimiter or encapsulating character, you can do that in the Authorize.Net merchant interface. Navigate to Account -> Settings. In the section "Transaction Format Settings", subsection "Transaction Response Settings", click on "Direct Response".
Again, not the most elegant part of our interface. since the AIM interface is deprecated and we prefer people to use our new API, it's challenging to introduce a string out of the old API in the middle of the current API. If it helps any, here's a sample response string for a declined transaction:
2,1,2,This transaction has been declined.,,Y,60026409053,,,10.00,CC,auth_capture,,,,,,,,46282,,,,,,,,,,,,,,,,,,FCA9792E28B2BE42BAAC0504F94E82B4,P,2,,,,,,,,,,,XXXX1111,Visa,,,,,,,,,,,,,,,,,74263FBF0925674F4FF785E012E8140352AE241BCED519478485FB4211A9549F5F54501CC20524C74D2D4906E49C5A355E53E487D806615707F0723F5350F7F3
โ07-10-2017 12:11 PM

