Mews experienced a minor incident on February 12, 2026 affecting Mews Payments, lasting 4h 54m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Feb 12, 2026, 02:30 PM UTC
We're investigating the issue.
- investigating Feb 12, 2026, 03:58 PM UTC
We have identified the cause and are in the process of fixing it. We will update again once we have confirmation of a fix.
- monitoring Feb 12, 2026, 05:24 PM UTC
Deployment with the reverted changes has been deployed to production. Waiting for confirmation that the issue is resolved.
- resolved Feb 12, 2026, 07:25 PM UTC
The issue has been resolved. Payment requests should be working as expected. Thank you for your patience.
- postmortem Feb 18, 2026, 09:04 AM UTC
### Overview 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. ### Action 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. ### Causes 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. ### Solution 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.