This thread is from 2018 and it seems that this issue is still there in
Auth.net Production API endpoint. We have multiple instances of the same
issue for different clients who have been using Aith.net. Does anyone
know if this has been addressed as ...