These objects are used in postMessage events between CruiseAPI and the merchant.
Currently, V2 Endpoint is only supported for Implementation Option 1 and Implementation Option 3. We plan to add V2 support for Implementation Option 2 in the near future.
Profile Completed
The V1 and V2 profile completed objects are similar, however 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 Cardinal is unable to collect “CardinalData”, the merchant could opt to send the 11 required Browser Fields on the cmpi_lookup request to ensure an EMV 3DS transaction can still complete.
postMessage Response -
{
"MessageType": "profile.completed",
"Payload":{
"ActionCode":"SUCCESS",
"SessionId": "0_90de2cfc-f8c7-4793-b4fa-ddd841aa2be8",
"DataSources": {
"CardinalData": {
"Attempted": true,
"Completed": true
},
"MethodUrl": {
"Attempted": true,
"Completed": true
}
}
}
}
|
postMessage Response Fields -
Field | Type | Value | Description |
|---|---|---|---|
MessageType | String | profile.completed | The message type for this object |
Payload | Profile Completed Object |