> ## Documentation Index
> Fetch the complete documentation index at: https://docs.rc.cleverhub.co/llms.txt
> Use this file to discover all available pages before exploring further.

# Create KYC for Beneficiary

> Submit KYC (Know Your Customer) documentation for a beneficiary before proceeding with a payout. The KYC submission helps verify the beneficiary’s identity. The email provided will be used for approving the payout process in subsequent steps.




## OpenAPI

````yaml /api/openapi/v1-reference.yaml post /v1/payouts/create_kyc
openapi: 3.0.3
info:
  title: Payment APIs (AUD only)
  description: >-
    ## Introduction

    The Payment API Solution (AUD) offers developers a comprehensive suite of
    API services to build innovative AUD payment solutions efficiently. These
    APIs enable seamless transactions using various payment methods and
    functionalities, ensuring a robust, reliable, and scalable payment
    infrastructure tailored for the Australian market.

    ### Key Features

    - **Payment Methods**:
      - **Payment Link**: Supports payments via card and PayID.
      - **PayID**: Provides instant payments using a unique identifier.
      - **PayTo**: Enables scheduled or recurring payments.
      - **BSB/Account Number**: Allows direct bank transfers.
      - **Payout**: Manage payouts to designated accounts.

    - **Additional Functionalities**:
      - **Balance Management**: Real-time balance inquiries and updates.
      - **Reporting Services**: Generate detailed transaction and payment reports.

    This documentation provides detailed guidance for integrating these
    capabilities into your application.
  termsOfService: https://helloclever.co/terms
  contact:
    email: support@helloclever.co
  version: 1.0.11
servers:
  - url: https://api.cleverhub.co/api
    description: Sandbox Environment
  - url: https://api-merchant.helloclever.co/api
    description: Production Environment
security: []
paths:
  /v1/payouts/create_kyc:
    post:
      tags:
        - AUD Payout
      summary: Create KYC for Beneficiary
      description: >
        Submit KYC (Know Your Customer) documentation for a beneficiary before
        proceeding with a payout. The KYC submission helps verify the
        beneficiary’s identity. The email provided will be used for approving
        the payout process in subsequent steps.
      requestBody:
        required: true
        content:
          multipart/form-data:
            schema:
              type: object
              required:
                - email
                - id_doc_type
                - id_doc_front_side
                - id_doc_back_side
                - selfie
              properties:
                email:
                  type: string
                  description: >
                    Email address associated with the beneficiary’s KYC process.
                    This email will be used to approve the payout processing
                    later.
                  example: beneficiary@example.com
                id_doc_type:
                  type: string
                  enum:
                    - id_card
                    - passport
                  description: >
                    Type of ID document provided for KYC verification. Options
                    include:

                    - **id_card**: National identification card.

                    - **passport**: Passport document.
                  example: passport
                id_doc_front_side:
                  type: string
                  format: binary
                  description: |
                    Front side of the ID document. The file format must be PDF.
                id_doc_back_side:
                  type: string
                  format: binary
                  description: |
                    Back side of the ID document. The file format must be PDF.
                selfie:
                  type: string
                  format: binary
                  description: >
                    A selfie image of the beneficiary for identity verification.
                    The file format must be JPEG.
      responses:
        '200':
          description: KYC submission was successful.
          content:
            application/json:
              schema:
                type: object
                properties:
                  status:
                    type: string
                    description: Indicates the status of the KYC submission.
                    example: OK
        '400':
          description: Bad Request
        '401':
          description: Unauthorized
        '422':
          description: Unprocessable Entity

````

## Related topics

- [Know Your Customer (KYC)](/platform-overview/compliance/kyc.md)
- [Create Contact](/api/contact/create-contact.md)
- [Create a Payin](/api/payin/create-a-payin.md)