# KYC Verification for Payout

After successfully creating a new receiver using the Create New Receiver API, the system will automatically send a KYC Verification for Payments email to the email address provided in the request.

What Happens Next?

1. Email Notification: The receiver will receive an email containing a secure link to complete their KYC (Know Your Customer) verification.
2. Identity Confirmation: The receiver must click the link in the email to confirm their personal details.
3. Document Upload: As part of the verification process, the receiver will be required to upload the necessary identification documents.
4. Verification Review: Once the receiver submits their details and documents, the system will review them for compliance before Subaccount can create payout for them.<br>

Important Notes:

• The verification link is time-sensitive and will expire after a set period.

• If the receiver does not complete the KYC verification, their account KYC status will remain pending for payouts until verification is completed.

• If the receiver does not receive the email, they should check their spam folder or request a new verification email.

Webhook Notification: [receiverKycUpdate](https://docs.payswiftly.io/payout-api/receiver/webhooks)

Once the receiver successfully completes their KYC verification, the system will trigger a receiverKycUpdate webhook notification. This allows Subaccount to be notified in real time when a receiver is fully verified and eligible for payouts.


---

# Agent Instructions: 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://docs.payswiftly.io/payout-api/receiver/kyc-verification-for-payout.md?ask=<question>
```

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.
