Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

The V1 and V2 profile completed objects are similar but , 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 we were Cardinal is unable to collect `CardinalData` “CardinalData”, the merchant could opt to send the 9 11 required fields Browser Fields on the `cmpicmpi_lookup` lookup request to ensure a an EMV 3DS 2.0 transaction can still complete.

postMessage Response -

Code Block
{
  "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