After the challenge is completed
The 3DS SDK will trigger:
- Android:
onValidated()- iOS:
stepUpDidValidate- Songbird.js:
"payments.validated"This is how the 3DS SDK hands back control to the merchant's application. This event will include data on how the transaction attempt ended and should be where you review the results of the transaction and make decisions regarding the next steps. The field ActionCode should be used to determine the overall state of the transaction. On the first pass, we recommend that on an ActionCode of 'SUCCESS' you send the response JWT to
AuthenticateAPI for verification.
| Value | Description |
|---|---|
| SUCCESS | Authentication was completed successfully. You will have a UCAF, ECIFlag, and XID to send during authorization. |
| CANCEL | Transaction canceled by the user. |
| ERROR | An error was encountered. Refer to ErrorNumber and ErrorDescription for more details on the error. If a Payment object is present you may have additional details in the ReasonCode and ReasonDescription fields within the Payment object |
| FAILURE | Authentication resulted in a failure - this includes the end user failing authentication. |
| NOACTION | Authentication was not applicable and no service level errors were encountered. When the ErrorNumber is 0, generally this means you may move on to authorization, but be aware the transaction may not be eligible for liability shift. |
| TIMEOUT | Returned when the challenge process reaches or exceeds the timeout interval that is specified during the cca_continue call. |