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

# Get fleet payment transaction details

> Uses the same detail notation as the fleet dashboard and verifies that the transaction belongs to the authenticated fleet.



## OpenAPI

````yaml /api-reference/flo/flo-api-oas.json get /public/fleets/v1/transactions/{payment_transaction_id}
openapi: 3.0.3
info:
  title: FLO Partner API
  version: 1.0.0
  description: >
    Contract-first API for fleet partners building an operations dashboard, a
    driver app,

    or a backend-for-frontend integration with FLO.


    The API is fleet scoped. The API key identifies exactly one fleet; callers
    never send an

    internal fleet ID. Stable opaque public IDs must be persisted instead of
    database IDs,

    phone numbers, or registration numbers.


    Modules:

    - Stations: contracted charging stations, availability, and tariffs.

    - Drivers: app-charging driver onboarding and access management.

    - Vehicles: fleet vehicle registry for tracking and restriction
    configuration.

    - Payments: read-only fleet billing summary and payment transactions.

    - Sessions: asynchronous remote start, observation, and stop for fleet
    drivers.

    - Restrictions: connector-level access, time, and SOC policy.


    Mutation requests that create sessions or resources require an

    Idempotency-Key. Money uses integer paise. A 202 session response means

    the command was accepted for processing, not completed by the charge point.


    Compatibility caveats:

    - Restrictions are evaluated only when FLO can identify the session as
    belonging to the configured driver_id or vehicle_id.

    - SOC-based stop enforcement depends on the CPO/charger sending usable SOC
    updates for the active session.

    - Time-window and SOC stop enforcement depend on the CPO/charger supporting
    remote stop for the active session path.

    - Vehicle restrictions are stored even when FLO cannot yet identify the
    vehicle during charging; enforcement begins when vehicle identification
    becomes available.

    - If identity, SOC telemetry, or remote stop support is unavailable, FLO
    enforces only the supported parts of a restriction.
servers:
  - url: https://api.ionage.in
security:
  - ApiKeyAuth: []
tags:
  - name: Operators
    description: Charge point operators whose stations are contracted to the fleet.
  - name: Drivers
    description: App-charging driver onboarding and access management.
  - name: Vehicles
    description: Fleet vehicle registry for tracking and restriction configuration.
  - name: Restrictions
    description: Connector-level access, time, and SOC policy.
  - name: Stations
    description: Contracted charging stations, availability, and tariffs.
  - name: Billing
    description: Read-only fleet billing summary.
  - name: Transactions
    description: Read-only fleet payment transactions.
  - name: Sessions
    description: Asynchronous remote start, observation, and stop for fleet drivers.
paths:
  /public/fleets/v1/transactions/{payment_transaction_id}:
    get:
      tags:
        - Transactions
      summary: Get fleet payment transaction details
      description: >-
        Uses the same detail notation as the fleet dashboard and verifies that
        the transaction belongs to the authenticated fleet.
      operationId: get_transactions_by_payment_transaction_id
      parameters:
        - name: payment_transaction_id
          in: path
          required: true
          schema:
            type: string
          description: Fleet dashboard payment transaction reference.
          example: TXN20260917_7K4N2P9R5T8V3X6Z
      responses:
        '200':
          description: Fleet payment transaction details.
          content:
            application/json:
              schema:
                type: object
                properties:
                  recipient_name:
                    type: string
                  recipient_operator_name:
                    type: string
                  transaction_datetime:
                    type: string
                    format: date-time
                  fleet_driver_name:
                    type: string
                  payment_amount_incl_tax_paise:
                    type: integer
                  payment_amount_excl_tax_paise:
                    type: integer
                  payment_transaction_type:
                    type: string
                  payment_transaction_id:
                    type: string
                  payment_method:
                    type: string
                  payment_external_reference_id:
                    type: string
                  payment_transaction_utr:
                    type: string
                  fleet_contract_name:
                    type: string
                  payment_source_bank:
                    type: string
                  session_id:
                    type: string
                required:
                  - recipient_name
                  - recipient_operator_name
                  - transaction_datetime
                  - fleet_driver_name
                  - payment_amount_incl_tax_paise
                  - payment_amount_excl_tax_paise
                  - payment_transaction_type
                  - payment_transaction_id
                  - payment_method
                  - payment_external_reference_id
                  - payment_transaction_utr
                  - fleet_contract_name
                  - payment_source_bank
                  - session_id
              example:
                recipient_name: HPC Indiranagar
                recipient_operator_name: HPC Charging
                transaction_datetime: '2026-09-17T09:22:41Z'
                fleet_driver_name: Ananya Rao
                payment_amount_incl_tax_paise: 47200
                payment_amount_excl_tax_paise: 40000
                payment_transaction_type: DEBIT
                payment_transaction_id: TXN20260917_7K4N2P9R5T8V3X6Z
                payment_method: Wallet
                payment_external_reference_id: pay_R8A2mN7K4vQ9Xs
                payment_transaction_utr: HDFC2026091700123456
                fleet_contract_name: Acme Logistics India Fleet Contract
                payment_source_bank: HDFC Bank
                session_id: ses_9df5f4f7b0f64f9e
        '401':
          description: The API key is missing or invalid.
        '404':
          description: The resource was not found for the authenticated fleet.
          content:
            application/json:
              schema:
                type: object
                properties:
                  error:
                    type: object
                    properties:
                      code:
                        type: string
                      message:
                        type: string
                    required:
                      - code
                      - message
                required:
                  - error
              example:
                error:
                  code: RESOURCE_NOT_FOUND
                  message: the requested resource was not found
        '500':
          description: Unexpected server-side error while processing a valid request.
          content:
            application/json:
              schema:
                type: object
                properties:
                  error:
                    type: object
                    properties:
                      code:
                        type: string
                      message:
                        type: string
                    required:
                      - code
                      - message
                required:
                  - error
              example:
                error:
                  code: INTERNAL_ERROR
                  message: an unexpected error occurred while processing the request
components:
  securitySchemes:
    ApiKeyAuth:
      type: apiKey
      in: header
      name: x-api-key
      description: >-
        Fleet-scoped API key. The key identifies exactly one fleet; callers
        never send an internal fleet ID.

````

This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.