Purse incident

Secure Fields - Creditcard incident

Major Resolved View vendor source →

Purse experienced a major incident on September 29, 2026 affecting Web embedded components and Widget V3 and 1 more component, lasting 15m. The incident has been resolved; the full update timeline is below.

Started
Sep 29, 2026, 07:10 AM UTC
Resolved
Sep 29, 2026, 07:25 AM UTC
Duration
15m
Detected by Pingoru
Sep 29, 2026, 07:10 AM UTC

Affected components

Web embedded componentsWidget V3Secure FieldsHeadless SDKDropIn UI

Update timeline

  1. resolved Sep 29, 2026, 07:34 AM UTC

    Between 09:10 and 09:25 (CEST) this morning, payments made with vaulted credit cards were disrupted. During this window, some transactions using saved card details may have failed or been declined. The issue was caused by a recent deployment. Our team identified it quickly and rolled back the change at 09:25, and vaulted card payments have been operating normally since then. Payments with non-vaulted cards and other payment methods were not affected. We are investigating the root cause as a priority and will share further details once our analysis is complete. We apologize for the inconvenience this may have caused you and your customers.

  2. investigating Sep 29, 2026, 08:20 AM UTC

    Update – Clarification on impacted scope We would like to clarify the scope of this morning’s incident. Our previous message referred to “vaulted credit cards”, which may have suggested that only payments using saved card details were affected. This was inaccurate. All card payments processed through our platform rely on our card vault, whether or not the card was saved by the end customer. As a result, between 09:10 and 09:25 (CEST), card payments in general may have failed or been declined, including one-time payments with newly entered card details. Payments made with non-card payment methods were not affected. The rollback performed at 09:25 fully restored card payment processing, and all card payments have been operating normally since then. Our root cause analysis is ongoing, and we will share further details once it is complete. We apologize for the confusion caused by our earlier message and for the inconvenience to you and your customers.