On This Page
Test Authentication
Use this table to determine how to test your authentication method.
Product | Payment Method | Authentication | Minimum Follow-On Actions | Prerequisites | Test Cards | Details |
|---|---|---|---|---|---|---|
Unified Checkout | PAN Entry | Payer Authentication through Unified Checkout | Authorization and Payer Authentication | The transacting MID must be enabled for Payer Authentication and the complete mandate is used with the
consumerAuthentication field set to
true . | See Testing Payer Authentication in the Payer Authentication
Developer Guide. | When the complete mandate is not used, Unified Checkout does not initiate authentication and you
must perform authentication within your own environment. |
Click to Pay | Payer Authentication through Unified Checkout | Authorization and Payer Authentication | The transacting MID must be enabled for Payer Authentication and the complete mandate is used with the
consumerAuthentication field set to
true .Authentication for
Click to Pay must not be configured. | When authentication is not enabled for Click to Pay or Click to Pay is
not able to perform authentication for Click to Pay , Unified Checkout performs
authentication using Payer Authentication when the complete
mandate is used with the consumerAuthentication
field set to true . | ||
Click to Pay | Visa Click to Pay | Authorization and Payer Authentication | You must configure the authentication for Click to Pay . Click to Pay
performs authentication only if it is a tokenized Visa card. | See Test Payment Details. | When authentication is enabled for Click to Pay , authentication is attempted for all Click to Pay transactions for Visa cards that are
stored in Click to Pay . For information about
setting up authentication for Visa Click to Pay ,
see Set Up Customer Authentication for Visa Click to Pay. | |
Google Pay | Google Pay | Authorization | A Google device must be used with biometric authentication for
Google authentication. | A user authenticates themselves on a Google device with a
tokenized Google Pay credential – the returned payload from Google
will be Authenticated | ||
Google Pay | Payer Authentication through Unified Checkout | Authorization and Payer Authentication | You must use a device, such as a web browser, that does not
authenticate the cardholder as part of the authorization
process. | Google will return an un-authenticated payload to Unified
Checkout . Unified Checkout will step in and process Authentication
via Payer Authentication when the Complete Mandate function is used
with consumerAuthentication | ||
Click to Pay Drop-In UI | PAN Entry | Your authentication product | N/A | Cardholder checking out by manually entering card details in
Drop-in UI and not enrolling the chosen card in Click to Pay or is
enrolling the card in Click to Pay for the first time | Authentication is not performed within the Click to Pay flow. Authentication takes place within
your own environment where required. | |
Click to Pay | Visa Click to Pay | Click to Pay Authentication | You must configure the authentication for Click to Pay . Click to Pay
performs authentication only if it is a tokenized Visa card. | See Test Payment Details. | When authentication is enabled for Click to Pay , authentication is attempted for all Click to Pay transactions for Visa cards that are
stored in Click to Pay . For information about
setting up authentication for Visa Click to Pay ,
see Set Up Customer Authentication for Visa Click to Pay. | |
Click to Pay | Your authentication product | N/A | Use this option when authentication is not enabled for Click to Pay . | See Test Payment Details. | Authentication is not performed within the Click to Pay flow. Authentication takes place within
your own environment where required. |