Webhook Events

The table below gives descriptions for each of the webhook events your application can currently subscribe to.

Account Access Consent

Webhook events that are related to the account-access-consent endpoint.

Event - Account Access ConsentDescription
AccountAccessConsent.ApprovedThe account-access-consent request has been approved by the end-user with their account servicer. Now you can request account information.
AccountAccessConsent.DataFetchedData has been refreshed from the account servicer's system and is available via the relevant Tapico API endpoint.
AccountAccessConsent.ExpiredSome account servicers have an expiry date for consents. Once expired your application will not be able to fetch data via that consent anymore. The end-user will have to re-authenticate again.

You can see the expiry date of an account-access-consent under the consent page of the Tapico Developer Portal and also as a field of the account-access-consent endpoint payload.
AccountAccessConsent.RevokedThe end user will always have the ability to revoke the consent. If this happens you will no longer have access to the user's data set. The end-user will have to give their consent again to restore access for your app.

Payment Instruction

Webhook events that are related to the payment-instruction endpoint.

Event - Payment InstructionDescription
PaymentInstruction.DispatchedThe payment-instruction has been approved by the end-user and dispatched to the account servicer for execution.
PaymentInstruction.FailedThe payment-instruction has failed.
PaymentInstruction.RejectedThe payment-instruction has been rejected by the account servicer.