Your group has had this problem reported in Community since October 12, 2025.
This is a problem with CACHE or the implementation of the PAYMENT API based on what was previously reported by me and others over the life of this problem. In general the windows version does not matter and your question becomes a fishing exercise in the delay of gettiing a resolution with working with the windows platform development group. You really need to chase this. How do you know this is not an open hack in the PAYMENT API? You don't! This really should get prioritized (October 12, 2025 right?)
