NewNo plan feeNo plan fee. Just 2.9% + $0.30 per card sale, and signing up is free.Try now →

Authorize.Net · Decline codes

What does Authorize.Net E00003 “An error occurred while parsing the XML request” mean?

Checked

Authorize.Net E00003, "An error occurred while parsing the XML request", means the API request body could not be parsed: a field is out of order, misspelled, has an invalid value, or the document is malformed. The card was never looked at. The fix is in the integration, by checking the request against Authorize.Net's API schema.

Type
Error (integration)
Who declined
The store's integration
Retry
Only after the request is fixed.
Shopper action
Nothing; contact the store if checkout keeps failing.
Merchant action
Have your developer validate the request against Authorize.Net's schema.

What PlatformDTC does

PlatformDTC builds its Authorize.Net requests from typed structures that follow Authorize.Net's published schema; if E00003 ever came back, the shopper would see Authorize.Net's own sentence rather than a claim that their card failed.

Why it happens

Authorize.Net validates each request against its schema; elements must appear in the documented order with valid values.

What the store can do

Ask your developer or platform provider; there is nothing to change in the Merchant Interface.

For developers

messages.message[0].code "E00003". Authorize.Net translates JSON to XML, and XML requires strict element order, so JSON requests must follow the element order in the API reference.

Frequently asked questions

Does Authorize.Net E00003 affect JSON requests too?
Yes. Authorize.Net translates JSON elements to XML, which requires strict ordering, so JSON must follow the API reference's element order.
Can a shopper cause Authorize.Net E00003?
Rarely; it means the store's integration sent a malformed request.

Sources

Related

Payments library