Live / Spendesk / Incident
Spendesk: Amazon Payments – Card Tokenisation Failure
Spendesk · spendesk.comMajor incidentResolved2026-10-07 09:09 UTC
Public — what happened
Summary
Spendesk reported a major problem starting on 16 September 2026 at 14:52 UTC in which customers could not save their Spendesk cards on Amazon. Over the following days the company widened the scope, saying some online card payments in the EEA and at several merchants were being declined when the merchant did not ask for extra authentication, and it suggested retrying with 3D Secure or paying another way while it worked with its banking partners, including Visa. On 28 September Spendesk said it had found a likely cause and that service was stable, and the incident was marked resolved on 7 October 2026.
Affected
Virtual Cards, Physical Cards, Subscription Cards
Timeline
- Started — 2026-09-16 14:52 UTC
- Investigating — 2026-09-16 14:52 UTC (4 updates)
- Monitoring — 2026-09-28 06:44 UTC
- Resolved — 2026-10-07 09:09 UTC · 21 days after it started
With SquidGrid — where it starts on the route
Independent path health
The status page is the symptom. SquidGrid measures the paths that reach Spendesk against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.
🔒 Sign in to seeCustomers get the live Provider Assessment Report for Spendesk: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the Spendesk report →
More from Spendesk
Covered in The Squid’s Ink, Week 39, 2026, our weekly internet health report.