User login block/unblock notification
Provides notification that the user's login status has been either blocked or unblocked.
User login block/unblock notification parameters
Parameters | Type | Description |
---|---|---|
NotificationType | string | Three-digit identifier of the notification type. "061" denotes the User login block/unblock notification. |
CardHolderID | integer | Unique identifier of the user. |
LoginBlockStatus | string | Denotes the status of block/unblock change. "01" - blocked "00" - unblocked |
Description | string | Description of the reason for the login block. |
SecurityHash | string | Contains the hash of the payload values and your webhook security key, to verify the origin and integrity of the notification. |
Example of login block notification
This is an example of a notification for a blocked user. The status of the user is changed from Unblocked (00) to Blocked (01).
{
"NotificationType": "061",
"CardHolderID": "55320",
"LoginBlockStatus": "01",
"Description" : "User blocked, Invalid SCA attempts",
"SecurityHash" : "fc4d41c59c366e8a3028d87a123520ac6b87aaa8a22808ba63fadbe59a89f003"
}
Validating the notification security hash
Security Hash validation
See the respective guide for more information on calculating and verifying the notification security hash.
To compute the hash of the notification payload, concatenate the payload values in the following sequence, with your webhook security key as the final item:
<NotificationType>&<CardHolderID>&<LoginBlockStatus>&<Description>&<webhook-security-key>
The payload values above and example webhook security key of abcdefghijklmnop
, will produce the following hash input:
061&55320&01&User blocked, Invalid SCA attempts&abcdefghijklmnop