URLSuccess

KeyFormatCNDDescription
URLSuccess

ans..256

M

Complete URL which calls up  if payment has been successful. The URL may be called up only via port 443. This URL may not contain parameters: In order to exchange values between  and shop, please use the parameter UserData.

(info) Common notes:

  • We recommend to use parameter "response=encrypted" to get an encrypted response by
  • However, fraudster may just copy the encrypted DATA-element which are sent to URLFailure and send the DATA to URLSuccess. Therefore ensure to check the "code"-value which indicates success/failure of the action. Only a result of "code=00000000" should be considered successful.

URLSuccess 3-D Secure

KeyFormatCNDDescription
URLSuccess

ans..256

M

Complete URL which calls up  if payment has been successful. The URL may be called up only via port 443. This URL may not contain parameters: In order to exchange values between  and shop, please use the parameter UserData.

(info) Common notes:

  • We recommend to use parameter "response=encrypted" to get an encrypted response by
  • However, fraudster may just copy the encrypted DATA-element which are sent to URLFailure and send the DATA to URLSuccess. Therefore ensure to check the "code"-value which indicates success/failure of the action. Only a result of "code=00000000" should be considered successful.

(info) Information for 3-D Secure:

  • payssl.aspx / payNow.aspx: Please note that the URL is called via POST for 3-D Secure 2.x and via GET for 3-D Secure 1.x (e.g. in case of fallback). Therefore your system should check parameters for POST as well as for GET method.
  • No labels