User Tools

Site Tools


Event Notifications - extended version

Automatic notification service

Description, message format

Before starting work with Event Notification service it is necessary to contact Mayzus Financial Services (service provider) technical support team to exchange technical data.

Merchant must prepare and provide script-page, which should automatically process notification messages received from service provider.

Merchant will be provided with the MerchantCode and Security Key, needed by Merchant to verify integrity and authenticity of received notifications.

Notification message is sent automatically by service provider via POST request to the Merchant's script-page.

Service suppose that POST request is successfully delivered to the Merchant only if script-page returns HTTP code 200 and text page, which contains “OK” text (no html/css markup tags/etc).

In all other cases service suppose notification message as undelivered and will try automatically resend it with the certain periodicity.

Service provider uses the following parameters in POST request:

Name Type Description
Data string Request Data
Signature string Request Signature

Request Data is provided in JSON format and has the following structure:

eventtarget string MerchantCode provided to Merchant earlier.
eventtype string Event type code (see paragraph 2).
eventstate string Event status code (see paragraph 3).
eventitem int Unique identifier of the item relating to the Notification request (Document ID or AccountID).
details string Additional notification details.
MerchantDocumentID string * Unique identifier of document/request supplied by Merchant in original request. optional, can be empty if original request didn't contain MerchantDocumentID.
CardNumber string * Masked card number, optional, is present in documents which contain client card data (for e.g. for eventtype CARDPROCESSINGPAYMENT, WITHDTOCARD).
CurrencyCode string * 3 character currency code of document according to ISO 4217, optional, can be empty.
Amount string *Amount of document, optional, can be empty.
DocumentID string *Identifier of MoneyPolo operation, optional, can be empty.

Signature making rule:
hash = SHA512(Data + Security Key)

Example of Notification Request:


Event Type Code values

Code Description
CARDLOAD Notification regarding Client's Card Loading Payment status
CARDPROCESSINGPAYMENT Notification regarding Client's Card Processing Payment status
CARDREQ Notification regarding Client's Card Request status
CHEQUE Notification regarding Client's Cheque status
CLIDOCS Notification regarding Client's Document status
INBANKTR Notification regarding Client's Inward bank wire status
INEMONEYPAYMENT Notification regarding Client's Inward Emoney Payment status
MT Notification regarding Client's Money Transfer status
WITHDTOCARD Notification regarding Client's Withdrawal To Card Payment status
MPCBALANCE Notification regarding MoneyPolo Card Balance Value

Event Status Code values

Code Description
ACTIVATIONREQ Activation of card was requested
ACTIVE Card is active
ADD Item was added
ATTEN Item needs attention from Merchant's side
CANCEL Item was canceled
CHANGE Item was changed
CLOSED Card is closed
CLOSEREQ Close of card was requested
CONFIRM Item was confirmed
DOCACCEPT Document was accepted
DOCREJECT Document was rejected
DONE Item (processing) is done
DONEEXPRESS Item (processing) is done in manual mode
DONESWIFT Item (processing) is done in Automatic mode
ERROR Error while processing item
EXPIREDID ID document is about to expire on date, that is provided in details parameter
EXPIREDPOA Proof of Address document is about to expire on date, that is provided in details parameter
FEECHARGED Fee is charged by MoneyPolo
INPROCESS Item processing is not finished
NEW New item
PAID Item was payed
PAIDOUT Item has been paid out to recipient
PAIDRETURN Returned item was paid back
REFUND Item was Refunded
REJECT Item was Rejected
RETURN Item was returned
SENT Card was sent to Client
STORNED Item has been Storned
UNAVBALANCE Unavailable account balance to process item

It should be taken into account that parameter 'eventstate' have different meaning in case of different Notification Types. For example, for type MT (money transfer) value DONE means that transfer was paid-out to the receiver, whereas for type PAYMENT value DONE means that payment is sent.

Generally, value CHANGE means that some changes have been made with the item relating to the Notification Message.

Service provider is able to add new notification types upon the agreement with Merchant.

eventnotificationextended.txt · Last modified: 2019/02/21 14:02 (external edit)