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

# Get payment concept

> Returns a single payment concept by id.



## OpenAPI

````yaml /openapi.yaml get /v1/payment-concepts/{id}
openapi: 3.0.3
info:
  title: Quentli REST API
  version: 1.0.0
  description: OpenAPI spec for Quentli REST endpoints.
servers:
  - url: https://api.quentli.com
    description: Production API
  - url: https://api.staging.quentli.com
    description: Staging API for production-like validation
  - url: https://api.demo.quentli.com
    description: Demo API hostname served by staging
security:
  - organizationApiKey: []
tags:
  - name: Auth
  - name: Billing
  - name: Catalog
  - name: Customers
  - name: Invoices
  - name: Payment Methods
  - name: Payment Sessions
  - name: Payments
  - name: Subscriptions
  - name: Tax Invoices
  - name: Webhooks
paths:
  /v1/payment-concepts/{id}:
    get:
      tags:
        - Catalog
      summary: Get payment concept
      description: Returns a single payment concept by id.
      operationId: payment_concepts_get_by_id
      parameters:
        - schema:
            type: string
            description: Identifier of the payment concept.
          required: true
          description: Identifier of the payment concept.
          name: id
          in: path
      responses:
        '200':
          description: Payment concept details
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/GetPaymentConceptResponse'
        '401':
          description: Authentication required
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/UserError'
        '403':
          description: Permission denied
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/UserError'
        '404':
          description: Payment concept not found
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/UserError'
components:
  schemas:
    GetPaymentConceptResponse:
      type: object
      nullable: true
      properties:
        id:
          type: string
          description: Unique identifier of the payment concept.
          example: pc_1234567890abcdefghij
        createdAt:
          anyOf:
            - type: string
              description: Date string
            - type: string
              format: date-time
              description: Date object
          description: When the concept was created.
          example: '2025-01-01T00:00:00.000Z'
        updatedAt:
          anyOf:
            - type: string
              description: Date string
            - type: string
              format: date-time
              description: Date object
          description: When the concept was last updated.
          example: '2025-01-01T00:00:00.000Z'
        displayName:
          type: string
          description: Name of the product or service shown to customers.
          example: Colegiatura
        description:
          type: string
          nullable: true
          description: Optional longer description of the product or service.
          example: Colegiatura mensual de preparatoria
        amount:
          type: number
          description: Unit price in minor currency units (e.g. cents).
          example: 150000
        currency:
          type: string
          description: ISO 4217 currency code.
          example: MXN
        organizationId:
          type: string
          description: Identifier of the owning organization.
          example: org_1234567890abcdefghij
        active:
          type: boolean
          description: Whether this concept is currently available for use.
          example: true
        sku:
          type: string
          nullable: true
          description: Optional SKU for internal identification.
          example: COL-PREP-001
        recurrentDetailId:
          type: string
          nullable: true
          description: Identifier of the recurrence configuration, if applicable.
          example: null
        amountEditable:
          type: boolean
          description: Whether customers can customize the price.
          example: false
        quantityEditable:
          type: boolean
          description: Whether customers can customize the quantity.
          example: false
        archivedAt:
          anyOf:
            - type: string
              description: Date string
            - type: string
              format: date-time
              description: Date object
            - nullable: true
          description: Date and time when the concept was archived, if any.
          example: null
        oneOff:
          type: boolean
          description: Whether this concept is a one-time custom charge.
          example: false
        groupId:
          type: string
          nullable: true
          description: Identifier of the group this concept belongs to, if any.
          example: null
        recurrentDetail:
          type: object
          nullable: true
          properties:
            collectionInterval:
              type: string
              enum:
                - DAY
                - WEEK
                - FORTNIGHT
                - MONTH
                - YEAR
              description: Time interval unit for recurring charges.
              example: MONTH
            chargeEach:
              type: number
              description: Number of intervals between charges.
              example: 1
            toleranceDays:
              type: number
              nullable: true
              description: Grace days after the due date before the invoice expires.
              example: 5
          required:
            - collectionInterval
            - chargeEach
          description: Recurrence configuration when the concept is a recurring charge.
          example: null
      required:
        - id
        - createdAt
        - updatedAt
        - displayName
        - description
        - amount
        - currency
        - organizationId
        - active
        - sku
        - recurrentDetailId
        - amountEditable
        - quantityEditable
        - archivedAt
        - oneOff
        - groupId
      description: Payment concept details. Returns null if not found.
    UserError:
      type: object
      properties:
        error:
          type: object
          properties:
            message:
              type: string
          required:
            - message
      required:
        - error
      additionalProperties: false
      description: Standard user-facing error response envelope.
  securitySchemes:
    organizationApiKey:
      type: http
      scheme: bearer
      description: 'Organization API key using `Authorization: Bearer sk_...`.'

````