Issue with Payments

Incident Report for Tink

Postmortem

Introduction 

On 2 February 2026, between 17:48 and 19:01 CET, Tink experienced a technical issue that affected the availability of all Payments products across all markets. During this period of the incident, end‑users were unable to successfully initiate one‑time or bulk payments. 

Root Cause Analysis 

Following a detailed investigation, it was determined that the incident was caused by an availability issue affecting a critical database table. As this table is a required dependency for multiple service flows, all flows relying on it were unable to function during the incident.  

Remediation 

Once the issue was identified, a new copy of the database table was created to minimize the total duration of unavailability of our PIS (Payment Initiation Service) and restore normal service. 

Follow-up actions 

To prevent similar issues in the future, Tink will be implementing the following actions: 

  1. Review alerting and improve monitoring of database table parameters
Posted Feb 05, 2026 - 15:22 CET

Resolved

This issue has been resolved as of 19:01 CET. We apologize for the inconvenience.
Posted Feb 02, 2026 - 19:17 CET

Investigating

We’re currently experiencing a major outage impacting Payments since 17:48 CET.

Our team is investigating the issue, and we’ll share updates here as soon as possible.
Posted Feb 02, 2026 - 18:15 CET
This incident affected: Payments.