Notification of the shop
After processing the payment, the payment platform notifies the shop of the payment result. To do this, the payment platform calls URLNotify via HTTP POST. This is an entirely separate communication which has nothing to do with the original connection between the shop, the customer and the payment platform. The parameters are transmitted in the HTTP Body as a Blowfish-encrypted parameter string. The content type is application/x-www-form-urlencoded; charset=iso-8859-1. Therefore, the standard values for HTML-form analysis are used.
Notice: Please note that the Notify-call is permitted only via Port 443 (TLS) for security reasons.
If the shop’s URLNotify is not accessible (e.g. HTTP-status 500/404), notification is repeated 8 times. In this case the customer transmits to the shop is prior to the URLNotify request. Therefore, the shop should analyse and compare both status messages from URLNotify and transmission (URLSuccess, URLFailure).
Repeat | Waiting time | Time after first notify |
|---|---|---|
0 | Instantly | 0 |
1 | 00:01 h | 00:01 h |
2 | 00:08 h | 00:09 h |
3 | 00:27 h | 00:36 h |
4 | 01:04 h | 01:40 h |
5 | 02:05 h | 03:45 h |
6 | 03:36 h | 07:21 h |
7 | 05:43 h | 13:04 h |
8 | 08:32 h | 21:36 h |
Time of repeat of Notify respectively calculated after first failed attempt
Notice: The URL encoded parameters are transmitted in key-value pairs (Key1=Value1&Key2=Value2). Please note that new parameters can be added unannounced at any time. Therefore, we recommend the use of the parameter name for the analysis, not the order since this can change at any time. Please do not use case sensitive mechanisms for the spelling of the parameters as this can change at any time. For example, it is recommended switching all parameters “to lower” and continuing in lower case.
For more details please go to: www.w3.org/MarkUp/html-spec/html-spec_8.html#SEC8.2.1
POST and GET methods use to send the payment notification
Card payments | POST for 3DSV2 |
Other payment methods | GET for URLNotify |