FILTER BY TAG

completeMandate.consumerAuthentication

This field determines whether
Payer Authentication
should be used. Set this field to
true
and include
completeMandate.type
in your request to run
Payer Authentication
. When this field set to
true
,
Payer Authentication
runs. When this field is set to
false
or is not included in the request,
Payer Authentication
does not run.
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
.
For information about challenge codes, see
consumerAuthenticationInformation.challengeCode
in the REST API Field Reference. Unified Checkout supports
3-D Secure
data only when your payment processor supports it. For information see Visa Data Only in the
Payer Authentication
Developer Guide
.
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
  • Cartes Bancaires
  • China UnionPay
  • Diners Club
  • Discover
  • EFTPOS
  • ELO
  • Jaywan
  • 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.