Handle the Centinel Lookup Response and SDK Handle the Challenge UI - Android- V 2.2.3
After the completion of the cmpi_lookup request, check the CMPI_Lookup_Response for the following fields :
- ThreeDSVersion = 2.X ( 2.0, 2.1, etc)
- Enrolled = Y
- PAResStatus = C
Upon validating the above fields, you will call cardinal.cca_continue to hand control to SDK for performing the challenge between the user and the issuing bank. Use the code snippet below for completing the cardinal.continue().
cardinal.cca_continue is updated to not passing the hardcoded directoryServerID anymore
cardinal.cca_continue(
"[TRANSACTION ID ]"
,
"[PAYLOAD]"
,
this
,
new
CardinalValidateReceiver() {
});
/** * Cca continue. * * @param transactionId the transaction id * @param payload the payload * @param currentActivity the current activity * @throws InvalidInputException the invalid input exception * @throws JSONException the json exception * @throws UnsupportedEncodingException the unsupported encoding exception */ try { cardinal.cca_continue("[TRANSACTION ID ]", "[PAYLOAD]", this, new CardinalValidateReceiver() { /** * This method is triggered when the transaction has been terminated. This is how SDK hands back * control to the merchant's application. This method will * include data on how the transaction attempt ended and * you should have your logic for reviewing the results of * the transaction and making decisions regarding next steps. * JWT will be empty if validate was not successful. * * @param validateResponse * @param serverJWT */ @Override public void onValidated(Context currentContext, ValidateResponse validateResponse, String serverJWT) { } }); } catch (Exception e) { // Handle exception }
onValidated() is triggered when the transaction has been terminated. This is how the Cardinal Mobile 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' or 'NOACTION' you send the response JWT to your backend for verification. There is more information on verifying JWT's in the next section.
@Override public void onValidated(Context currentContext, ValidateResponse validateResponse, String serverJWT) { switch (validateResponse.getActionCode()){ case SUCCESS: // Handle successful transaction, send JWT to backend to verify break; case NOACTION: // Handle no actionable outcome break; case FAILURE: // Handle failed transaction attempt break; case CANCEL: // Handle cancel transaction break; case ERROR: // Handle service level error break; case TIMEOUT: // Handle timeout break; } }
ValidateResponse Object
Validate Response
Modifier and Type | Field and Description |
---|---|
com.cardinalcommerce.cardinalmobilesdk.models.CardinalActionCode | actionCode |
java.lang.String | consumerSessionId |
java.lang.String | errorDescription |
int | errorNumber |
com.cardinalcommerce.cardinalmobilesdk.models.Payment | payment |
boolean | validated |
Action Code
Enum Constant and Description |
---|
ERROR |
FAILURE |
NOACTION |
SUCCESS |
CANCEL |
TIMEOUT |
Payment
Modifier and Type | Field and Description |
---|---|
com.cardinalcommerce.cardinalmobilesdk.models.ExtendedData | extendedData The Extended data. |
java.lang.String | processorTransactionId The Processor transaction id. |
java.lang.String | type The Type. |
Extended Data
Modifier and Type | Field and Description |
---|---|
java.lang.String | cavv The Cavv. |
java.lang.String | eciFlag The Eci flag. |
java.lang.String | enrolled Status of Authentication eligibility. |
java.lang.String | paResStatus Transaction status result identifier. |
java.lang.String | signatureVerification Transaction status result identifier. |
java.lang.String | xid The Xid. |