{"title":"Google Secure Payment Authentication (Google SPA)","category":"default","creationDate":1789729029,"content":"<p><span style=\"color: #0ABF53;\"><span style=\"font-size: 20px;\"><strong>Limited availability<\/strong><\/span><\/span><br \/>\nGoogle SPA is currently only enabled for a specific group of merchants. If you want to be included in this group, reach out to your Adyen contact.<\/p>\n<hr \/>\n<p>Google Secure Payment Authentication (Google SPA) lets shoppers authenticate online card payments with device biometrics. It supports Strong Customer Authentication (SCA) requirements, including the revised Payment Services Directive (PSD2).<\/p>\n<p>The shopper completes the authentication directly on your website, using the Google web front end. This avoids a redirect to the shopper's card issuer for 3D Secure authentication. By reducing this friction, Google SPA can help improve payment conversion. When the authentication is successful, Google SPA also provides a liability shift.<\/p>\n<h2>Requirements<\/h2>\n<table>\n<thead>\n<tr>\n<th style=\"text-align: left;\">Requirement<\/th>\n<th style=\"text-align: left;\">Description<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td style=\"text-align: left;\"><strong>Integration type<\/strong><\/td>\n<td style=\"text-align: left;\">An Adyen online payments integration that uses Adyen to authenticate and authorize payments.<\/td>\n<\/tr>\n<tr>\n<td style=\"text-align: left;\"><strong>Limitations<\/strong><\/td>\n<td style=\"text-align: left;\"><ul><li markdown=\"1\">Google SPA is not supported if the redirect URL opens in an iFrame.<\/li><li markdown=\"1\">You cannot enforce Google SPA as the authentication method on a transaction. The Authentication Engine automatically selects Google SPA only if it is the most optimal authentication method for the transaction.<\/li><li markdown=\"1\">You currently cannot test the Google SPA shopper experience in the TEST environment.<\/li><li markdown=\"1\">Google SPA is currently not supported for recurring Merchant Initiated Transactions (MIT), such as <a href=\"\/online-payments\/tokenization\/make-token-payments#make-a-subscription-or-unscheduled-card-on-file-payment\">subscriptions or unscheduled card-on-file payments<\/a> where the  <a href=\"https:\/\/docs.adyen.com\/api-explorer\/Checkout\/latest\/post\/payments#request-recurringProcessingModel\" class=\"codeLabel  external-link no-image\" target=\"_blank\" rel=\"nofollow noopener noreferrer\">recurringProcessingModel<\/a> is set to <strong>Subscription<\/strong> or <strong>UnscheduledCardOnFile<\/strong>.<\/li><li markdown=\"1\">Google SPA is only supported if you use Adyen for both authentication and authorization.<\/li><\/ul><\/td>\n<\/tr>\n<tr>\n<td style=\"text-align: left;\"><strong>Setup steps<\/strong><\/td>\n<td style=\"text-align: left;\"><ul><li markdown=\"1\">You must support the redirect flow for 3D Secure 2 authentication:<ul><li><a href=\"\/online-payments\/build-your-integration\/sessions-flow\">\n  <strong>Sessions flow<\/strong>\n<\/a>: 3D Secure 2 support is built-in. You must set the  <a href=\"https:\/\/docs.adyen.com\/api-explorer\/Checkout\/latest\/post\/sessions#request-authenticationData-threeDSRequestData-nativeThreeDS\" class=\"codeLabel  external-link no-image\" target=\"_blank\" rel=\"nofollow noopener noreferrer\">nativeThreeDS<\/a> to <span translate=\"no\"><strong>disabled<\/strong><\/span> in your POST  <a href=\"https:\/\/docs.adyen.com\/api-explorer\/Checkout\/latest\/post\/sessions\" class=\"codeLabel  external-link no-image\" target=\"_blank\" rel=\"nofollow noopener noreferrer\">\/sessions<\/a> request.<\/li><li markdown=\"1\"><a href=\"\/online-payments\/build-your-integration\/advanced-flow\">\n  <strong>Advanced flow<\/strong>\n<\/a>: <a href=\"\/online-payments\/3d-secure\/redirect-3ds2\">Implement redirect 3D Secure 2<\/a> and make sure you send in the <a href=\"\/online-payments\/3d-secure\/api-reference#3d-secure-2-additional-data-objects\">applicable 3D Secure 2 parameters<\/a> for your integration type in your POST  <a href=\"https:\/\/docs.adyen.com\/api-explorer\/Checkout\/latest\/post\/payments\" class=\"codeLabel  external-link no-image\" target=\"_blank\" rel=\"nofollow noopener noreferrer\">\/payments<\/a> request.<\/li><\/ul><\/li><li markdown=\"1\">Add the <a href=\"\/payment-methods\/add-payment-methods\">payment methods that you want to accept<\/a> in your <a href=\"https:\/\/ca-test.adyen.com\/\" target=\"_blank\" rel=\"nofollow noopener noreferrer\" class=\"external-link no-image\">Customer Area<\/a>.<\/li><\/ul><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<h2>How Google SPA works<\/h2>\n<ol>\n<li>You make a payment request using your 3D Secure 2 redirect integration.\n<ul>\n<li><a href=\"\/online-payments\/build-your-integration\/sessions-flow\">\n  <strong>Sessions flow<\/strong>\n<\/a>: 3D Secure 2 support is built-in. You must set the  <a href=\"https:\/\/docs.adyen.com\/api-explorer\/Checkout\/latest\/post\/sessions#request-authenticationData-threeDSRequestData-nativeThreeDS\" class=\"codeLabel  external-link no-image\" target=\"_blank\" rel=\"nofollow noopener noreferrer\">nativeThreeDS<\/a> to <strong>disabled<\/strong> in your POST  <a href=\"https:\/\/docs.adyen.com\/api-explorer\/Checkout\/latest\/post\/sessions\" class=\"codeLabel  external-link no-image\" target=\"_blank\" rel=\"nofollow noopener noreferrer\">\/sessions<\/a> request.<\/li>\n<li><a href=\"\/online-payments\/build-your-integration\/advanced-flow\">\n  <strong>Advanced flow<\/strong>\n<\/a>: <a href=\"\/online-payments\/3d-secure\/redirect-3ds2\">Implement redirect 3D Secure 2<\/a> and make sure you send in the <a href=\"\/online-payments\/3d-secure\/api-reference#3d-secure-2-additional-data-objects\">applicable 3D Secure 2 parameters<\/a> for your integration type in your POST  <a href=\"https:\/\/docs.adyen.com\/api-explorer\/Checkout\/latest\/post\/payments\" class=\"codeLabel  external-link no-image\" target=\"_blank\" rel=\"nofollow noopener noreferrer\">\/payments<\/a> request.<\/li>\n<\/ul><\/li>\n<li>The Authentication Engine determines whether the transaction requires a challenge and chooses the most optimal authentication method based on <a href=\"#eligibility\">eligibility<\/a>.\n<ol>\n<li>If Google SPA is the most optimal authentication method, the shopper verifies their identity using device biometrics in the Google web front end. If the authentication fails, Adyen falls back to 3D Secure 2 authentication.<\/li>\n<li>If the transaction is not eligible for Google SPA, or if it is not the most optimal authentication method, Adyen selects a different method such as 3D Secure 2.<\/li>\n<\/ol><\/li>\n<li>After the shopper completes authentication successfully, Adyen continues the payment flow.<\/li>\n<\/ol>\n<h2>Eligibility<\/h2>\n<p>When the shopper makes a payment request, Adyen checks if Google SPA is an eligible authentication method for the transaction. The eligibility depends on the following criteria:<\/p>\n<table>\n<thead>\n<tr>\n<th style=\"text-align: left;\"><strong>Criterion<\/strong><\/th>\n<th style=\"text-align: left;\"><strong>Description<\/strong><\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td style=\"text-align: left;\"><strong>Supported devices and browsers<\/strong><\/td>\n<td style=\"text-align: left;\">Supported operating system: Android <br><br>Supported browsers:<ul><li markdown=\"1\">Google Chrome<\/li><li markdown=\"1\">Microsoft Edge<\/li><li markdown=\"1\">Brave<\/li><li markdown=\"1\">Samsung Internet<\/li><\/ul>.<\/td>\n<\/tr>\n<tr>\n<td style=\"text-align: left;\"><strong>Supported payment methods<\/strong><\/td>\n<td style=\"text-align: left;\">Google SPA is supported for Mastercard and Visa Funding Primary Account Number (FPAN) transactions. The shopper's card must be tokenized in Google Wallet.<\/td>\n<\/tr>\n<tr>\n<td style=\"text-align: left;\"><strong>Supported payment flows<\/strong><\/td>\n<td style=\"text-align: left;\">Google SPA is supported for all payments with <code>shopperInteraction<\/code> set to <strong>Ecommerce<\/strong>. For <a href=\"\/online-payments\/tokenization\/make-token-payments\">recurring payments<\/a>, Google SPA is supported for all Customer Initiated Transactions (CIT). Google SPA is not supported for recurring Merchant Initiated Transactions (MIT), such as subscriptions.<\/td>\n<\/tr>\n<tr>\n<td style=\"text-align: left;\"><strong>Regional availability<\/strong><\/td>\n<td style=\"text-align: left;\">Google SPA is currently available in the UK and Poland.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<h2>Shopper experience<\/h2>\n<p>When authenticating a payment using Google SPA, the shopper follows the following flow:<\/p>\n<ol>\n<li>The shopper clicks the <strong>Pay<\/strong> button on your website.<br \/>\n<a rel=\"lightbox\" href=\"\/user\/pages\/docs\/02.online-payments\/18.authentication\/01.google-secure-payment-authentication\/payment-screen.png\" src=\"\">\n  <img alt=\"Payment screen\" src=\"\/images\/1\/5\/5\/d\/2\/155d226fe5f91ec3e4f865b269c6e9e831a40a5d-payment-screen.png\" \/>\n<\/a><\/li>\n<li>Adyen redirects the shopper to the Google web front end.<br \/>\n<a rel=\"lightbox\" href=\"\/user\/pages\/docs\/02.online-payments\/18.authentication\/01.google-secure-payment-authentication\/google-web-front-end.png\" src=\"\">\n  <img alt=\"Google web front end\" src=\"\/images\/7\/7\/f\/e\/9\/77fe9c015fe4467335a9d52e56e73327b6032799-google-web-front-end.png\" \/>\n<\/a><\/li>\n<li>The shopper verifies their identity using device biometrics.<br \/>\n<a rel=\"lightbox\" href=\"\/user\/pages\/docs\/02.online-payments\/18.authentication\/01.google-secure-payment-authentication\/biometrics.png\" src=\"\">\n  <img alt=\"Biometrics\" src=\"\/images\/c\/f\/8\/5\/1\/cf851487470d011ff22d35fd4de9eae8036d9ae3-biometrics.png\" \/>\n<\/a><\/li>\n<li>Adyen redirects the shopper back to your website.<br \/>\n<a rel=\"lightbox\" href=\"\/user\/pages\/docs\/02.online-payments\/18.authentication\/01.google-secure-payment-authentication\/successful-verification.png\" src=\"\">\n  <img alt=\"Successful verification\" src=\"\/images\/1\/3\/b\/2\/a\/13b2a08f776b62994ba56ae75a70e15a600f4b03-successful-verification.png\" \/>\n<\/a><\/li>\n<li>Adyen continues the payment flow.<\/li>\n<\/ol>\n<h2>Liability shift<\/h2>\n<p>A successful Google SPA authentication can shift liability from your company to the issuer. These transactions benefit from the same fraud protection rules as <a href=\"\/payment-methods\/google-pay#liability-shift\">Device Primary Account Number (DPAN) transactions in Google Pay<\/a>.<\/p>\n<p>Every transaction authenticated with 3D Secure 2 receives an Electronic Commerce Indicator (ECI) value that indicates the state of the authentication and determines whether liability can be shifted to the issuer.<\/p>\n<p>The final liability shift outcome is determined after authorization. A card scheme can downgrade a payment's liability shift during authorization, even if the ECI value indicated a liability shift during authentication.<\/p>\n<p>Liability shift does not prevent a shopper from raising a dispute or chargeback. For more information, see <a href=\"\/online-payments\/3d-secure-for-regulation-compliance#3dsecurechargebackliabilityshiftrules\">3D Secure liability shift rules<\/a>.<\/p>\n<h2>See also<\/h2>\n<div class=\"see-also-links output-inline\" id=\"see-also\">\n<ul><li><a href=\"\/online-payments\/authentication\"\n                        target=\"_self\"\n                        >\n                    Authentication\n                <\/a><\/li><li><a href=\"\/online-payments\/3d-secure\/redirect-3ds2\"\n                        target=\"_self\"\n                        >\n                    Redirect 3D Secure 2\n                <\/a><\/li><li><a href=\"\/online-payments\/3d-secure-for-regulation-compliance\"\n                        target=\"_self\"\n                        >\n                    3D Secure for regulation compliance\n                <\/a><\/li><\/ul><\/div>\n","url":"https:\/\/docs.adyen.com\/online-payments\/authentication\/google-secure-payment-authentication","articleFields":{"description":"Use Google Secure Payment Authentication to authenticate shoppers with device biometrics.","feedback_component":true,"filters_component":false},"algolia":{"url":"https:\/\/docs.adyen.com\/online-payments\/authentication\/google-secure-payment-authentication","title":"Google Secure Payment Authentication (Google SPA)","content":"Limited availability\nGoogle SPA is currently only enabled for a specific group of merchants. If you want to be included in this group, reach out to your Adyen contact.\n\nGoogle Secure Payment Authentication (Google SPA) lets shoppers authenticate online card payments with device biometrics. It supports Strong Customer Authentication (SCA) requirements, including the revised Payment Services Directive (PSD2).\nThe shopper completes the authentication directly on your website, using the Google web front end. This avoids a redirect to the shopper's card issuer for 3D Secure authentication. By reducing this friction, Google SPA can help improve payment conversion. When the authentication is successful, Google SPA also provides a liability shift.\nRequirements\n\n\n\nRequirement\nDescription\n\n\n\n\nIntegration type\nAn Adyen online payments integration that uses Adyen to authenticate and authorize payments.\n\n\nLimitations\nGoogle SPA is not supported if the redirect URL opens in an iFrame.You cannot enforce Google SPA as the authentication method on a transaction. The Authentication Engine automatically selects Google SPA only if it is the most optimal authentication method for the transaction.You currently cannot test the Google SPA shopper experience in the TEST environment.Google SPA is currently not supported for recurring Merchant Initiated Transactions (MIT), such as subscriptions or unscheduled card-on-file payments where the  recurringProcessingModel is set to Subscription or UnscheduledCardOnFile.Google SPA is only supported if you use Adyen for both authentication and authorization.\n\n\nSetup steps\nYou must support the redirect flow for 3D Secure 2 authentication:\n  Sessions flow\n: 3D Secure 2 support is built-in. You must set the  nativeThreeDS to disabled in your POST  \/sessions request.\n  Advanced flow\n: Implement redirect 3D Secure 2 and make sure you send in the applicable 3D Secure 2 parameters for your integration type in your POST  \/payments request.Add the payment methods that you want to accept in your Customer Area.\n\n\n\nHow Google SPA works\n\nYou make a payment request using your 3D Secure 2 redirect integration.\n\n\n  Sessions flow\n: 3D Secure 2 support is built-in. You must set the  nativeThreeDS to disabled in your POST  \/sessions request.\n\n  Advanced flow\n: Implement redirect 3D Secure 2 and make sure you send in the applicable 3D Secure 2 parameters for your integration type in your POST  \/payments request.\n\nThe Authentication Engine determines whether the transaction requires a challenge and chooses the most optimal authentication method based on eligibility.\n\nIf Google SPA is the most optimal authentication method, the shopper verifies their identity using device biometrics in the Google web front end. If the authentication fails, Adyen falls back to 3D Secure 2 authentication.\nIf the transaction is not eligible for Google SPA, or if it is not the most optimal authentication method, Adyen selects a different method such as 3D Secure 2.\n\nAfter the shopper completes authentication successfully, Adyen continues the payment flow.\n\nEligibility\nWhen the shopper makes a payment request, Adyen checks if Google SPA is an eligible authentication method for the transaction. The eligibility depends on the following criteria:\n\n\n\nCriterion\nDescription\n\n\n\n\nSupported devices and browsers\nSupported operating system: Android Supported browsers:Google ChromeMicrosoft EdgeBraveSamsung Internet.\n\n\nSupported payment methods\nGoogle SPA is supported for Mastercard and Visa Funding Primary Account Number (FPAN) transactions. The shopper's card must be tokenized in Google Wallet.\n\n\nSupported payment flows\nGoogle SPA is supported for all payments with shopperInteraction set to Ecommerce. For recurring payments, Google SPA is supported for all Customer Initiated Transactions (CIT). Google SPA is not supported for recurring Merchant Initiated Transactions (MIT), such as subscriptions.\n\n\nRegional availability\nGoogle SPA is currently available in the UK and Poland.\n\n\n\nShopper experience\nWhen authenticating a payment using Google SPA, the shopper follows the following flow:\n\nThe shopper clicks the Pay button on your website.\n\n  \n\nAdyen redirects the shopper to the Google web front end.\n\n  \n\nThe shopper verifies their identity using device biometrics.\n\n  \n\nAdyen redirects the shopper back to your website.\n\n  \n\nAdyen continues the payment flow.\n\nLiability shift\nA successful Google SPA authentication can shift liability from your company to the issuer. These transactions benefit from the same fraud protection rules as Device Primary Account Number (DPAN) transactions in Google Pay.\nEvery transaction authenticated with 3D Secure 2 receives an Electronic Commerce Indicator (ECI) value that indicates the state of the authentication and determines whether liability can be shifted to the issuer.\nThe final liability shift outcome is determined after authorization. A card scheme can downgrade a payment's liability shift during authorization, even if the ECI value indicated a liability shift during authentication.\nLiability shift does not prevent a shopper from raising a dispute or chargeback. For more information, see 3D Secure liability shift rules.\nSee also\n\n\n                    Authentication\n                \n                    Redirect 3D Secure 2\n                \n                    3D Secure for regulation compliance\n                \n","type":"page","locale":"en","boost":17,"hierarchy":{"lvl0":"Home","lvl1":"Online payments","lvl2":"Authentication","lvl3":"Google Secure Payment Authentication (Google SPA)"},"hierarchy_url":{"lvl0":"https:\/\/docs.adyen.com\/","lvl1":"https:\/\/docs.adyen.com\/online-payments","lvl2":"https:\/\/docs.adyen.com\/online-payments\/authentication","lvl3":"\/online-payments\/authentication\/google-secure-payment-authentication"},"levels":4,"category":"Online Payments","category_color":"green","tags":["Google","Secure","Payment","Authentication","(Google"]},"articleFiles":{"biometrics.png":"<img alt=\"\" src=\"https:\/\/docs.adyen.com\/user\/pages\/docs\/02.online-payments\/18.authentication\/01.google-secure-payment-authentication\/biometrics.png\" \/>","google-web-front-end.png":"<img alt=\"\" src=\"https:\/\/docs.adyen.com\/user\/pages\/docs\/02.online-payments\/18.authentication\/01.google-secure-payment-authentication\/google-web-front-end.png\" \/>","payment-screen.png":"<img alt=\"\" src=\"https:\/\/docs.adyen.com\/user\/pages\/docs\/02.online-payments\/18.authentication\/01.google-secure-payment-authentication\/payment-screen.png\" \/>","successful-verification.png":"<img alt=\"\" src=\"https:\/\/docs.adyen.com\/user\/pages\/docs\/02.online-payments\/18.authentication\/01.google-secure-payment-authentication\/successful-verification.png\" \/>"}}