https://community.developer.cybersource.com/t5/Integration-and-Testing/Ensuring-a-E00040-response-in-CIM-transactions-caused-by-Account/m-p/63991#M37994 <P>I have a situation I want to reliably test, where the account updater process removes a payment profile from CIM due to being unable to find new updated info and returns the E00040 response when using a (now) invalid token.&nbsp; &nbsp;I need to be able to trigger this response consistently for integration test purposes.&nbsp; &nbsp;I understand that I can create a bogus vault_token to get this response back, but this is not reliable given that if I happen to choose a value that I thought was bogus, but just happens to be a valid value in the sandbox (due to randomness or whatever).&nbsp; &nbsp;How can I reliably simulate the account updater scenario listed above?</P> Thu, 02 Aug 2018 17:06:02 GMT mwhagedorn 2018-08-02T17:06:02Z https://community.developer.cybersource.com/t5/Integration-and-Testing/Ensuring-a-E00040-response-in-CIM-transactions-caused-by-Account/m-p/63991#M37994 <P>I have a situation I want to reliably test, where the account updater process removes a payment profile from CIM due to being unable to find new updated info and returns the E00040 response when using a (now) invalid token.&nbsp; &nbsp;I need to be able to trigger this response consistently for integration test purposes.&nbsp; &nbsp;I understand that I can create a bogus vault_token to get this response back, but this is not reliable given that if I happen to choose a value that I thought was bogus, but just happens to be a valid value in the sandbox (due to randomness or whatever).&nbsp; &nbsp;How can I reliably simulate the account updater scenario listed above?</P> Thu, 02 Aug 2018 17:06:02 GMT https://community.developer.cybersource.com/t5/Integration-and-Testing/Ensuring-a-E00040-response-in-CIM-transactions-caused-by-Account/m-p/63991#M37994 mwhagedorn 2018-08-02T17:06:02Z