3D Secure has changed considerably since its earliest implementations.<\/p>\n
Authentication requirements have evolved. Cardholder expectations have changed. Issuers are managing increasingly complex fraud and payment environments, while technology teams are under pressure to modernise infrastructure and reduce dependency on legacy platforms.<\/p>\n
An Access Control Server needs to evolve with those requirements.<\/p>\n
That is why we have continued to develop ActiveAccess<\/strong>, GPayments\u2019 Access Control Server for issuer-side 3D Secure authentication.<\/p>\n The latest ActiveAccess brings together support for evolving EMV 3DS requirements, modern technology architecture, greater operational control and improved visibility across the authentication environment.<\/p>\n The role of the ACS has expanded beyond simply supporting a 3D Secure authentication request.<\/p>\n Issuers increasingly need to manage multiple authentication approaches, determine when additional cardholder verification is appropriate, understand authentication outcomes and maintain experiences that balance security with customer friction.<\/p>\n At the same time, EMV 3DS specifications and card scheme requirements continue to develop.<\/p>\n ActiveAccess is designed to support the latest applicable EMV 3DS 2.3.x requirements alongside existing 2.1 and 2.2 environments, giving issuers a platform built with continued authentication evolution in mind.<\/p>\n Payment authentication may happen in seconds, but the infrastructure behind it needs to operate reliably at enterprise scale.<\/p>\n Older ACS environments can depend on technology stacks that are increasingly difficult to maintain, integrate into modern delivery environments or align with current infrastructure strategies.<\/p>\n ActiveAccess has been modernised from the ground up.<\/p>\n The platform is built on Java 21<\/strong> and supports a simplified application architecture, container-ready deployment and flexible database options including PostgreSQL and Oracle.<\/p>\n For technology teams, this means an ACS architecture that can fit more naturally into contemporary infrastructure and CI\/CD environments.<\/p>\n Modernising the ACS is not simply a technology exercise. Reducing infrastructure complexity can also make it easier for organisations to operate and maintain a critical component of their payment authentication environment.<\/p>\n The technology underneath ActiveAccess is only one part of the change.<\/p>\n A major focus has also been placed on how teams manage authentication day to day.<\/p>\n ActiveAccess introduces a modern administration experience designed to move more configuration and management into the hands of the teams responsible for authentication.<\/p>\n For example, challenge experiences can be configured through a structured interface rather than relying solely on file-based processes.<\/p>\n Teams can manage elements such as challenge messaging, authentication templates and issuer-specific experiences while previewing how those changes will appear across different screen sizes.<\/p>\n Authentication page flows can also be configured around requirements such as:<\/p>\n This gives organisations greater flexibility over how authentication experiences are constructed and managed.<\/p>\n Understanding what is happening across the authentication environment is critical to managing it effectively.<\/p>\n ActiveAccess provides interactive dashboard capabilities that give teams visibility across areas including:<\/p>\n Users can explore activity across different time periods and issuer environments, providing a clearer operational view of how authentication is being handled.<\/p>\n The objective is simple: make authentication activity easier to understand and give teams better information when investigating trends or operational issues.<\/p>\n There is no single authentication method that is appropriate for every transaction.<\/p>\n ActiveAccess supports a range of authentication approaches designed to give issuers greater flexibility over how cardholders are verified.<\/p>\n These include risk-based authentication, OTP, out-of-band authentication, decoupled authentication and modern authentication capabilities aligned with evolving EMV 3DS requirements.<\/p>\n Configurable risk logic can also be used to help determine whether transactions proceed frictionlessly, require additional cardholder authentication or should be rejected based on the issuer’s authentication strategy.<\/p>\n As new authentication approaches continue to emerge, this flexibility becomes increasingly important.<\/p>\n ActiveAccess has evolved because the environment around issuer authentication has evolved.<\/p>\n For GPayments, supporting the latest specifications is only one part of that evolution.<\/p>\n A modern ACS also needs to consider the infrastructure supporting authentication, the teams operating it, the experience presented to cardholders and the information available when authentication decisions need to be understood.<\/p>\n ActiveAccess brings those requirements together in a modern platform designed for issuer authentication today and as 3D Secure continues to develop.<\/p>\n3D Secure continues to evolve<\/h2>\n
Modernising the infrastructure behind authentication<\/h2>\n
Giving authentication teams greater control<\/h2>\n
\n
Greater visibility into authentication activity<\/h2>\n
\n
Supporting flexible authentication strategies<\/h2>\n
Built for what comes next<\/h2>\n
Modern authentication starts with a modern ACS.<\/h3>\n