Overview
This article explains what an event.transaction.linking_id is and clarifies whether it is a value that can be used to track a transaction and whether it is a value that can be set.
Applies To
- Strong Customer Authentication (SCA)
- Highly Regulated Identity (HRI)
- Post Login Action
Solution
To understand the linking_id attribute, it is best to understand its role in Strong Customer Authentication (SCA) and Highly Regulated Identity (HRI) as they relate to the purpose and use of this property.
- Strong Customer Authentication (SCA) is a regulatory requirement, primarily in Europe, designed to reduce fraud by requiring multi-factor authentication for transactions. It assesses various contextual factors, such as user behavior, location, and transaction details, to determine when additional authentication is necessary.
- Highly Regulated Identity (HRI) environments demand strict compliance with security regulations, ensuring that only authorized and authenticated individuals can access certain services or perform high-risk actions. Linking identity data with contextual information is crucial in maintaining this level of security.
With that in mind, here are the answers to specific questions about the ‘linking_id’ property:
- Is this a value that can be used to track a transaction?
Its primary purpose is to enforce security measures within highly regulated environments, ensuring that identities are appropriately linked to the context of each transaction for security purposes. The ‘linking_id’ property is not designed to track transactions directly.
- Is this a value that can be set?
The ‘linking_id’ is generally auto-generated and managed by the system, particularly in the context of Strong Customer Authentication (SCA). It is not typically intended to be set manually by users or developers but is rather handled internally to associate identities during critical processes.
Related References
For more detailed information on the attribute, please review the following articles: