Transaction with available balance notification

Solaris API service notifies the client about debit and credit transactions of consumer’s account. The latest notification contains all the details of all the transactions that happened after posting of the preceding notification.

Transaction with available balance notification parameters

Parameters	Type	Description
NotificationType	string	Three-digit identifier of the notification type. "056" denotes the Transaction with available balance notification.
TransactionID	integer	Unique identifier of the transaction.
LocalTransactionDate	string	The local date and time of the card transaction in `yyyyMMddHHmmss` format.
Description	string	The description that describes the nature, type or purpose of transaction.
TransactionType	string	Lookup value that identifies the type of transaction.
ClientReferenceNumber	string	Unique reference number provided by user for tracking/auditing.
TransactionAmount	integer	The transaction amount
AccountBalance	integer	Available amount
AccountNumber	string	Eight-digit account number of the consumer.
SortCode	string	Six-digit number that identifies the branch of the bank where consumer holds account.
IBAN	string	Unique, 34-alphanumeric character code that identifies banks globally. IBAN consists of country code, two-check digits, and a alpha-numeric pattern that includes the domestic bank account number, branch identifier, and potential routing information.
BIC	string	Bank Identifier Code that identifies the name, country and branch of the bank. Used for quick, accurate and automated money transfer.
IsCredit	bit	Return that this transaction is as credit for this account or debit
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 Transaction with available balance notification

Copy

Copied

{
   "NotificationType" : "056",
   "TransactionID" : "123",
   "LocalTransactionDate" : "20170602105733",
   "Description" : "abc",
   "TransactionType" : "29",
   "ClientReferenceNumber" : "Load Money: 6347595",
   "TransactionAmount" : "123",
   "AccountBalance" : "123",
   "AccountNumber" : "00123456",
   "SortCode" : "123541",
   "IBAN" : "GB35CNFV60837000000570",
   "BIC" : "CNFVGB21XXX",
   "IsCredit" : "0",
   "SecurityHash" : "2ac413a9a8e23dca860a30fc4fe94d07ab1783f22fc14c73b6e936ee5b8f786e"
}

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>&<TransactionID>&<LocalTransactionDate>&<Description>&<TransactionType>&<ClientReferenceNumber>&<TransactionAmount>&<AccountBalance>&<AccountNumber>&<SortCode>&<IBAN>&<BIC>&<IsCredit>&<webhook-security-key>

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

Copy

Copied

056&123&20170602105733&abc&29&Load Money: 6347595&123&123&00123456&123541&GB35CNFV60837000000570&CNFVGB21XXX&0&abcdefghijklmnop