Wise incident

Delayed AED payments

Critical Resolved View vendor source →

Wise experienced a critical incident on August 24, 2026 affecting 💸 Payments and 🔗 API, lasting 24d 22h. The incident has been resolved; the full update timeline is below.

Started
Aug 24, 2026, 10:05 AM UTC
Resolved
Sep 18, 2026, 08:21 AM UTC
Duration
24d 22h
Detected by Pingoru
Aug 24, 2026, 10:05 AM UTC

Affected components

💸 Payments🔗 API

Update timeline

  1. identified Aug 24, 2026, 10:05 AM UTC

    We're aware of an issue that's affecting customers sending AED. As a result, some payments may be delayed. This also affects Wise Platform partners. Our team is already working on a solution. We apologise for any inconvenience.

  2. identified Sep 02, 2026, 06:26 AM UTC

    We have identified the root cause and are working on a solution. Customers will continue to see delays impacting pending transfers. We will update you next at 16:00 CET on September 2 the latest.

  3. identified Sep 02, 2026, 11:47 AM UTC

    We are continuing to work on a solution. Customers will continue to see some delays impacting AED transfers. We will update you next at 16:00 CET on September 3 the latest.

  4. identified Sep 03, 2026, 11:11 AM UTC

    We are continuing to work on a solution. Customers will continue to see some delays impacting AED transfers. We will update you next at 16:00 CET on September 4 the latest.

  5. identified Sep 04, 2026, 01:57 PM UTC

    We are continuing to work on a solution. Customers will continue to see some delays impacting AED transfers. We will update you next at 17:00 CET on September 7 the latest.

  6. identified Sep 07, 2026, 01:57 PM UTC

    We are continuing to work on a solution. Customers will continue to see some delays impacting AED transfers. We will update you next at 17:00 CET on September 8 the latest.

  7. identified Sep 14, 2026, 02:02 PM UTC

    We are continuing to work on a solution. Customers will continue to see some delays impacting AED transfers. We will update you next at 17:00 CET on September 18 the latest.

  8. monitoring Sep 16, 2026, 09:20 AM UTC

    We have identified the issue and deployed a fix. We will continue monitoring and provide a further update on Friday.

  9. resolved Sep 18, 2026, 08:21 AM UTC

    This incident has been resolved.