Pending Authorization auto release notification
For partners utilizing a Buffer Account in their integration, this notification will be sent in cases when authorizations have been auto-released due to the relevant clearing not having been received by Solaris. This notification is for each individual released authorization and not aggregated. The duration after which authorizations will be automatically released is based upon your specific partner level configuration.
Pending authorization auto release notification parameters
Parameter Naming
This notification's parameter names contain inconsistent usage of "Authorization", "Authorised" etc.
| Parameters | Type | Description |
|---|---|---|
| NotificationType | string | Three-digit identifier of the notification type. "073" denotes the denotes the Pending authorization auto release notification. |
| CardID | integer | Unique identifier of the card. |
| TransactionID | integer | Unique identifier of the transaction. |
| AuthorizationDate | string | The date and time of the authorization in yyyyMMddHHmmss format. |
| AuthorisedAmount | integer | The amount authorized for the card transaction. |
| ReleasedAmount | integer | The pending amount that will be released back to the user account. |
| 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 Pending authorization auto release notification
{
"NotificationType": "073",
"CardID": "99543",
"TransactionID": "11218068416121",
"AuthorizationDate": "20210806124802",
"AuthorisedAmount": "310200",
"ReleasedAmount": "310200",
"SecurityHash": "b4e58552b54aa3312164954a161f4a94e0c78fad8c3ea0357b6784a179f628e2"
}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>&<CardID>&<TransactionID>&<AuthorizationDate>&<AuthorisedAmount>&<ReleasedAmount>&<webhook-security-key>The payload values above and example webhook security key of abcdefghijklmnop, will produce the following hash input:
073&99543&11218068416121&20210806124802&310200&310200&abcdefghijklmnop