Open Banking Consent Reconfirmed
open_banking.consent.reconfirmed
This event triggers when a consent is successfully reconfirmed.
Event Message
The table below describes the structure of the event.
Field | Description | Values |
---|---|---|
event | The event this webhook relates too. | open_banking.consent.reconfirmed |
consent_id | The consent this event relates too. | |
customer_id | The customer this consent relates too | |
provider | The provider this consent is associated with | |
updated_at | The date time that the event occurred |
Examples
{
"data": {
"consent_id": "ab32780a-3d60-4d4d-984f-11ea3ef329cd",
"customer_id": "99e911e9-d084-4790-9911-52fdf482fe95",
"provider": "Natwest",
"updated_at": "2023-10-02T14:05:55Z",
"event": "open_banking.consent.reconfirmed"
}
}
How and when this event is triggered
This event triggers when an Open Banking consent been successfully reconfirmed.
Legend
Icon | Description |
---|---|
Behaviour depend on the configuration of the original gateway URL. For example, reconfirm_consent_redirect |
User Reconfirms Consent Through BUD Connect
The diagram below describes the reconfirm flow through Bud Connect and when in the flow this webhook is triggered.
Consent Is Reconfirm Using The API
The diagram below describes how the webhook is trigger when using the Reconfirm Consent endpoint.
Updated 16 days ago