> ## Documentation Index > Fetch the complete documentation index at: https://developer.hellgate.io/llms.txt > Use this file to discover all available pages before exploring further. # List transactions > Retrieves a paginated list of all transactions associated with a refund. The results are grouped into pages, and the caller can specify the number of transactions per page via a query parameter, with a maximum limit of 500 transactions per page. If no value is specified, a default page size will be used. ## OpenAPI ````yaml /products/commerce/v2/openapi.yaml get /refunds/{id}/transactions openapi: 3.1.0 info: title: Commerce API version: '2.0' description: > The Commerce V2 API provides a comprehensive payment orchestration platform designed to streamline and optimize payment processing for modern businesses. Built with flexibility and security at its core, our API enables you to process payments, manage authentications, and handle cardholder data across multiple payment processors without vendor lock-in. contact: name: Starfish GmbH & Co. KG email: hello@starfish.team url: https://hellgate.io/cpa/commerce license: name: Commerce API Terms url: https://hellgate.io/terms-and-conditions servers: - url: https://sandbox.hellgate.io description: Commerce SaaS Sandbox - url: https://api.hellgate.io description: Commerce SaaS Production security: [] tags: - name: payments_ci description: >- Handle payment processing where the customer is actively present and authorizing the transaction. - name: payments_mi description: >- Process transactions without direct customer interaction at the time of payment. - name: payments_modifications description: >- Modify existing payment transactions after initial authorization (capture, void, refund). - name: payments_data description: >- Access comprehensive payment transaction data for reporting, reconciliation, and analysis. - name: refunds_data description: Access detailed refund transaction data for tracking and reconciliation. - name: authentications_ci description: >- Process EMVCo 3-D Secure authentication requests as standalone transactions (one-off, recurring, installment). - name: authentications_mi description: >- Process requestor-initiated EMVCo 3-D Secure authentication requests (3RI) as standalone transactions. - name: authentications_data description: Access the results of prior authentications for reference. - name: credentials_management description: >- Manage stored payment credentials for repeat customers across all operating models. - name: tokens_create description: >- Create and import Commerce tokens to securely store cardholder data while maintaining PCI DSS compliance. - name: tokens_management description: Manage stored Commerce tokens including CVC2 security code management. - name: compliance_service description: >- Safely handle sensitive cardholder data while maintaining PCI DSS compliance via a secure proxy service. - name: network_tokens description: >- Manage network tokens with major card schemes with automatic lifecycle management. - name: merchants description: >- Configure and manage merchant accounts based on your chosen operating model. - name: reconciliation description: Reconcile imported token data. - name: processor_backup description: >- Migrate payment tokens from third-party processors (currently supports stripe.com). paths: /refunds/{id}/transactions: get: tags: - refunds_data summary: List transactions description: > Retrieves a paginated list of all transactions associated with a refund. The results are grouped into pages, and the caller can specify the number of transactions per page via a query parameter, with a maximum limit of 500 transactions per page. If no value is specified, a default page size will be used. operationId: list_refund_transactions parameters: - in: query name: limit description: The desired amount of records per page. schema: type: integer minimum: 0 default: 50 maximum: 500 required: false - in: query name: page description: The desired number of the page to return. schema: type: integer minimum: 0 required: false - in: path name: id description: The ID of the refund on Commerce. schema: type: string format: uuid required: true responses: '200': description: Success response content: application/json: schema: $ref: '#/components/schemas/TransactionList' example: data: - id: 54ba1fdb-7e4e-402b-aebb-66f9d5345cf8 type: refund status: succeeded started_at: '2021-01-01T00:00:00Z' finished_at: '2021-01-01T00:00:00Z' processor: name: Starfish Bank transaction_id: ch_1H9zvz2eZvKYlo2C5J1J9zvz merchant_id: acct_1H9zvz2eZvKYlo2C network_transaction_reference: '1234567890' pagination: current_page: 1 page_size: 50 total_items: 1 total_pages: 1 '401': $ref: '#/components/responses/401_UnauthorizedError' '403': $ref: '#/components/responses/403_ForbiddenError' '404': $ref: '#/components/responses/404_NotFoundError' security: - APIKeyAuth: [] components: schemas: TransactionList: type: object properties: data: type: array items: $ref: '#/components/schemas/Transaction' pagination: $ref: '#/components/schemas/Pagination' Transaction: type: object properties: id: type: string format: uuid description: The ID of the Transaction on Commerce failure_details: type: array items: type: object properties: classifier: type: string description: Unique classifier of the error message: type: string description: Human readable information about the failure source: type: string enum: - processor - integration required: - classifier - source finished_at: type: string format: date-time description: The date-time the transaction was finished (following ISO 8601) processor: type: object properties: name: type: string description: Name of the processor of payment transaction transaction_id: type: string description: The transaction ID on the processor side merchant_id: type: string description: The identification of the merchant being used with the processor network_transaction_reference: type: string description: The network transaction reference started_at: type: string format: date-time description: The date-time the transaction was started (following ISO 8601) status: $ref: '#/components/schemas/TransactionStatus' type: type: string enum: - authorize - capture - cancel - refund Pagination: type: object description: > The meta-data describing lists of data from the Commerce API. The pages are indexed from 1 up to the total_pages. properties: current_page: type: integer description: The index of the current page page_size: type: integer description: > The maximum number of items on a page (relates to the limit query parameter) total_items: type: integer description: The total quantity of items regardless of the pages total_pages: type: integer description: The total amount of pages the data is segmented into example: current_page: 1 page_size: 1 total_items: 1 total_pages: 1 ErrorGeneric: type: object properties: code: $ref: '#/components/schemas/ErrorStatusCode' classifier: $ref: '#/components/schemas/ErrorClassifier' message: $ref: '#/components/schemas/ErrorMessage' TransactionStatus: type: string enum: - pending - succeeded - failed ErrorStatusCode: type: integer description: The corresponding HTTP status code for the error ErrorClassifier: type: string description: Technical code that helps to identify the error ErrorMessage: type: string description: Human readable representation of the error responses: 401_UnauthorizedError: description: Unauthorized content: application/json: schema: $ref: '#/components/schemas/ErrorGeneric' example: code: 401 message: No valid means of authentication was provided classifier: UNAUTHORIZED 403_ForbiddenError: description: Forbidden content: application/json: schema: $ref: '#/components/schemas/ErrorGeneric' example: code: 403 message: Not allowed to access this resource or feature classifier: FORBIDDEN 404_NotFoundError: description: Not found content: application/json: schema: $ref: '#/components/schemas/ErrorGeneric' example: code: 404 message: The requested resource was not found. classifier: NOT_FOUND securitySchemes: APIKeyAuth: type: apiKey name: X-API-Key in: header ````