Cybersource Developer Community Cybersource Developer Community

It turns out that the account had a secondary address field with a `%` in it... Soon as that was removed, it went through ok.

I am pointing to secure2 and am experiencing the same issue. Authorize support has no other info and suggested I come here. In troubleshooting, I am logging bothserialize(curl_getinfo($curl))and$response When I test with my personal account, everythi...