> ## Documentation Index
> Fetch the complete documentation index at: https://yn-c9bb3266.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Create Recipient

> Creates a new payout recipient.



## OpenAPI

````yaml POST /v1/recipients
openapi: 3.1.0
info:
  title: Yuno Payments API
  description: >-
    Yuno payment orchestration platform — unified REST API for payments,
    checkout sessions, customers, payment methods, subscriptions, payouts,
    marketplace transfers, and banking connectivity across Latin America.
  version: 1.0.0
  contact:
    name: Yuno Support
    email: support@y.uno
    url: https://docs.y.uno
  license:
    name: Proprietary
    url: https://y.uno
servers:
  - url: https://api-sandbox.y.uno
    description: Sandbox
  - url: https://api.y.uno
    description: Production
security:
  - publicApiKey: []
    privateSecretKey: []
paths:
  /v1/recipients:
    post:
      tags:
        - Recipients
      summary: Create recipient
      description: Creates a new payout recipient.
      operationId: createRecipient
      requestBody:
        required: true
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/RecipientRequest'
            example:
              merchant_recipient_id: seller-001
              country: BR
              name: Carlos Oliveira
              email: carlos@example.com
              document:
                document_type: CPF
                document_number: '98765432100'
              bank_account:
                bank_code: '001'
                account_number: 12345-6
                account_type: CHECKING
      responses:
        '201':
          description: Recipient created successfully
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Recipient'
              example:
                id: d1e2f3a4-b5c6-7d8e-9f0a-1b2c3d4e5f6a
                merchant_recipient_id: seller-001
                country: BR
                name: Carlos Oliveira
                email: carlos@example.com
                document:
                  document_type: CPF
                  document_number: '98765432100'
                bank_account:
                  bank_code: '001'
                  account_number: 12345-6
                  account_type: CHECKING
                created_at: '2026-03-01T09:00:00.000Z'
        '400':
          description: Invalid request
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
components:
  schemas:
    RecipientRequest:
      type: object
      required:
        - merchant_recipient_id
        - country
      properties:
        merchant_recipient_id:
          type: string
          description: Your internal recipient identifier
          example: seller-001
        country:
          type: string
          description: ISO 3166-1 alpha-2 country code
          pattern: ^[A-Z]{2}$
          example: BR
        name:
          type: string
          description: Recipient name
          example: Carlos Oliveira
        email:
          type: string
          format: email
          example: carlos@example.com
        document:
          $ref: '#/components/schemas/CustomerDocument'
        bank_account:
          type: object
          properties:
            bank_code:
              type: string
              example: '001'
            account_number:
              type: string
              example: 12345-6
            account_type:
              type: string
              enum:
                - CHECKING
                - SAVINGS
              example: CHECKING
      example:
        merchant_recipient_id: seller-001
        country: BR
        name: Carlos Oliveira
        email: carlos@example.com
        document:
          document_type: CPF
          document_number: '98765432100'
        bank_account:
          bank_code: '001'
          account_number: 12345-6
          account_type: CHECKING
    Recipient:
      type: object
      properties:
        id:
          type: string
          format: uuid
          example: d1e2f3a4-b5c6-7d8e-9f0a-1b2c3d4e5f6a
        merchant_recipient_id:
          type: string
          example: seller-001
        country:
          type: string
          example: BR
        name:
          type: string
          example: Carlos Oliveira
        email:
          type: string
          format: email
          example: carlos@example.com
        document:
          $ref: '#/components/schemas/CustomerDocument'
        bank_account:
          type: object
          properties:
            bank_code:
              type: string
              example: '001'
            account_number:
              type: string
              example: 12345-6
            account_type:
              type: string
              example: CHECKING
        created_at:
          type: string
          format: date-time
          example: '2026-03-01T09:00:00.000Z'
      example:
        id: d1e2f3a4-b5c6-7d8e-9f0a-1b2c3d4e5f6a
        merchant_recipient_id: seller-001
        country: BR
        name: Carlos Oliveira
        email: carlos@example.com
        document:
          document_type: CPF
          document_number: '98765432100'
        bank_account:
          bank_code: '001'
          account_number: 12345-6
          account_type: CHECKING
        created_at: '2026-03-01T09:00:00.000Z'
    Error:
      type: object
      description: >-
        Standard error envelope returned by every Yuno service for any 4xx or
        5xx response. Top level. `code` is a stable SCREAMING_SNAKE_CASE
        identifier. `messages` is always an array of strings, even when there is
        only one entry. There is no `error` wrapper, no singular `message`, no
        `type`, no `details`. See the Error handling guide for the full code
        catalog.
      required:
        - code
        - messages
      properties:
        code:
          type: string
          description: >-
            Stable, machine readable identifier. Branch on this in your client.
            Common values include `BAD_REQUEST`, `VALIDATION_ERROR`,
            `INVALID_REQUEST`, `UNAUTHORIZED`, `FORBIDDEN`, `NOT_FOUND`,
            `TOO_MANY_REQUESTS`, `INTERNAL_ERROR`, `BAD_GATEWAY`,
            `SERVICE_UNAVAILABLE`, plus business codes like
            `CUSTOMER_ID_DUPLICATED`, `RECIPIENT_NOT_FOUND`, `INVALID_STATE`,
            and the `PROVIDER_*` family for downstream provider errors.
          example: VALIDATION_ERROR
        messages:
          type: array
          description: >-
            Human readable details. Validation errors put one entry per failed
            field, formatted `"fieldName message"`.
          items:
            type: string
          example:
            - merchant_customer_id must not be blank
      example:
        code: VALIDATION_ERROR
        messages:
          - amount must be greater than 0
          - country must not be blank
    CustomerDocument:
      type: object
      description: >-
        Customer's identification document. Both fields are required when the
        `document` object is sent. Yuno does not enforce a fixed enum on
        `document_type`; pass the local code expected by the destination payment
        method.
      required:
        - document_type
        - document_number
      properties:
        document_type:
          type: string
          minLength: 3
          maxLength: 6
          description: >-
            Type of identification document. Common values per country: Brazil —
            `CPF` (individuals), `CNPJ` (businesses); Colombia — `CC`, `CE`,
            `NIT`, `PP`, `TI`; Mexico — `CURP`, `RFC`; Argentina — `DNI`,
            `CUIT`, `CUIL`; Chile — `RUT`, `RUN`; Peru — `DNI`, `RUC`; Uruguay —
            `CI`, `RUT`; United States — `SSN`; international — `PASSPORT`. See
            the [Country Reference](/reference/country-reference) for the
            document required by each payment method.
          example: CPF
        document_number:
          type: string
          minLength: 3
          maxLength: 40
          description: >-
            Document number, digits only, no separators or formatting. Length
            depends on the document type (CPF: 11 digits, CNPJ: 14 digits, CURP:
            18 chars, RFC: 12-13 chars, DNI-AR: 7-8 digits).
          example: '12345678901'
      example:
        document_type: CPF
        document_number: '12345678901'
  securitySchemes:
    publicApiKey:
      type: apiKey
      in: header
      name: public-api-key
      description: Your public API key from the Yuno Dashboard
    privateSecretKey:
      type: apiKey
      in: header
      name: private-secret-key
      description: Your private secret key (server-side only)

````