ReturnUrl Response (v2 Endpoint)

These objects are used in postMessage events between CruiseAPI and the merchant.

Profile Completed

The V1 and V2 profile completed objects are similar but V2 offers additional information about the data collection to allow merchants to make decisions based on the success or failure of certain data points. For example if we were unable to collect `CardinalData` the merchant could opt to send the 11 required fields on the `cmpi_lookup` request to ensure a 3DS 2.0 transaction can still complete.

ReturnUrl Response JWT Example -

{
  "iss": "5b7c5b922f3e733a44320e85",
  "iat": 1535052764,
  "exp": 1535059964,
  "jti": "83840924-a856-4901-ab21-0b61421c0933",
  "aud": "49e56790-a70b-11e8-9354-f715d5987f69",
  "Payload": {
    "ActionCode":"SUCCESS",
    "SessionId": "0_90de2cfc-f8c7-4793-b4fa-ddd841aa2be8",
    "DataSources": {
        "CardinalData": {
            "Attempted": true,
            "Completed": true
        },
        "MethodUrl": {
            "Attempted": true,
            "Completed": true
        }
    }
}
}

ReturnUrl Response Fields -

The ReturnUrl Response object is the Payload object of a collect response flow.

Field

Type

Description

ActionCode

String

The status of the collect attempt.

Possible Values:

SUCCESS
ERROR

DataSources

DataSources Object

Refer to the DataSources object for more details.

SessionId

String

The McsId generated for this request. This value should be used as the DFReferenceId the merchant sends to Centinel Core on the cmpi_lookup.

DataSources

Field	Type	Description
CardinalData	ProfileResult	An object that describes the collection status of Cardinal data
MethodUrl	ProfileResult	An object that describes the collection status of MethodUrl

ProfileResult

Field	Type	Description
Attempted	boolean	Was this data source even attempted to be collected
Completed	boolean	Was this data source collection completed successfully