Versions Compared

Old Version 7

changes.mady.by.user Suyash Somani

Saved on

compared with

New Version Current

changes.mady.by.user Suyash Somani

Saved on

Key

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

...

Example of JWT with ReturnUrl Claim -

Code Block
languagejson
{
  "jti": "f7c64630-a167-11e8-9db5-9f12cae676de",
  "iat": 1534432854,
  "iss": "Midas-NoDV-Key",
  "OrgUnitId": "564cdcbcb9f63f0c48d6387f",
  "ReferenceId": "c3989c38-6caf-410a-8965-459b1e814648",
  "ReturnUrl": "http://localhost:8189/cart/enterprise/collect-term",
  "Payload": {
    "OrderDetails": {
      "Amount": 1500,
      "CurrencyCode": 840,
      "OrderNumber": "asdf"
    }
  },
  "ObjectifyPayload": true
}

Based on the endpoint a merchant is integrated with, we will provide different responses.

  1. ReturnUrl Response (v1 Endpoint)

  2. ReturnUrl Response (v2 Endpoint)

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 9 required fields on the `cmpi_lookup` request to ensure a 3DS 2.0 transaction can still complete.

Note

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.