Logs

The Logs page provides centralized visibility into system activity, security events, and technical issues across the platform.

It helps monitor user behavior, track authentication activity, detect potential security risks, and troubleshoot integration or system errors.

Overview

{[ { title: "System Visibility", icon: "eye", text: `The Logs page provides visibility into system activity, security events, and technical issues.` }, { title: "Key Benefits", icon: "check-circle", text: `Monitor user activity, track login attempts, identify security events, and detect SDK or API errors.` } ].map((c, i) => ( <Card key={i} title={c.title} icon={c.icon}> {c.text} </Card> ))}

📊
Logs provide operational insight and help identify both security-related and technical issues across the system.

Log Types

{[ { title: "Audit Logs", icon: "shield-alt", text: `Record user and system actions related to access and authentication.` }, { title: "Threat Logs", icon: "exclamation-triangle", text: `Provide technical insight into errors and issues during SDK or API usage.` } ].map((c, i) => ( <Card key={i} title={c.title} icon={c.icon}> {c.text} </Card> ))}

Audit Logs

Audit Logs record user and system actions related to authentication and access.

They are primarily used for monitoring system security, tracking user activity, and supporting compliance and auditing processes.

Audit logs capture events such as login attempts (successful and failed), along with relevant details including user identifiers, timestamps, and request origin when available.

🔐
Audit logs help track who accessed the system, when the access occurred, and whether the action was successful or failed.

Threat Logs

Threat Logs provide technical visibility into errors and issues that occur during SDK or API usage.

They are designed to help identify integration issues, troubleshoot unexpected failures, and monitor error trends across different versions and environments.

Threat logs capture information such as error type, error message, source (SDK or API), version details, and timestamps.

They are typically generated when system errors occur, such as failed API requests, SDK runtime issues, or validation failures during integration.

⚙️
Threat logs are essential for debugging and improving integration stability across applications.

Access & Permissions

{[ { title: "Role-Based Access", icon: "user-lock", text: "Access to logs depends on user role" }, { title: "Partner Access", icon: "users", text: "Partners typically have access to all logs under their scope" }, { title: "Merchant Access", icon: "store", text: "Merchants can view logs related to their own account" } ].map((c, i) => ( <Card key={i} title={c.title} icon={c.icon}> {c.text} </Card> ))}

🔐
Access to logs is restricted based on user roles and permissions.

Important Notes

📘
Key Notes

Logs are read-only and cannot be modified.

Historical logs are retained for auditing purposes.

Threat logs do not expose sensitive customer data.

Log timestamps reflect system time.