Shared Core Data Model
2 min
\<font color="#78b5c7">\</font> topic type concept purpose explain the shared core data concepts used across fraud‑related apis audience api integrators and client developers applies to apis used for fraud detection and risk assessment does not apply to data privacy apis, internal batch processing, or non‑request‑based integrations ’s fraud‑related apis are built on a shared core data model while this shared core is most fully expressed in the apis today, many of these concepts also appear across other apis that assess fraud risk at different stages of the customer lifecycle this shared model defines common concepts that apply regardless of industry, such as users, payments, items, devices, and locations the shared core ensures consistency across apis while allowing industry‑specific extensions where needed what the shared core includes the shared core typically captures information such as transaction identifiers and timestamps user and account context payment details item or order details device and network attributes address and location information these concepts appear across all industry apis, even though the specific fields or emphasis may vary benefits of a shared core using a shared core model provides several advantages consistency — similar concepts behave the same way across industries reusability — integrations can share logic across multiple industry apis extensibility — industry‑specific data can be added without redefining the entire model this approach allows you to think in terms of what happened rather than which api you are calling