Current status
Tink’s UK provider status page says the Chase payment incident was resolved at 23:47 GMT on 16 November. The outage was first posted at 04:47 GMT on 14 November, giving a 67-hour incident window in Tink’s public log.
Tink now lists Chase operational. It has not published a root cause, affected merchant count, transaction value or explanation of which endpoint failed.
Verified scope
During the incident, Tink reported all payments on its monitored Chase component affected. That figure described one provider-specific connection. It did not describe every Chase payment, card or customer.
At the 01:25 GMT check on 17 November, Chase UK’s own status page showed all listed services operational, including sending money out, using a card and Using Third Party Providers. Chase did not post a matching open-banking incident for 14–16 November.
What UK merchants should do now
If a Chase Pay by Bank attempt failed or returned without a clear result during the incident, reconcile it before asking the customer to pay again. A failed browser screen or callback does not prove whether a payment was created.
- Check the order record, payment-provider dashboard, API response and webhook history for the original payment reference.
- Confirm whether the attempt is failed, pending, completed or reversed before retrying or taking another payment.
- Keep the attempt time, amount, provider reference and non-sensitive error message for reconciliation or support.
- Check settlement and refunds against the same reference so a delayed status update does not create a duplicate charge or refund.
- Do not ask for the customer’s bank login, card security code or one-time passcode, and do not collect payment details outside the approved flow.
Do not combine separate Chase incidents
Chase completed planned maintenance at 05:13 GMT on 14 November, shortly after Tink posted its incident. Chase later reported a separate card-processing problem from 19:00 to 20:28 GMT that evening.
The published records do not connect the maintenance, card incident or Tink payment-initiation outage. No reviewed source identifies a common cause, cyber incident or security breach.
What the evidence does not establish
There is no public figure for affected merchants, customers or transaction value. Tink’s component figure is not a measure of all Chase payments. Tink has not published a root cause or said whether every payment attempt failed for the full 67-hour window.
Merchants using another open-banking provider should use that provider’s status and their own payment records. An incident on Tink’s route does not establish that every Pay by Bank provider was affected.
How this page is maintained
This is the stable record for the Tink-to-Chase payment-initiation incident first posted on 14 November 2026 and resolved on 16 November. Any material correction or official explanation will be added here with a dated log. The original publication date and URL remain unchanged.
Sources and dates
Checked 17 Nov 2026, 01:25 UK time · Published 2026-11-14
Checked 17 Nov 2026, 01:25 UK time
Checked 17 Nov 2026, 01:25 UK time · Published 2026-11-14
Checked 17 Nov 2026, 01:25 UK time · Published 2026-11-14
Update log
- . Tink lists Chase operational. Its incident log says the payment outage was resolved at 23:47 GMT on 16 November, 67 hours after the first post. Chase continues to show all listed services operational.
- . Tink still labels its Chase component a major outage and the incident remains investigating. Chase’s own status page shows all listed services, including Using Third Party Providers, operational. These status pages cover different scopes.
- . Tink posted “Chase payments - Major outage” and said all payments on its monitored Chase component were affected. The notice gives no root cause, affected merchant count or recovery estimate.
