Less than 0.5% of properties were unable to create payment requests. All affected customers had multicurrency enabled. The issue was caused by incorrect handling of multicurrency status checks introduced in the release.
The issue was resolved by reverting the update that introduced the faulty logic. After the rollback, payment request creation returned to normal for all affected properties.
Due to the update, payment gateway accounts data did not load correctly. This caused an error when retrieving multicurrency status, which resulted in payment requests being blocked.
The hotfix was deployed by reverting the multicurrency status changes introduced in the update. Improvements to test coverage and alerting are underway to help prevent similar issues in the future.