> ## 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 Customer Session

> Creates a new customer session for SDK initialization, enabling one-click payments and saved payment methods.

Creates a session for enrolling payment methods without initiating a payment.


## OpenAPI

````yaml POST /v1/customer-sessions
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/customer-sessions:
    post:
      tags:
        - Customer Sessions
      summary: Create customer session
      description: >-
        Creates a new customer session for SDK initialization, enabling
        one-click payments and saved payment methods.
      operationId: createCustomerSession
      requestBody:
        required: true
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/CustomerSessionRequest'
            example:
              customer_id: c9d0e1f2-3a4b-5c6d-7e8f-9a0b1c2d3e4f
      responses:
        '201':
          description: Customer session created successfully
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/CustomerSession'
        '400':
          description: Invalid request
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
components:
  schemas:
    CustomerSessionRequest:
      type: object
      required:
        - customer_id
      properties:
        customer_id:
          type: string
          format: uuid
          description: The customer to create a session for
          example: c9d0e1f2-3a4b-5c6d-7e8f-9a0b1c2d3e4f
        merchant_customer_id:
          type: string
          description: 'Alternative: your internal customer identifier'
          example: cust-internal-001
      example:
        customer_id: c9d0e1f2-3a4b-5c6d-7e8f-9a0b1c2d3e4f
    CustomerSession:
      type: object
      properties:
        id:
          type: string
          format: uuid
          example: cs_a1b2c3d4-e5f6-7890-abcd-ef1234567890
        customer_id:
          type: string
          format: uuid
          example: c9d0e1f2-3a4b-5c6d-7e8f-9a0b1c2d3e4f
        status:
          type: string
          enum:
            - ACTIVE
            - EXPIRED
          example: ACTIVE
        sdk_token:
          type: string
          description: Token for SDK initialization
          example: sdk_tok_abc123def456
        expires_at:
          type: string
          format: date-time
          example: '2026-03-01T15:30:00.000Z'
        created_at:
          type: string
          format: date-time
          example: '2026-03-01T14:30:00.000Z'
      example:
        id: cs_a1b2c3d4-e5f6-7890-abcd-ef1234567890
        customer_id: c9d0e1f2-3a4b-5c6d-7e8f-9a0b1c2d3e4f
        status: ACTIVE
        sdk_token: sdk_tok_abc123def456
        expires_at: '2026-03-01T15:30:00.000Z'
        created_at: '2026-03-01T14:30: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
  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)

````