Ch 52. Device Channel Update

Owned by Suyash Somani
Last updated: Mar 08, 2023 by Chris Bohatka
1 min read

Changes made on 2020-07-14 are delineated below.

  • Additions are underlined in Green

  • Deletions are underlined in Red

  • Modifications are underlined in Blue

Change Occurred on: https://cardinaldocs.atlassian.net/wiki/spaces/CCen/pages/905478187

Device Data Information - OPTIONAL

DeviceChannel

Determines the channel that the transaction came through.

Possible Values: 

  • SDK

  • Browser

  • 3RI

NOTE: Cardinal will dynamically set 'Browser' when customer is using our Cardinal Cruise JavaScript. However, if the merchant is not running Device Data Collection, they need to pass Device Channel as 'Browser' along with the required browser fields in the Lookup Request.

C

Client will need to set Device Channel as:

  • 3RI for Merchant Initiated or 3RI transactions and; 

  • SDK for transactions initiated with Cardinal Mobile SDK

AN(10)

Merchant Initiated (3RI) - Conditionally Required

These fields are required for merchant initiated transactions when a cardholder isn't present.

DeviceChannel

Determines the channel that the transaction came through.

Possible Values: 

  • 3RI

  • SDK

  • Browser

C

Required for Merchant Initiated transactions.

AN(10)