Implement a UK Open Banking (OBIE) AIS consent revocation flow covering both TPP-initiated and bank-initiated revocation
domain: banking · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Build a consent management dashboard per OBIE Customer Experience Guidelines that lets the PSU view, search, and revoke each active account-access-consent
On PSU-initiated revocation in your dashboard, call DELETE on the account-access-consent resource at the ASPSP as soon as practically possible
Separately handle bank-initiated revocation — where the PSU cancels access directly in their online banking rather than through your dashboard — by detecting failed/401-403 responses on subsequent data calls or refresh attempts rather than assuming you'll be proactively notified
On either revocation path, immediately stop further data pulls tied to that consent and apply your data-retention policy to any previously cached data
Send the PSU a written confirmation (e.g. email) of the revocation in addition to on-screen confirmation, since OBIE customer research found this the preferred experience
Log the revocation event with a timestamp and trigger source for audit and complaint-handling purposes
Known gotchas
There is no guaranteed real-time push telling the AISP when a PSU revokes consent directly at the ASPSP — build detection via failed API calls, don't assume a webhook will arrive
Failing to promptly DELETE the consent resource and halt polling after a PSU-initiated revocation is a common OBIE conformance failure
You must clearly disclose what happens to already-collected data after revocation — silently continuing to use previously fetched data is a compliance and trust issue
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?