You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am using PHP SDK "authorizenet/authorizenet", version 2.0. Today I received error "E00013 Extra Options is invalid" when I went to charge a card "create a transaction API". I found out the issue was that I had an ampersand in the PO # even though the documents states that the poNumber field is a JSON string. The solution or work-around is to escape the ampersand character.
A few questions:
why would a JSON-encapsulated string field cause this error?
Are there any other string fields that would need escaping?
The "E00013 Extra Options is invalid" is misleading and not accurate.
The text was updated successfully, but these errors were encountered:
I am using PHP SDK "authorizenet/authorizenet", version 2.0. Today I received error "E00013 Extra Options is invalid" when I went to charge a card "create a transaction API". I found out the issue was that I had an ampersand in the PO # even though the documents states that the poNumber field is a JSON string. The solution or work-around is to escape the ampersand character.
A few questions:
The text was updated successfully, but these errors were encountered: