Our company received the notification from Authorize.net that:
In October of this year, due to system updates, it will be possible to receive Authorize.Net IDs (Transaction ID, Batch ID, etc.) that are not in sequential order.
Currently, if you receive a Transaction ID of "1000," you could expect that the next Transaction ID would not be less than 1000. However, after the updates, it will be possible to receive a Transaction ID less than the one you previously received.
If your system has any functionality that expects Authorize.Net-generated IDs to be sequential, please update it immediately so that you will not see any disruptions to your solution.
Additionally, please make sure that your solution does not restrict any Authorize.Net ID field to 10 characters. If you are required to define a character limit when storing any of our IDs, the limit should be no less than 20 characters.
Our developer team has made necessary changes to handle the Authorize.net Transaction ID change and are ready to perform the integration testing. The developer has accoun in the sandbox environment, but in the sandbox environment, the transaction id is always zero.
Question:
1) Is the transaction ID change ready by Authorize.net for partners to test?
2) If yes then how to get valid values (other than zero)?
