At a high level, cardholders have registered their payment information with a 3rd party such as a mobile phone vendor, e.g., Apple, with a token being returned that is stored on their device. The cardholder then uses this stored token to purchase goods/services within a merchant’s application that is on their device. The merchant’s application sends the authorization message to Portico using the standard CreditAuth or CreditSale transactions. However, the SecureECommerce field is sent within those messages containing the necessary eCommerce InApp data that is required by the brands and issuers to settle correctly.

ECI Indicator

If an EcommerceIndicator is sent in for ApplePay or GooglePay, it will be passed along to the host.

If an ECI value is not passed in, the following default values will be assigned:

• Exchange the value is 4
• GSAP-NA the value is 5

This functionality is currently only supported for ApplePay and GooglePay for Visa, MasterCard, American Express, and Discover.

ApplePay or GooglePay In App

For ApplePay or GooglePay In-App, the following SecureECommerce data elements apply:

• PaymentDataSource  set to the appropriate value, eg, "ApplePay", "ApplePayInApp", "GooglePayInApp"
• TypeOfPaymentData
  • 3DSecure
• PaymentData
  • Visa CAVV, Discover CAVV, AMEX Token Data Token Data Block A followed by Token Data Block B, and Mastercard UCAF
• ECommerceIndicator
  • Numeric value from 0–7
    If sent, this value is ignored.

American Express Payment Data

For AMEX only, the following is also supported, but both token data blocks may be sent in PaymentData:

• PaymentData
  • AMEX Token Data Token Data Block B
• XID
  • AMEX Token Data Token Data Block A