Ensuring a E00040 response in CIM transactions caused by Account Updater deleting a profile
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. I need to be able to trigger this response consistently for integration test purposes. 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). How can I reliably simulate the account updater scenario listed above?