Overview
Consent events notify your application when a user’s consent status changes. These events cover the full consent lifecycle — from approval through expiration or revocation. All consent events haveeventType: "CONSENT" and differ by eventStatus.
Consent Lifecycle
Events
CONSENT_APPROVED
CONSENT_APPROVED
Sent when a user approves a consent request. This is typically the trigger to initiate an FI Request to fetch the user’s financial data.
Basic Payload (Type 1)
Extended Payload (Type 2)
CONSENT_REJECTED
CONSENT_REJECTED
Sent when a user rejects a consent request. The
consentId may be empty or <NULL> since no consent artifact was created.Basic Payload (Type 1)
Extended Payload (Type 2)
When a consent is rejected,
consentId will be empty or <NULL>. Use the consentHandle to correlate this event with the original consent request.CONSENT_PAUSED
CONSENT_PAUSED
CONSENT_RESUMED
CONSENT_RESUMED
CONSENT_REVOKED
CONSENT_REVOKED
Integration Guidance
| Event | Recommended Action |
|---|---|
CONSENT_APPROVED | Trigger an FI Request to begin data fetch |
CONSENT_REJECTED | Update UI to inform the user; optionally retry consent request |
CONSENT_PAUSED | Suspend any scheduled data fetches for this consent |
CONSENT_RESUMED | Resume scheduled data fetches; trigger a new FI Request if needed |
CONSENT_REVOKED | Stop all data operations; clean up stored data per retention policies |
CONSENT_EXPIRED | Stop all data operations; prompt user to create a new consent request if ongoing access is needed |
