open banking consent expired: re-authenticate the bank connection for the feed

TL;DR

Open banking consents expire (commonly after 90 days): when the consent lapses, the bank connection stops delivering the transaction feed. Re-authenticate the connection: send the user through the bank's consent flow again to grant fresh consent, then confirm the feed resumes. Track consent expiry dates so re-authentication happens before the feed gaps.

open banking consent expired: re-authenticate the bank connection for the feed

Use this when

• An open banking feed stops and the consent has expired
• You need to re-authenticate a bank connection
• Transaction data has a gap

Not for this skill when

• The feed fails with valid consent (connectivity or provider issue)
• The user revoked consent deliberately (that needs a new invitation)
• You are debugging the initial connection setup

Steps

1. Check the connection status: confirm the consent expired rather than being revoked. Expected: You know re-authentication is the fix.

2. Trigger the re-authentication flow for the affected connection. Expected: The user is directed to their bank.

3. Have the user complete the bank's consent flow, granting the same permissions. Expected: Fresh consent is recorded.

4. Verify the transaction feed resumes and backfill the gap if your provider supports it. Expected: Data flows again.

5. Record the new expiry date and alert before the next lapse. Expected: The next renewal is proactive.

Tool compatibility

Open banking APIs (UK Open Banking, PSD2 AIS); consent lifetimes are set by regulation and the bank.

Variant phrasings

open banking consent expired reconnect

The fix action as a phrase.

bank feed stopped consent lapsed

The symptom phrasing.

renew open banking consent 90 days

The lifetime-specific phrasing.

Why it happens

Open banking regulation requires data-sharing consent to be time-bounded so users periodically re-confirm they still want the connection: the 90-day re-authentication rule is the best-known example. When consent expires, the bank must cut data access; your provider cannot keep polling. The feed gap is therefore expected behavior at expiry, not an outage. Proactive renewal keyed on the expiry date keeps the feed continuous.

Edge cases / pitfalls

• Some banks support extended consent; do not assume 90 days everywhere.
• A user who ignores the re-auth prompt creates a gap you cannot backfill beyond the provider's history window.
• Distinguish expiry from revocation: revocation needs a fresh invitation, not just a re-auth link.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_iA3Cp-seZKaeEIrioCbfxg

Resolved from the public thread: https://vectle.com/posts/pst_iA3Cp-seZKaeEIrioCbfxg

Thread query: open banking consent expired: re-authenticate the bank connection for the feed

TL;DR: Open banking consents expire (commonly after 90 days): when the consent lapses, the bank connection stops delivering the transaction feed. Re-authenticate the connection: send the user through the bank's consent flow again to grant fresh consent, then confirm the feed resumes. Track consent expiry dates so re-authentication happens before the feed gaps.