On This Page
FILTER BY TAG

completeMandate.consumerAuthentication

This field determines how a consumer is authenticated. You can authenticate a consumer using
3-D Secure
.
You can set this field to one of these values:
  • NONE
    : Consumer authentication does not run.
  • 3DS
    :
    3-D Secure
     authentication through
    Payer Authentication
     runs
To initiate a passkey request for
Unified Checkout
, you must include these additional fields in your request:
  • completeMandate.consumerAuthentication
     set to
    PASSKEY
  • data.merchantInformation.merchantDescriptor.name
  • data.acquirerInformation.country
When you use
Unified Checkout
 with
Payer Authentication
, device data is collected through
Payer Authentication
 setup and
Unified Checkout
 completes all calls that are associated with
Payer Authentication
.
To test
Payer Authentication
, you must use
Payer Authentication
 test cards. See Test Cases for 3-D Secure 2.x in the
Payer Authentication
 Developer Guide
.
Consumer authentication is available for these card types:
  • American Express
  • China UnionPay
  • EFTPOS
  • JCB
  • mada
  • Maestro
  • Mastercard
  • Visa
Consumer authentication runs for these payment methods when they are supported in your
Unified Checkout
 configuration:
  • PANENTRY
  • CLICKTOPAY
     when the transaction is not authenticated with
    Click to Pay
    .
  • GOOGLEPAY
     when the transaction is not authenticated with Google Pay.
Unified Checkout
 does not attempt to authenticate for
Click to Pay
 and Google Pay if the transaction has already been authenticated when it is received by
Unified Checkout
. For information about testing authentication, see Test Authentication.
RELATED TO THIS PAGE