SCA: Webhooks for proxy action scope consent changes
Platforms can now take advantage of webhooks to know if a User gave or revoked their consent to the platform taking actions on their behalf under proxy:
SCA_CONTACT_INFORMATION_UPDATE_CONSENT_GIVEN
SCA_CONTACT_INFORMATION_UPDATE_CONSENT_REVOKED
SCA_TRANSFER_CONSENT_GIVEN
SCA_TRANSFER_CONSENT_REVOKED
SCA_RECIPIENT_REGISTRATION_CONSENT_GIVEN
SCA_RECIPIENT_REGISTRATION_CONSENT_REVOKED
SCA_VIEW_ACCOUNT_INFORMATION_CONSENT_GIVEN
SCA_VIEW_ACCOUNT_INFORMATION_CONSENT_REVOKED
These webhooks are triggered by the User changing their consent and completing the SCA session to authenticate the change.Read more about these event types→
SCA: Webhooks for email and phone number verification
Platforms can now take advantage of webhooks to know if a User’s email or phone number factor was enrolled successfully:
SCA_EMAIL_VERIFIED
SCA_PHONE_NUMBER_VERIFIED
These webhooks are triggered when the data is added (enrollment) or changed (during re-enrollment) and the User completes the SCA session to validate the change. Note that the user can’t update their email from the hosted SCA session.Read more about these event types→