Token activation notification

Token lifecycle notification

This notification is used to inform you when a token is activated. For more comprehensive token-related notifications, it is advised to subscribe instead to the Token lifecycle notification as this provides updates throughout the entire lifecycle of a token, including its creation, suspension, as well as activation. Please contact Solaris if you have any queries regarding this, or wish to subscribe to the Token lifecycle notification.

Token activation notification parameters

Notification Type

Please note this notification is identified by a two-digit value in the NotificationType field.

Parameters	Type	Description
NotificationType	string	Identifier of the notification type. "68" denotes the Token activation notification.
CardID	integer	Unique identifier of the card.
TokenID	integer	Unique identifier of the token.
CardEndingNumber	string	Last four digits of card number
TokenRequestorCode	string	Token requestor code. Possible values are: "APLPAY" "GGLPAY" "SAMPAY"
DeviceID	string	Mobile device ID.
DeviceType	string	Device type value. Possible values are: "01" – Mobile Phone "02" – Tablet "03" – Watch "04" – Mobile Phone or Tablet "05" – Personal Computer
Datetime	string	The date and time of token activation in `yyyyMMddHHmmss` format.
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 Token activation notification

Copy

Copied

{
    "NotificationType": "68",
    "CardID": "74318",
    "TokenID": "478",
    "CardEndingNumber": "5574",
    "TokenRequestorCode": "APLPAY",
    "DeviceID": "0000123",
    "DeviceType": "01",
    "DateTime": "20201105173851",
    "SecurityHash": "1edc3c6b87a495ed5afb476057f185674e92e478e0c887d5f83aeb91f0b6a41a"
}

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:

Copy

Copied

<NotificationType>&<CardID>&<TokenID>&<CardEndingNumber>&<TokenRequestorCode>&<DeviceID>&<DeviceType>&<DateTime>&<webhook-security-key>

The payload values above and example webhook security key of abcdefghijklmnop, will produce the following hash input:

Copy

Copied

68&74318&478&5574&APLPAY&0000123&01&20201105173851&abcdefghijklmnop