Parameter | Description | Value |
---|---|---|
operation | Type of transaction | CallBack |
merchant_id | Merchant ID | |
orderReference | Operation ID in the merchant system | |
amount | Transaction amount | |
currency | Transaction currency | |
phone | Client's phone number (If phone input is enabled on the payment page) | |
createdDate | Payment date in YYYY-MM-DD HH:II:SS format | Example: 2018-12-14 12:01:26 |
cardPan | Masked PAN cards. | Example: 535277******0298 |
cardType | Card type | Visa |
fee | Operation fee | |
transactionId | Transaction ID on the PC side | |
type | Type of transaction | |
recToken | Token for recurrent payment | |
transactionStatus | Operation status | APPROVED – Successfully, |
reason | Text reason for rejection | |
reasonCode | Failed error code | |
merchantSignature | In order to confirm the validity of the data, a verification signature must be generated and transmitted in the |
HMAC_MD5 request using the merchant's private_key. | |
A string subject to |
HMAC_MD5 is generated by concatenating merchant_id, orderReference, amount,currency parameters separated by “;” (semicolon) in UTF-8 encoding. | ||
The order of the parameters when concatenating is important! |
Filter by label (Content by label) | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
|