Michael Klett
posted this on May 10, 2011 08:42 pm
One reason is that your Authorize.Net configuration might be "Requiring" certain fields that are a part of the Authorize.Net Payment Form settings. These settings actually affect API transactions as well, and all should be unchecked.




Comments
No images?
Fixed the images