Start off with some basics here:
1) This software is an authorize.net certified solution
2) The software works on everyone's site
3) But not this one.
The site in question gets a response back, but the elements are not in the correct order. As such, the software does not know how to process the response. Example: the transaction type "auth_capture" should be returned in position 12. Instead, it is in position 35. How is the software supposed to guess where the correct elements are??
Below, please see the raw pipe-separated string and also a numbered layout with the order of elements.
Any help you can provide would be wonderful; it seems insane that one of dozens of customers would get the wrong information back. AIM ref guide: http://www.authorize.net/support/AIM_guide.pdf
|3|||2|||33|||Description is required.||||||P|||0|||||||||11.84|||CC|||auth_capture||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||1AF41A8E114224FF1A5C15E5F09FFCEE|||||||||||||||||||||||||||||||||||||||XXXX1111|||Visa|||||||||||||||||||||||||||||||||||||||||||||||||
---
Solved! Go to Solution.
01-27-2012 05:18 PM - edited 01-27-2012 05:20 PM
http://developer.authorize.net/faqs/#diffdelim
If both the delim character and the encap character are set to pipe, every field will be separated by 3 pipes instead of 1, leading to field padding. This will produce the results you're seeing.
01-28-2012 05:15 AM
Look like the x_encap_char is set as a pipe'|' either in code
or in the merchant account(since you say it working on other site, this is probably it)
Account - Settings - Transaction Format Settings - Transaction Response Settings - Direct Response
01-27-2012 06:05 PM - edited 01-27-2012 06:06 PM
Yes, pipe is the separator. But what does that have to do with the order of the elements in the array? The element order is the problem here.
01-28-2012 02:38 AM
http://developer.authorize.net/faqs/#diffdelim
If both the delim character and the encap character are set to pipe, every field will be separated by 3 pipes instead of 1, leading to field padding. This will produce the results you're seeing.
01-28-2012 05:15 AM
Oh, I see... the "encap" character. Gotcha... perfect sense. I missed that or misunderstood that in your previous post.
I will have the merchant check this.
01-28-2012 08:04 AM - edited 01-28-2012 08:06 AM