Two transactions can involve the same cardholder and merchant yet present very different authentication information. A browser checkout, an in-app purchase and a 3DS Requestor-Initiated (3RI) request each operate within different interaction conditions.
This raises an important issuer question: should the decision strategy acknowledge what each channel can – and cannot – tell the issuer? A consistent security objective does not require identical handling of every transaction.
The three channels are not interchangeable
In a browser flow, the issuer may receive information from the merchant and browser environment, subject to the protocol and implementation. In an app flow, 3DS SDK functionality can support relevant device and authentication data collection.
A 3RI request is different because the cardholder may not be participating in an active checkout at all. That affects the options for interactive authentication and the relevance of prior transaction information.
The EMV 3DS framework provides defined messages and capabilities for these channels. It does not imply that every channel contains the same signals or supports the same challenge journey.
Make data completeness part of the decision
A risk strategy should know which data elements it expected to receive, which were actually present and whether missing information materially affects the conclusion.
A device-related field missing from a browser request may have a different explanation from missing prior-authentication information in a 3RI request. Treating every omission as identical can create unnecessary challenges or misleading confidence.
The response should be governed: can the issuer proceed with available information, request additional authentication through a supported method or return an appropriate outcome?
Consider channel-specific failure modes
Browser flows may encounter unsupported features, abandoned challenges or interruptions. App flows may involve SDK integration issues, device changes or user-interface problems. 3RI flows may depend on supported prior-authentication details and, where challenge is required, decoupled authentication capability.
Testing needs to cover those differences rather than applying one generic checklist across all channels. A platform might process a standard browser transaction correctly while failing to handle an important 3RI exception.
Example: similar payment, different evidence
Imagine a customer paying for a service in an app, then later being charged under an agreed recurring arrangement. During the first transaction, the customer is present and the app may support relevant device and interaction data. During the later 3RI request, the customer is absent and the issuer instead considers appropriate merchant and prior-authentication context.
Neither interaction should be judged solely on whether the card number and merchant are the same. The available data and appropriate authentication options differ.
A decision framework should record the channel and the reasons for an action, not just the final challenge result.
How Decision AI could improve operational understanding
A future decision-support capability might help issuers classify failures by channel, explain which evidence was missing or reveal patterns where one channel experiences disproportionately high challenge failures.
Such analytics could support improvements to policy and implementation, but would not be an authority to override the EMV 3DS specifications or issuer controls.
The critical safeguards are clear source data, version-aware interpretation and human ownership of policy. An AI system must not claim that a transaction was safe because it lacked a signal the channel was never designed to provide.
Compare performance fairly
Track challenge rates, authentication outcomes, timeouts, abandonment and error patterns separately by channel, device eligibility and relevant transaction type.
Also compare results after changes to the issuer’s policy or technical environment. If a channel shows a higher rate of unsuccessful authentication, investigate whether the cause is genuine risk, incomplete data, implementation quality or a customer-experience issue.
EMVCo’s 3DS overview describes the protocol’s support for browser- and app-based implementation and different authentication options.
Consistent policy, context-specific execution
The best issuer strategy can apply consistent risk principles while allowing channel-specific decisions. That is more reliable than forcing browser, app and 3RI transactions into one identical experience.
Frequently asked questions
Is 3RI just another browser transaction?
No. It is a distinct device channel used for eligible requestor-initiated authentication scenarios.
Does missing device data always mean a transaction is high risk?
No. The meaning of absent data depends on the channel, expected information and broader transaction context.
Take the next step
Explore GPayments ActiveAccess and discuss how your organisation can support robust issuer decisions across browser, app and 3RI authentication journeys.
Explore GPayments ActiveAccess
