> 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/4.-developer-and-payment-engine/waas/payout-external-verification.md).
# Payout External Verification
Payout External Verification adds an additional approval layer controlled by the customer's business system before a payout request (Wallet Payout and Sub-Address Payout) enters the Cregis approval workflow\.When this feature is enabled, payout requests are not processed immediately after they are submitted. Instead, Cregis sends the payout request to the customer's configured external verification system through a callback API. The customer can then review the request based on their own business rules, risk control policies, or approval workflow, and submit the verification result back to Cregis.Cregis processes the payout request according to the returned verification result:
* **Approved (ok):** The payout request proceeds with the subsequent approval, signing, and blockchain transaction process.
* **Rejected (deny):** The payout request is terminated, and no signing or blockchain broadcasting will be performed.
By integrating Payout External Verification with internal approval, risk management, or compliance systems, enterprises can implement customized payout approval workflows, strengthen fund security, and enhance risk control capabilities.
## **Enable Payout External Verification**
Log in to the Cregis, then navigate to **WaaS > Settings > Callback Setting**. Click **Enable** under Payout External Verification.
In the confirmation dialog, click **Confirm**.
On the **Configure Callback URL** page, enter or paste the callback URL that will receive payout verification requests, then click **Test Connection**.
The system will attempt to connect to the specified callback URL. If the test is successful, the message **"Connection test successful. The server responded normally."** will be displayed. Click **OK**.
Complete identity verification. Payout External Verification will then be enabled successfully.
**Edit Callback URL**
Log in to the Cregis, then navigate to **WaaS > Settings > Callback Setting**. Click **Edit** under Payout External Verification.
On the **Configure Callback URL** page, enter or paste the new callback URL, then click **Test Connection**.
The system will attempt to connect to the specified callback URL. If the test is successful, the message **"Connection test successful. The server responded normally."** will be displayed. Click **OK**.
Complete identity verification, then click **Confirm**. The callback URL will be updated successfully.
**Disable Payout External Verification**
Log in to the Cregis, then navigate to **WaaS > Settings > Callback Setting**. Click **Disable** under Payout External Verification.
In the confirmation dialog, click **Confirm**.
Complete identity verification, then click **Confirm**. Payout External Verification will be disabled successfully.
---
# 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/4.-developer-and-payment-engine/waas/payout-external-verification.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.
