What was affected
NatWest Group’s Bank of APIs identified an issue affecting payment initiation service provider, or PISP, APIs for NatWest, Royal Bank of Scotland and Ulster Bank NI. These APIs support open-banking payment journeys in which a customer authorises a bank payment from a merchant checkout or payment link.
Open Banking Limited’s downtime register records that approximately 20% of payment consents were affected between 13:30 and 22:15 GMT. Tink separately reported that 70% of users on its monitored provider connections were affected and identified increased access_denied callbacks. One percentage covers payment consents reported to the ecosystem; the other covers Tink’s monitored users. Neither is a percentage of all NatWest Group customers, and the figures should not be combined.
Verified recovery times
Open Banking Limited records the incident window as 13:30 to 22:15 GMT on 8 November. NatWest Group’s service record says NatWest recovered at 18:10 GMT, with RBS and Ulster Bank NI recovering at 22:15 GMT. The bank-owned status page marked the incident resolved at 22:46 GMT and said services had returned to normal operation.
At 00:25 GMT on 9 November, the Bank of APIs page showed NatWest, RBS and Ulster payment-consent and payment-status components operational. At 08:24 GMT, Tink also marked its provider incident resolved. Open Banking Limited later listed the incident as completed.
What this meant for UK merchants
A customer choosing Pay by Bank through a service that depended on the affected connections could be denied during bank authorisation or returned without a confirmed payment result. The reviewed sources do not show a general card-acquiring, card-network or terminal failure.
NatWest’s customer service page showed payments, debit cards, its mobile app and online banking working normally during the later checks. A narrow third-party open-banking journey can fail while the bank’s ordinary customer services remain available.
What to do with an affected payment
Treat an interrupted journey as uncertain until your provider or merchant dashboard confirms the outcome. An access_denied callback does not prove that funds left the customer’s account.
- Check whether the original payment failed, completed, reversed or remains pending before retrying.
- If it failed, offer another payment method you already support.
- If the result is unclear, avoid repeated attempts and follow your provider’s reconciliation process.
- Keep the attempt time, bank, error message and a non-sensitive transaction reference for support.
- Do not collect bank login details or card information outside your approved payment flow.
What the sources do not establish
No official root cause has been published. The access_denied symptom does not establish a security incident, customer loss or a relationship with any concurrent outage. The separate planned NatWest International and RBS International maintenance on 7 November was not this incident.
The 20% payment-consent figure and Tink’s 70% monitored-user figure use different denominators. They cannot be averaged or used to estimate the share of all NatWest Group customers affected. A provider all-clear also does not prove that every individual transaction completed.
How this page is maintained
This is the stable record for the 8 November NatWest Group open-banking payment-initiation incident. Any material correction or post-incident explanation will be added here with a dated log. The original publication date and URL will remain unchanged.
Sources and dates
Checked 9 Nov 2026, 10:20 UK time · Published 2026-11-08
Checked 9 Nov 2026, 10:20 UK time · Published 2026-11-08
Checked 9 Nov 2026, 10:20 UK time
Checked 9 Nov 2026, 10:20 UK time · Published 2026-11-08
Checked 9 Nov 2026, 18:10 UK time · Published 2026-11-09
Update log
- . Open Banking Limited’s downtime register recorded the incident as completed and reported that approximately 20% of payment consents were affected between 13:30 and 22:15 GMT. This is a different denominator from Tink’s 70% of monitored users and the figures are not combined.
- . Tink marked its NatWest Group provider incident resolved. This removes the earlier status-page lag; both the bank-owned API page and Tink now record the incident as resolved.
- . NatWest Group’s Bank of APIs showed all payment consent and payment status components operational and retained the incident as resolved. Tink’s provider page still displayed its earlier investigating notice and partial-outage labels, so this page records the bank-owned resolution and flags the provider-status lag.
- . NatWest Group marked the PISP API incident resolved. It reported an approximate 13:30 GMT start, NatWest recovery at 18:10 GMT, and RBS and Ulster Bank NI recovery at 22:15 GMT.
- . Tink reported 70% of its monitored users affected in the payment initiation flow, increased access_denied callbacks and a first observed time of 13:32 GMT.
