> For the complete documentation index, see [llms.txt](https://support.cregis.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.cregis.com/2.-transaction-and-account/tasks/signing.md). # Signing Once a transaction completes the necessary approval process, it enters the signing stage. When a transaction meets the signing conditions and the current account possesses signing permissions, it is routed to Tasks > Signatures. Signers can sign or reject the transaction. Cregis supports both single-transaction signing and batch signing to help teams process pending transactions efficiently. Once signed, you can view the processed signature history under Tasks > Signed. **Important Notes** * If the recipient address is blacklisted, the transaction can only be rejected; signing is not permitted. * Batch signing only supports transactions of the same cryptocurrency in a single operation. Mixed-currency batch signing is not supported. * Batch signing only supports single-recipient transfers initiated by single-sig wallets and transactions initiated via API. * Transactions initiated by multi-sig wallets, Swap applications, or batch transfer functions do not support batch signing and must be processed individually. ## Single-Transaction Signing Because signing mechanisms differ between single-sig and multi-sig wallets, single-transaction signing is processed based on the outgoing wallet type. ### **Single‑Signature Wallet Transaction Signing** #### **Cregis Desktop** For transactions initiated by a single-sig wallet, only one person is required to execute the signature. Navigate to Tasks > Signature, locate the transaction, and click Review on the right side.
On the signature details page, review the transaction details and choose an action: * **Sign**: Authorize the transaction for execution. * **Reject**: Decline the transaction and stop the signing process. *(Note: If the recipient is a blacklisted address, you can only select Reject.)*
Click Sign. In the gas fee pop-up window, confirm the gas fee and click Confirm.
Perform identity verification: enter your Transaction Password and click Confirm.
After verification, you will be directed to the signing page. Upon successful signing, the system automatically broadcasts the transaction to the blockchain and displays a success prompt.
#### **Cregis Mobile** You can see pending signature items from the Home Page's To-Do section or from **Tasks**. Click on an item to view the transaction details. After confirming the signature, the estimated **Gas Fee** will be displayed.
After clicking Send, you need to complete the transaction password verification. The signing is then successfully completed.
### **Multi-Signature Wallet Transaction Signing** #### **Cregis Desktop** Multi-sig wallet transactions must satisfy the wallet's configured signature threshold. Navigate to Tasks > Signature, select the target multi-sig transaction, and click Review.
Review the transaction details and choose an action: * **Sign**: Authorize the transaction (requires participation from other signers). * **Reject**: Decline the transaction and stop the signing process. *(Note: If the recipient is blacklisted, you can only select Reject.)*
Click Sign, enter your Transaction Password, and click Confirm.
After verification, you will enter a waiting page. You must wait for other wallet members to join until the signature threshold is met.
Once the signature request is initiated, other online members of the wallet will receive an invitation notification.
They must click Multi-Sig Invitation, review the details, and click Join.
Joining members must complete identity verification by entering their Transaction Password and clicking Confirm.
When the number of participating members reaches the required threshold, the initiator clicks Confirm.
In the gas fee pop-up window, confirm the gas fee and click Confirm.
Enter the transaction signing page. Upon successful signing, the system automatically broadcasts the transaction to the blockchain and displays a success prompt.
#### **Cregis Mobile App** You can see pending signature items from the Home Page's To-Do section or from **Tasks**. Click on an item to view the transaction details. After confirming the signature, you will need to verify the transaction password.
Once verification is complete, you will enter the multi‑signature process. **If you are the initiator**, you can see which members have joined.\ When the number of joined multi‑signature signers reaches the minimum signing threshold, the signature initiator will see the estimated Gas Fee and can confirm it.
## Batch Signing Navigate to Tasks > Signature and click Batch Process in the top right corner.
Select the cryptocurrency you wish to batch sign and click View.
Select the target transactions and choose an action: * **Sign**: Authorize the execution of selected transactions. * **Reject**: Decline selected transactions and stop the signing process.
Click Sign. Review the summary statistics for the batch operation and click Confirm.
In the gas fee pop-up window, confirm the gas fee and click Confirm.
Enter your Transaction Password for identity verification and click Confirm.
Upon successful verification, the system executes the batch signing process.
When handling multiple pending signatures, use batch signing to process multiple transactions at once.

--- # 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://support.cregis.com/2.-transaction-and-account/tasks/signing.md?ask=&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.