https://community.developer.cybersource.com/t5/Integration-and-Testing/ClientId-idk-node-1-0-10-is-invalid/m-p/95290#M58868 <P>It appears that as of today 2026-05-29 that the Sandbox has decided that using the clientId of 'sdk-node-1.0.10' is invalid. &nbsp;This is the clientId that is hardcoded into the last release of&nbsp;<A href="https://github.com/AuthorizeNet/sdk-node" target="_blank">https://github.com/AuthorizeNet/sdk-node</A></P><P>Using the exteranlConfig param on the constructor with a custom clientId makes this error message go away.</P><P>Hopefully this doesn't impact Authorize.net production before our next release, &nbsp;if this was communicated in advance somewhere that I've missed I would love to know.</P><P>&nbsp;</P> Fri, 29 May 2026 17:53:53 GMT pmggary 2026-05-29T17:53:53Z https://community.developer.cybersource.com/t5/Integration-and-Testing/ClientId-idk-node-1-0-10-is-invalid/m-p/95290#M58868 <P>It appears that as of today 2026-05-29 that the Sandbox has decided that using the clientId of 'sdk-node-1.0.10' is invalid. &nbsp;This is the clientId that is hardcoded into the last release of&nbsp;<A href="https://github.com/AuthorizeNet/sdk-node" target="_blank">https://github.com/AuthorizeNet/sdk-node</A></P><P>Using the exteranlConfig param on the constructor with a custom clientId makes this error message go away.</P><P>Hopefully this doesn't impact Authorize.net production before our next release, &nbsp;if this was communicated in advance somewhere that I've missed I would love to know.</P><P>&nbsp;</P> Fri, 29 May 2026 17:53:53 GMT https://community.developer.cybersource.com/t5/Integration-and-Testing/ClientId-idk-node-1-0-10-is-invalid/m-p/95290#M58868 pmggary 2026-05-29T17:53:53Z