Delay processing of AUTHORISATION success=false notifications by 10 min
In some edge cases (for example 3DS1 authentication) an authorisation success=false notification can be sent earlier than the success=true one The reason can be a closed and reopened mobile application where the customer performs the 3DS1 authentication To avoid closing false unsuccessful orders, processing authorisation success=false and offer_closed notifications are delayed
Showing
Please register or sign in to comment