Skip to content

Stop sending client ID to avoid E00013 errors#218

Open
karl-loebach wants to merge 1 commit into
AuthorizeNet:masterfrom
karl-loebach:fix/remove-clientid-e00013
Open

Stop sending client ID to avoid E00013 errors#218
karl-loebach wants to merge 1 commit into
AuthorizeNet:masterfrom
karl-loebach:fix/remove-clientid-e00013

Conversation

@karl-loebach
Copy link
Copy Markdown

The SDK injected an undocumented clientId (sdk-java-<version>) onto every request via the controller constructor. The Authorize.Net API now rejects requests containing this field with E00013 "The field is invalid."

Removing the setClientId() call leaves the field null so JAXB omits it from the serialized request. Mirrors the sdk-php fix in AuthorizeNet/sdk-php#475 (fixes AuthorizeNet/sdk-php#474).

The SDK injected an undocumented `clientId` (`sdk-java-<version>`) onto every request via the
controller constructor. The Authorize.Net API now rejects requests containing this field with
`E00013 "The field is invalid."`

Removing the `setClientId()` call leaves the field null so JAXB omits it from the serialized
request. Mirrors the sdk-php fix in AuthorizeNet/sdk-php#475 (fixes AuthorizeNet/sdk-php#474).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

Sending clientId causes E00013 "The field is invalid."

1 participant