TABLE OF CONTENTS

Card authentication methods


There are two card authentification methods for Google Pay:

  • PAN_ONLY: This authentication method is associated with payment cards stored on file with the user's Google Account. Returned payment data includes personal account number (PAN) with the expiration month and the expiration year.
  • CRYPTOGRAM_3DS: This authentication method is associated with cards stored as Android device tokens. Returned payment data includes a 3-D Secure (3DS) cryptogram generated on the device. 



Solid forces all PAN_ONLY authorisation requests to 3DS. There is no need to send additional parameters. 



3DS steps


Google Pay 3DS going through a few steps:


1) Google request,

2) Redirect to verify_url - URL for 3DS verification.



To proceed with 3D Secure verification procedure client should be redirected to the issuing bank page `verify_url.
virify_url` can be received from the following requests:
- Status
- Notification


Liability shift


CRYPTOGRAM_3DS credentials receive liability shift by default.

Applying 3DS enables liability shift for PAN_ONLY transactions.