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

# Retrieve Payment

> Retrieve detailed information about a specific payment transaction by its ID.

Retrieve detailed information about a specific payment transaction by its ID.

## Overview

This endpoint returns comprehensive details about a single payment transaction, including all metadata, status information, and transaction history.

## Path Parameters

<ParamField path="id" type="string" required>
  Payment transaction UUID
</ParamField>

## Response

<ResponseField name="data" type="object">
  Complete payment transaction object including:

  * `id`: Payment transaction ID
  * `reference`: Payment reference number
  * `amount`: Payment amount
  * `currency`: Currency code
  * `description`: Payment description
  * `status`: Current payment status
  * `type`: Transaction type (debit/credit)
  * `sub_type`: Transaction sub-type
  * `category`: Transaction category
  * `sub_category`: Transaction sub-category
  * `channel`: Payment channel used
  * `tags`: Transaction tags
  * `notes`: Additional notes
  * `is_reversed`: Whether payment was reversed
  * `is_completed`: Whether payment is completed
  * `transaction_date`: When transaction occurred
  * `created_at`: Creation timestamp
  * `updated_at`: Last update timestamp
</ResponseField>


## OpenAPI

````yaml GET /payments/{id}
openapi: 3.0.0
info:
  title: Pooler Developer API
  description: >-
    Comprehensive API documentation for Pooler payment and financial services
    platform
  version: 1.0.0
servers:
  - url: https://api.usepooler.com
    description: Production server
  - url: https://sandbox.usepooler.com
    description: Sandbox server
security:
  - bearerAuth: []
paths:
  /payments/{id}:
    get:
      tags:
        - Payments
      summary: Retrieve Payment
      description: >-
        Retrieve detailed information about a specific payment transaction by
        its ID.
      operationId: retrievePayment
      parameters:
        - name: id
          in: path
          required: true
          description: Payment transaction ID
          schema:
            type: string
            format: uuid
      responses:
        '200':
          description: Payment retrieved successfully
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/PaymentResponse'
components:
  schemas:
    PaymentResponse:
      type: object
      properties:
        success:
          type: boolean
        message:
          type: string
        stan:
          type: string
          format: uuid
        data:
          $ref: '#/components/schemas/Payment'
    Payment:
      type: object
      properties:
        id:
          type: string
          format: uuid
        reference:
          type: string
        status:
          type: string
          enum:
            - pending
            - completed
            - failed
        amount:
          type: string
        currency:
          type: string
        description:
          type: string
        type:
          type: string
        sub_type:
          type: string
        category:
          type: string
        transaction_date:
          type: string
          format: date-time
        tags:
          type: string
        is_reversed:
          type: boolean
        is_completed:
          type: boolean
        channel:
          type: string
        notes:
          type: string
        created_at:
          type: string
          format: date-time
        updated_at:
          type: string
          format: date-time
  securitySchemes:
    bearerAuth:
      type: http
      scheme: bearer
      bearerFormat: JWT
      description: >-
        Bearer token authentication. Include your API key in the Authorization
        header as: Bearer {your_api_key}

````