This page is describing lecacy "redierct mode" flavor of the payment_return message
This legacy mode can be switched on-off for your shop by our administrator (contact support@maksekeskus.ee)
We urge you not to use the legacy mode and use normal messages instead.
The request are either http(s) POST or GET request, as defined in the shop configuration (see in merchant portal Test / Live)

All message-specific details are sent as a JSON object in request parameter 'json' and the message authentication code is sent in request parameter 'mac'.


Structure of the payment_return message ('json') (legacy 'redirect' flavour)

data field example data description
message_time 2016-04-11T14:29:42+0000
message_type payment_return
paimentId order 123 merchant-side reference identifier, to associate data in MK and merchant' systrems
amount 11.0 Any positive number with two decimal places maximum
signature 98A123D3E2F6AB1D2E99... obsolete, do not use the field to verify authenticity of message. use MAC
status PAID RECEIVED, PAID, CANCELLED, EXPIRED, PART_REFUNDED, REFUNDED, DECLINED
auto False Boolean
merchant_data whatever was placed to the conatiner when transaction was created


Difference in Structure of the message, 'normal' vs 'redirect' flavour

normal redirect flavour comments
message_time message_time
message_type message_type
paimentId reference
amount amount
currency
signature obsolete, use MAC comparison described here
status status see differences in status model below
auto obsolete
merchant_data merchant_data optional, present only when it contains data
shop
transaction


Differences in state model of the normal and legacy 'redirect' flavour

normal 'redirect flavour' comment
CREATED
PENDING RECEIVED
CANCELLED CANCELLED
EXPIRED EXPIRED
APPROVED
DECLINED
COMPLETED PAID
PART_REFUNDED PART_REFUNDED
REFUNDED REFUNDED
See more about the state model