Spendesk experienced a major incident on September 16, 2026 affecting Virtual Cards and Physical Cards and 1 more component, lasting 20d 18h. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Sep 16, 2026, 02:52 PM UTC
We are currently investigating an issue affecting merchant card tokenisation when customers try to add Spendesk cards on Amazon. Our technical team is actively working to understand the scope and identify the cause. We sincerely apologise for any disruption this may cause and will provide an update as soon as more information is available.
- investigating Sep 17, 2026, 08:09 AM UTC
Our banking team is currently in contact with our banking partner Visa to investigate the root cause of this incident. We apologise for the ongoing disruption and will provide further updates as soon as more information is available.
- investigating Sep 21, 2026, 09:56 AM UTC
We are continuing to investigate an issue affecting some EEA card payments and card storage attempts at certain online merchants. Customers may experience declined transactions where additional authentication is not requested by the merchant. We are working with our banking partners to resolve the issue, apologise for the disruption, and will share a further update as soon as more information is available.
- investigating Sep 22, 2026, 10:51 AM UTC
We are continuing to investigate an issue affecting some online card payments across multiple merchants. Transactions may be declined when the merchant does not request Strong Customer Authentication; where possible, please ask the merchant to retry using 3D Secure or use an alternative payment method. We are working with our partners to resolve the issue, apologise for the disruption, and will provide an update as soon as more information is available.
- monitoring Sep 28, 2026, 06:44 AM UTC
We have identified a potential cause of the issue affecting some online card payments. The service is currently stable, and we are closely monitoring the situation while we continue to validate the resolution. We apologise for the disruption and will provide a further update once full resolution has been confirmed.
- resolved Oct 07, 2026, 09:09 AM UTC
This incident has been resolved.