Closed niklaswulff closed 2 years ago
Maybe allow new alternative key event
which will be called in all cases and if that key is defined, neither success
nor cancel
can be defined?
Hi @niklaswulff
A success-url cannot receive the fail status, these will always be sent to the cancel-url. Both are required so we and implementing merchants can cleanly separate the different outcomes.
@jfrojd-paytrail So why is there a need for status properties? Wouldn't it be sufficient to use the different endpoints?
In the documentation for callbacks, there's a reference to the "checkout-status", which can contain any of the listed statuses
Payment status, either ok, pending, delayed, or fail
If so, why do we need separate endpoints for success calls and fail calls?