Error Reporting & Cybersecurity Measures

Error Reporting

The SDK utilizes Sentry for error logging and reporting, with initialization based on the configuration provided by SDK Studio.

Since the SDK is embedded within the merchant's application, conflicts may arise if Sentry is also integrated into the app. To prevent such conflicts, Sentry can be disabled within the Checkout SDK by setting the is_enabled flag to false in the configuration.

Cyber Security Measures

Rooting Detection

The SDK prevents execution on rooted devices.

To enforce this restriction, rooting checks are performed during SDK initialization. If a device is detected as rooted, a modal alert dialog is displayed, providing an explanation. The message shown is as follows:

This device is not secure for payments. Transactions are blocked for security reasons.

After dismissing the alert, the app crashes unexpectedly

Checkout.init function needs to be called in a coroutine.

Screen Capture Prevention

The SDK is designed to protect sensitive data by restricting screen capture functionalities. These restrictions apply to the entire Activity that contains the SDK and operate as follows:

• Screenshot Attempts: If a user attempts to take a screenshot, a toast message will appear stating: "This app doesn’t allow screenshots."

• Screen Recording After SDK Initialization: If screen recording is initiated after the SDK has been initialized, the following toast message is displayed: "Can't record screen due to security policy."

• Screen Recording Before SDK Initialization: If screen recording begins before the SDK is initialized, the entire Activity containing the SDK will appear as a black screen in the recorded video.