Notifications

Notifications (webhooks) are asynchronous responses from Payture with the results of processed requests.

Notification methods

Notification examples

Event code: [EnginePaySuccess]
Is3DS: [False]
ForwardedTo: [NotForwarded]
Notification: [EnginePaySuccess]
MerchantContract: [Merchant]
Success: [True]
TransactionDate: [08.05.2019 15:36:27]
ErrCode: [NONE]
OrderId: [e83f0323-fca0-0f91-9db9-393523563bc5]
Amount: [12677]
MerchantId: [1]

• HTTP POST — an HTTP POST request. By default, the request is sent once. If needed, you can have Payture support configure the number of notification retry attempts and the interval between them (retries are made if a "200 OK" response is not received). The request body is a URL-encoded string containing key-value pairs separated by the "&" (ampersand) character. Keys and values are separated by the "=" (equals) character.
• Email — a message to the specified address, sent once.

Setting up notifications

When setting up test access to the payment gateway, the Merchant sends a setup request to Payture support. The request must specify the chosen notification method and the address for receiving notifications, and list the operations for which notifications must be sent. If needed, also list any additional parameters to be included in the notification.

When you switch to production, all notification method parameters are set by default to the same values as the corresponding test access parameters.

Changes to the current notification parameters are made upon a separate request from the Merchant to Payture support.

Additional security

Examples of encrypted notifications

DATA=4Rk65RLgsa7fUBoB72rz3TwrL3nHouyDQf91kK2eAPEEIp9DYqPFm0AnJh2eQBTcPVsfG9F8XzGtMu0zUuuxU%2FNxUVaxGDFw54n3kb5d%2FdnUMU2HaGeFTHGm%2F2p9JwmtTow82ZszX9e10u07a9x5xmn%2B3VXRJNttFcsiDBCuH3qdEmBYo9EhOVROjngki1aGucw0ZL3ifY4MEPbQrj0IWWcQ3LBGe2jhcaXc6iAGyKiDQZKymW0PwDvc3YAO29POzP0YB7tJtwPjIJgr%2FOSt31030P7hCtjM2XYjGPN4iy%2Fi2CV5bCw8ve01ZWP8XkPF

At the Merchant's request, to improve payment security, encryption with the AES-256-ECB algorithm can be applied to the HTTP POST notification method. In this case, the request body contains a single DATA parameter whose value is an encrypted string containing key-value pairs separated by the ";" (semicolon) character. Keys and values are separated by the "=" (equals) character.

Encryption keys are exchanged during setup and can be replaced later, at the initiative of either party.

Payture API notifications

InPay notifications

eWallet notifications

Receipt service notifications

ChargeBack notifications

Notification descriptions