The SDK sends "clientId": "sdk-node-1.0.8" in every request (set by the SDK during execute())
Authorize.Net’s sandbox recently started rejecting this field with E00013 (“The field is invalid”) on certain transaction types (void, possibly refund)
However, they still process the underlying transaction — the transactionResponse.responseCodecomes back as '1' (approved)
The charge endpoint is unaffected (returns resultCode: 'Ok' with no complaint about clientId)
The SDK sends "clientId": "sdk-node-1.0.8" in every request (set by the SDK during execute())
Authorize.Net’s sandbox recently started rejecting this field with E00013 (“The field is invalid”) on certain transaction types (void, possibly refund)
However, they still process the underlying transaction — the transactionResponse.responseCodecomes back as '1' (approved)
The charge endpoint is unaffected (returns resultCode: 'Ok' with no complaint about clientId)