Implement FDX consent receipt retrieval and structured consent revocation for a data aggregator serving multiple Financial Institutions

Steps

1. After the user grants consent, call GET /fdx/v6/consents/{consentId} to retrieve the consent receipt; store the consentId, granted scopes, expirationDate, and dataClusters for each FI connection in your data store
2. Build a consent management dashboard that renders the stored consent receipts; display the FI name, data scopes, expiry date, and a revoke button for each active consent
3. When the user revokes, call DELETE /fdx/v6/consents/{consentId} at the relevant FI with your access token; the FI must immediately invalidate the associated access and refresh tokens
4. Use the FDX Notifications endpoint (if the FI supports it) to receive push events when a consent is modified or revoked by the user directly at the FI's portal — subscribe via POST /fdx/v6/notifications/subscriptions
5. On receiving a consent-revoked notification, immediately stop all data retrieval, purge cached data per your data retention policy, and update the dashboard to reflect the revoked state
6. Implement bulk revocation for user account deletion: iterate stored consentIds per user, call DELETE for each, log each response code, and handle 404 (already revoked) gracefully without treating it as an error