> For the complete documentation index, see [llms.txt](https://docs.payments.thalescloud.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.payments.thalescloud.io/nfc-wallet-sdk-android/security-and-privacy/rasp-compatibility-notes.md).

# RASP compatibility notes

## Overview

NFC Wallet SDK includes a RASP (runtime application self-protection) component.

Some third-party security libraries can conflict with it. These conflicts can cause SDK errors, crashes, or payment flow hangs.

## Known incompatibilities

### Child process tracing the parent process

If a module or library spawns a child process, and that child process traces the parent process, NFC Wallet SDK can detect a conflict and return `DEVICE_SUSPICIOUS`.

Known examples:

* OneSpan
* DexGuard (DebugBlocker)
* AppDome
* Promon

### SIGTRAP handler overrides

If a module or library registers or overrides the SIGTRAP handler after NFC Wallet SDK initialization, your **digital wallet application** can crash or hang during payment flows.

## Recommendations

1. Avoid combining NFC Wallet SDK with third-party RASP providers when possible.
2. If you must use a library that registers SIGTRAP handlers, initialize it **before** initializing NFC Wallet SDK.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.payments.thalescloud.io/nfc-wallet-sdk-android/security-and-privacy/rasp-compatibility-notes.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.