On This Page
completeMandate.consumerAuthentication
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 Secureauthentication throughPayer Authenticationruns
Unified Checkout
, you must
include these additional fields in your request:- completeMandate.consumerAuthenticationset toPASSKEY
- 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
.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 GuideTo test .
Payer Authentication
, you must
use Payer Authentication
test cards. See Test Cases for 3-D Secure 2.x
in the
Payer Authentication
Developer GuideConsumer
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
- CLICKTOPAYwhen the transaction is not authenticated withClick to Pay.
- GOOGLEPAYwhen 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.