Cardinal Cruise Hybrid Steps
The following steps outline the requirements for integrating CCA into your baseline Cardinal Cruise integration, which was completed by following the steps in the Getting Started With Cardinal Centinel section.
Step 1: JWT Creation
Step 2: Include the Script
Step 3: Configure It
Step 4: Listen for Events
Step 5: Initialize It
Step 6: Include BIN Detection CCA
Step 7: Start Cardinal Consumer Authentication with Lookup Request CCA
Step 8: Handling the Lookup Response CCA
Step 9: Continue with CCA CCA
Step 10: Handling the CCA Response CCA
Step 11: JWT Validation
The below document outlines the transactional flow to complete a CCA hybrid transaction.
Implementation of Cardinal Cruise Hybrid
The below steps are required to enable CCA with your Cardinal Cruise Hybrid integration. We included sections in addition to Getting Started With Cardinal Centinel for including BIN Detection, running the Lookup Request & Response, Continuing with CCA and listening & processing the response.
Cardinal Cruise JS Hybrid integration allows for more flexibility when initiating CCA. As an integrator, it is required to run Steps 1 through Step 5 prior to initiating the cmpi_lookup request. However, you have the option to run Steps 1 through Steps 5 on a page prior to where the cmpi_lookup is initiated. This can be leveraged as a way to run the required device data collection and allow enough time to complete.
DFReferenceId / ReferenceId
When integrating Cardinal Cruise Hybrid method for CCA, it is required to populate the DFReferenceId in the cmpi_lookup request. In order to populate this ID correctly, there are two options available.
Option 1: You can subscribe to the payments.setupComplete callback function and pull the sessionId from the response and use that as your DFReferenceId in the cmpi_lookup request. Note, you will not need to add or populate the ReferenceId claim when generating the JWT.
Option 2: You can generate your own value, add this to the ReferenceId claim when the JWT is generated and pass the same value as your DFReferenceId in the cmpi_lookup request.
The DFReferenceId and the ReferenceId fields are 2 different names for the same value. Make sure to pass the same unique Id in both fields.
Step 7: Start Cardinal Consumer Authentication with Lookup Request
CCA is initiated by the merchant, typically when the customer clicks 'Place Order" or 'Submit Order' button. Instead of getting a card authorization, you will need to initiate the cmpi_lookup before authorization to our Cardinal Centinel platform. This API call is a backend server-to-server message that will be used to start the CCA transaction.
Please follow the Getting Started and Lookup Request/Response sections for completing your backend integration.
Lookup Request (cmpi_lookup)
Step 8: Handling the Lookup Response
The Lookup Response will return back an ACSUrl and Payload field, when these fields are populated, you can use these fields to determine if you need to present the authentication session to the consumer. If you need to present the authentication session, then continue with CCA in Step 9.
NOTE: If a Challenge is requested by the issuer, you must continue to Step 9 within 30 seconds of receiving the Lookup Response. If the StepUp does not occur within this window you may receive an error or an authentication failure and a new authentication request must be created before proceeding.
Step 9: Continue with Consumer Authentication
After the Lookup Response is returned, take the ACSUrl, Payload, and TransactionId and include them in the Cardinal.continue function in order to proceed with the authentication session.
The Cardinal.continue will display a modal window and automatically post the consumer's session over to the acs url for authentication.
Order object in the below example has been shortened for brevity.
// Add the rest of the Order object
Continue not working?
Cardinal.continue will only work after the payments.setupComplete event has been triggered. Try running Cardinal.continue later in your flow if payments.setupComplete has not triggered yet.
Step 10: Handling the CCA Response
Songbird.js will handle all the user interactions up until CCA has returned back the authentication result. The next step in the integration is to add logic to your payements.validated event to handle specific return values for CCA. The field ActionCode should be used as the primary transaction status indicator. Below are the possible values for ActionCode and what they indicate.
|SUCCESS||Authentication was completed successfully. You will have a CAVV, ECIFlag, and XID to send during authorization.|
|NOACTION||Authentication was not applicable, but 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.|
|FAILURE||Authentication resulted in a failure, this includes a the end user failing authentication.|
|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.|
Looking for CCA response objects?
Refer to the response objects section for information on what the CCA Payment object looks like.
The below example is what you should expect the response JWT to contain on a successful CCA transaction.
Alternative Option for Handling the CCA Response
Another option that is available, is to only take the ProcessorTransactionId from the payments.validated response and include that on a backend call to Cardinal Centinel called the cmpi_authenticate request. Some clients may find this helpful if they have already integrated the Lookup & Authenticate message pair.
Please follow the Getting Started and Authenticate Request/Response sections for completing your backend integration.
Authenticate Request (cmpi_authenticate)
An additional Cardinal Centinel configuration is available to suppress the 3-D Secure values and only populate the ProcessorTransactionId field.
Step 11: JWT Validation
Once the response JWT is received in the payments.validated event, you will need to send the response JWT to your backend to verify and extract the results. We recommend that any values sent to 3rd parties are sourced from the response JWT after it has been properly validated.
JWT validation should only ever be done on the server side for security reasons. Doing JWT validation on the front end is not an acceptable flow.
Looking for more information?
For more in depth information on JWT validation including code samples in a few languages, check out the JWT Validation
Please note that each Claim key is case sensitive.
|aud||Merchant jti Id - This is the 'jti' field from your request JWT echoed back. This field allows you to match up your request JWT with Cardinals response JWT.|
|jti||JWT Id - A unique identifier for this response JWT. This value is generated by Cardinal.|
|iat||Issued At Time - This is a timestamp of when the JWT was created.|
|iss||Issuer - The request JWT's iss field echoed back.|
|ConsumerSessionId||The unique session Id for the current user.|
|Payload||The response object for your request. This field will contain any actual state information on the transaction. This is the decoded data object that is passed into the |
payments.validated event as the first argument.
JWT Payload Example
Below is an example of the JSON content of a basic response JWT Payload where we are passing an object within the Payload claim:
Below is an example of the JSON content of a basic response JWT Payload where we are passing a string within the Payload claim. This would occur when the request JWT included a
ObjectifyPayload flag set to false:
You can begin testing transactions after you have completed the above steps for integrating Cardinal Cruise Standard into your merchant front end environment.