Home / Companies / Google Cloud / Blog / Post Details
Content Deep Dive

When to step-up your Google Pay transactions as a PSP

Blog post from Google Cloud

Post Details
Company
Date Published
Author
Dominik Mengelt, and Nick Alteen
Word Count
530
Company Posts That Month
9
Language
English
Hacker News Points
-
Post removed?
No
Summary

Step-up authentication in payment processing involves implementing additional security measures based on user activity and risk indicators to mitigate fraud and chargebacks. In the context of Google Pay transactions, whether step-up authentication is necessary depends on the type of authentication returned by the API, such as CRYPTOGRAM_3DS or PAN_ONLY. CRYPTOGRAM_3DS typically requires no further action if the user has already authenticated with their bank, while PAN_ONLY often necessitates additional authentication like 3D Secure. Merchants can specify supported authentication methods using the allowedAuthMethods parameter. When processing payments with Google Pay, the assuranceDetails property in the decrypted payment token indicates whether further authentication is needed, with step-up generally required unless both cardHolderAuthenticated and accountVerified are true. Merchants in the European Economic Area should also consider Strong Customer Authentication requirements, and they can follow @GooglePayDevs for updates and support.

Trends Found in this Post

No tracked trend matches for this post yet.

Use This Data

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.