> For the complete documentation index, see [llms.txt](https://idthrivo.gitbook.io/thrivosign-remote-signing-solution/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://idthrivo.gitbook.io/thrivosign-remote-signing-solution/thrivosign-remote-signing-solution-t-rss-documentation/introduction/solution-detail.md). # Solution Detail After the successful setup of the system, ThrivoSign RSSP solution empowers signers to initiate digitally signed transactions through intuitive signing interfaces like SSA, SIC, and the Relying Party app integrated with the RSSP REST API. Typically, signatories engage with the Relying Party via a browser. To sign a document, signers utilize the ThrivoSign app on a pre-registered mobile device, ensuring secure authentication for server-side digital signing using SAP (Signature Activation Protocol). For remote digital signing authentication, the mobile device must be pre-registered in association with the customer account. **Digital signature authentication follows SCAL#2 (Sole Control Assurance Level 2) as per EN 419 241-1.** Throughout the remote digital signing process, signers are prompted to launch the ThrivoSign mobile app to receive and authenticate authentication requests. Upon successful authentication, the ThrivoSign app digitally signs an authentication response JSON string using the authentication key stored in SE. The signed authentication response string is referred to as Signature Activation Data (SAD). The ThrivoSign service ensures that remote signers maintain control over the user signing key at the **SCAL2** level, adhering to the **EN 419 protocol 241-1:2018**. This ensures that signing tasks are authenticated and executed by the ThrivoSign app. --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://idthrivo.gitbook.io/thrivosign-remote-signing-solution/thrivosign-remote-signing-solution-t-rss-documentation/introduction/solution-detail.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.