topic Re: Authorize.net PHP API E00013 The field is invalid in Integration and Testing

Authorize.net PHP API E00013 The field is invalid

KT1984 — Sat, 30 May 2026 03:02:19 GMT

Yesterday transactions started failing while using authorize.net php API. But after looking at the logs, the transactions weren't failing at all. In fact, I get response code 1: {"code":"1","description":"This transaction has been approved."}. However, I also get: {"code":"E00013","text":"The field is invalid."} at the same time, which was triggering my fail logic. I changed my fail logic so the transaction goes through on my site but would like to know what is causing the error E00013. It gives no reference. I did a basic test that uses only a card and amount, and the error still comes through in the response. I literally checked each field and then did nothing but test card data and amount. I have no idea what to do now?? Any help would be appreciated.

Re: Authorize.net PHP API E00013 The field is invalid

WillCodeForCats — Mon, 01 Jun 2026 05:27:10 GMT

I am suddenly getting this E00013 error response too when it worked normally before. After some digging I figured out this problem appears to be caused by the PHP SDK sending a "clientId" in the request.

In file lib/net/authorize/api/controller/base/ApiOperationBase.php on line 122 calls the following:

$this->apiRequest->setClientId("sdk-php-" . \net\authorize\api\constants\ANetEnvironment::VERSION);

Since this line is added in execute() you don't have a chance to override it other than to comment out or delete that line of code.

I noticed this after comparing what the PHP SDK was generating for requests compared to the API documentation, and clientId is not listed anywhere in the request field description.

Re: Authorize.net PHP API E00013 The field is invalid

WillCodeForCats — Mon, 01 Jun 2026 06:10:07 GMT

I created an issue and PR in github as well: https://github.com/AuthorizeNet/sdk-php/issues/474

Re: Authorize.net PHP API E00013 The field is invalid

awGreY — Mon, 01 Jun 2026 15:54:12 GMT

Got the same error. Any request containing `clientId: "sdk-php-2.0.2"` is rejected with E00013. Removing the field
makes the identical request succeed.

Re: Authorize.net PHP API E00013 The field is invalid

VJAINFAW — Tue, 02 Jun 2026 10:36:10 GMT

I’m using the sample code provided in the Authorize.NET API documentation and running it against the Sandbox environment. Over the past 2–3 days, I’ve consistently been receiving the error E00013: The field is invalid.

Interestingly, the transaction itself is processed successfully at Authorize.NET — I receive the full transaction response with all expected details. However, the response.messages.resultCode always returns Error. This behavior only started recently; the same code was working correctly before.

Could you please advise what might be causing this issue? I am using C#.NET SDK.

Re: Authorize.net PHP API E00013 The field is invalid

SY — Tue, 02 Jun 2026 21:01:08 GMT

@VJAINFAW c# SDK has issue. They internal method (SetClientId()) override yours value of clientId to default value even if you set it manually. Default value contains dots and API returns this error if clientId contains dots.

Re: Authorize.net PHP API E00013 The field is invalid

SY — Wed, 03 Jun 2026 07:17:37 GMT

var request = new createTransactionRequest
{
    transactionRequest = transactionRequest,
    clientId = "clientid" //will be overridden
};
var controller = new createTransactionController(request); // here is overriding process
request.clientId = "clientid"; //should work
controller.Execute();

Re: Authorize.net PHP API E00013 The field is invalid

zpcohen — Wed, 03 Jun 2026 16:25:50 GMT

We're running into the same issue with the .NET SDK and bypassing the clientID fixes the issue.

Does Authorize.NET moderate this forum? Has anyone received a response from Authorize.NET directly?

Re: Authorize.net PHP API E00013 The field is invalid

jcamacho14 — Wed, 03 Jun 2026 23:19:58 GMT

Thanks! The API Live Console was working, so I was focused on our environment and your post help me identify the issue. I can confirm the same error/solution applies for the Java SDK.

var controller = new CreateTransactionController(apiRequest); // clientId is set in here apiRequest.setClientId("overriden"); controller.execute();

Overriding the client id after the controller is created solved the issue for me

Re: Authorize.net PHP API E00013 The field is invalid

kishanpatel — Thu, 04 Jun 2026 07:13:00 GMT

I'm also facing the same issue on the Authorize.net Sandbox environment:

Error:
E00013 - The field is invalid.

As a temporary workaround, I commented out the following line:

$this->apiRequest->setClientId("sdk-php-" . \net\authorize\api\constants\ANetEnvironment::VERSION);

File:

vendor/authorizenet/authorizenet/lib/net/authorize/api/controller/base/ApiOperationBase.php

After commenting out this line, the requests started working again in the Sandbox environment.

However, I'm not sure whether the same issue exists in the Production environment. If anyone has already verified this, please let me know.

Also, I'm looking for a proper solution instead of modifying files under the vendor directory.

Current package version:

"authorizenet/authorizenet": "~1.9.6"

Has anyone encountered this issue recently, or found a recommended fix/updated package version from Authorize.net?

Re: Authorize.net PHP API E00013 The field is invalid

kishanpatel — Thu, 04 Jun 2026 07:17:47 GMT

I'm also facing the same issue on the Authorize.net Sandbox environment:

Error:
E00013 - The field is invalid.

As a temporary workaround, I commented out the following line:

$this->apiRequest->setClientId("sdk-php-" . \net\authorize\api\constants\ANetEnvironment::VERSION);

File:

vendor/authorizenet/authorizenet/lib/net/authorize/api/controller/base/ApiOperationBase.php

After commenting out this line, the requests started working again in the Sandbox environment.

However, I'm not sure whether the same issue exists in the Production environment. If anyone has already verified this, please let me know.

Also, I'm looking for a proper solution instead of modifying files under the vendor directory.

Current package version:

"authorizenet/authorizenet": "~1.9.6"

Has anyone encountered this issue recently, or found a recommended fix/updated package version from Authorize.net?

Re: Authorize.net PHP API E00013 The field is invalid

pamahesh — Thu, 04 Jun 2026 16:13:22 GMT

Hi — this was due to a temporary platform issue, not your integration.

You were correctly seeing:

response code 1 → transaction approved
E00013 → incorrectly returned alongside it

The issue has now been resolved by the Authorize.Net team.

View incident details

Re: Authorize.net PHP API E00013 The field is invalid

muhammadammar23 — Wed, 10 Jun 2026 07:04:07 GMT

If you're receiving Response Code 1 ("This transaction has been approved"), then the payment itself is succeeding. The E00013 ("The field is invalid") message is likely coming from another part of the API request or response processing.

A few things to check:

Make sure you're using the latest Authorize.net PHP SDK.
Review the full API response, especially the messages and errors sections, to identify which field is triggering E00013.
Check whether any optional fields (customer profile, line items, invoice number, merchant-defined fields, etc.) are being sent automatically by your code.
Verify that you're not sending empty strings or invalid values in optional fields.
If this started suddenly, check whether Authorize.net recently changed validation rules or if a specific API endpoint is affected.
Since even your minimal test (card + amount) returns E00013, it may be worth comparing the raw request/response payloads with a known-working transaction or contacting Authorize.net support with the transaction ID and full response details. The approval code suggests the transaction is processing correctly, but some non-critical field is failing validation.

Re: Authorize.net PHP API E00013 The field is invalid

hunzafatimaa — Wed, 10 Jun 2026 12:40:59 GMT

If the transaction returns Response Code 1 (Approved), the payment is successful. E00013 usually means an invalid or unsupported field elsewhere in the request. Check your full API request/response, update the PHP SDK, and review any optional fields being sent. If the issue started recently, it may be related to an API validation change.