> ## Documentation Index > Fetch the complete documentation index at: https://docs.validationcloud.io/llms.txt > Use this file to discover all available pages before exploring further. # Retrieve a Transaction's Payments > This endpoint returns the payments of a specific transaction. This method will use `10` [Compute Units](/nodeapi/about/billing). *** ## OpenAPI ````yaml nodeapi/openapi/bundled-stellar-horizon-vc-urls.json GET /transactions/{transaction_hash}/payments openapi: 3.1.0 info: title: Horizon version: 0.0.1 summary: >- Horizon provides an HTTP API to data in the Stellar network. It ingests and re-serves the data produced by the Stellar network in a form that is easier to consume by the average application relative to the performance-oriented data representations used by Stellar Core. This API serves the bridge between apps and Stellar Core. Projects like wallets, decentralized exchanges, and asset issuers use Horizon to submit transactions, query an account balance, or stream events like transactions to an account. servers: - url: https://{network}.stellar.validationcloud.io/v1/ variables: network: default: mainnet enum: - mainnet - testnet - archive description: Validation Cloud Stellar Horizon RPC security: [] tags: - name: Accounts description: >- Users interact with the Stellar network through accounts. Everything else in the ledger—assets, offers, trustlines, etc. are owned by accounts, and accounts must authorize all changes to the ledger through signed transactions. - name: Assets description: >- Assets are representations of value issued on the Stellar network. An asset consists of a type, code, and issuer. - name: Claimable Balances description: >- A Claimable Balance represents the transfer of ownership of some amount of an asset. Claimable balances provide a mechanism for setting up a payment which can be claimed in the future. This allows you to make payments to accounts which are currently not able to accept them. - name: Effects description: >- Effects represent specific changes that occur in the ledger as a result of successful operations, but are not necessarily directly reflected in the ledger or history, as transactions and operations are. - name: Fee Stats description: >- Fee stats are used to predict what fee to set for a transaction before submitting it to the network. - name: Liquidity Pools description: >- Liquidity Pools provide a simple, non-interactive way to trade large amounts of capital and enable high volumes of trading. - name: Ledgers description: >- Each ledger stores the state of the network at a point in time and contains all the changes - transactions, operations, effects, etc. - to that state. - name: Offers description: >- Offers are statements about how much of an asset an account wants to buy or sell. - name: Operations description: >- Operations are objects that represent a desired change to the ledger: payments, offers to exchange currency, changes made to account options, etc. Operations are submitted to the Stellar network grouped in a Transaction. - name: Order Books description: An order book is a collections of offers for a specific pair of assets. - name: Paths description: >- Paths provide information about potential path payments. A path can be used to populate the necessary fields for a path payment operation. - name: Payments description: >- Payments are objects that represent balance transfer from one address to another. Payments are submitted to the Stellar network grouped in a Transaction. - name: Trade Aggregations description: >- A trade aggregation represents aggregated statistics on an asset pair (base and counter) for a specific time period. Trade aggregations are useful to developers of trading clients and provide historical trade data. - name: Trades description: >- When an offer is fully or partially fulfilled, a trade happens. Trades can also be caused by successful path payments, because path payments involve fulfilling offers. A trade occurs between two parties—base and counter. Which is which is either arbitrary or determined by the calling query. - name: Transactions description: >- Transactions are commands that modify the ledger state and consist of one or more operations. paths: /transactions/{transaction_hash}/payments: get: tags: - Payments summary: Retrieve a Transaction's Payments description: This endpoint returns the payments of a specific transaction. operationId: RetrieveATransactionsPayments parameters: - $ref: '#/components/parameters/HashParam' - $ref: '#/components/parameters/CursorParam' - $ref: '#/components/parameters/OrderParam' - $ref: '#/components/parameters/LimitParam' responses: '200': description: Success content: application/json: schema: allOf: - $ref: '#/components/schemas/Links' - $ref: '#/components/schemas/Payment' examples: RetrieveATransactionsPayments: $ref: '#/components/examples/RetrieveATransactionsPayments' components: parameters: HashParam: name: transaction_hash in: path required: true description: >- Transactions are commands that modify the ledger state and consist of one or more operations. schema: type: string example: 5ebd5c0af4385500b53dd63b0ef5f6e8feef1a7e1c86989be3cdcce825f3c0cc CursorParam: name: cursor in: query required: false description: >- A number that points to a specific location in a collection of responses and is pulled from the paging_token value of a record. schema: type: integer example: 6606617478959105 OrderParam: name: order in: query required: false description: >- A designation of the order in which records should appear. Options include `asc` (ascending) or `desc` (descending). If this argument isn’t set, it defaults to `asc`. schema: type: string enum: - asc - desc LimitParam: name: limit in: query required: false description: >- The maximum number of records returned. The limit can range from 1 to 200 - an upper limit that is hardcoded in Horizon for performance reasons. If this argument isn’t designated, it defaults to 10. schema: type: integer example: 10 schemas: Links: type: object properties: _links: type: object properties: self: $ref: '#/components/schemas/link' next: $ref: '#/components/schemas/link' prev: $ref: '#/components/schemas/link' Payment: type: object properties: _embedded: type: object properties: records: type: array items: type: object properties: _links: type: object properties: self: $ref: '#/components/schemas/link' transaction: $ref: '#/components/schemas/link' effects: $ref: '#/components/schemas/link' succeeds: $ref: '#/components/schemas/link' precedes: $ref: '#/components/schemas/link' required: - self - transaction - effects - succeeds - precedes id: $ref: '#/components/schemas/id' paging_token: type: string transaction_successful: type: boolean source_account: $ref: '#/components/schemas/address' type: type: string example: payment type_i: type: string created_at: type: string transaction_hash: type: string asset_type: type: string asset_code: enum: - native - credit_alphanum4 - credit_alphanum12 asset_issuer: $ref: '#/components/schemas/address' from: $ref: '#/components/schemas/address' to: $ref: '#/components/schemas/address' amount: type: string required: - id - paging_token - transaction_successful - source_account - type - type_i - created_at - transaction_hash - asset_type - from - to - amount link: type: object properties: href: type: string format: link templated: type: boolean required: - href id: type: string address: type: string pattern: G[A-Z0-9]{55} examples: RetrieveATransactionsPayments: value: _links: self: href: >- https://mainnet.stellar.validationcloud.io/v1///transactions/f8929884dfc56ff9d8bc220c7bfba9e58208943eba96f33e8a0787a5bb8a4629/payments?cursor=&limit=10&order=asc next: href: >- https://mainnet.stellar.validationcloud.io/v1///transactions/f8929884dfc56ff9d8bc220c7bfba9e58208943eba96f33e8a0787a5bb8a4629/payments?cursor=3382840796385281&limit=10&order=asc prev: href: >- https://mainnet.stellar.validationcloud.io/v1///transactions/f8929884dfc56ff9d8bc220c7bfba9e58208943eba96f33e8a0787a5bb8a4629/payments?cursor=3382840796385281&limit=10&order=desc _embedded: records: _links: self: href: >- https://mainnet.stellar.validationcloud.io/v1///operations/3382840796385281 transaction: href: >- https://mainnet.stellar.validationcloud.io/v1///transactions/f8929884dfc56ff9d8bc220c7bfba9e58208943eba96f33e8a0787a5bb8a4629 effects: href: >- https://mainnet.stellar.validationcloud.io/v1///operations/3382840796385281/effects succeeds: href: >- https://mainnet.stellar.validationcloud.io/v1///effects?order=desc&cursor=3382840796385281 precedes: href: >- https://mainnet.stellar.validationcloud.io/v1///effects?order=asc&cursor=3382840796385281 id: '3382840796385281' paging_token: '3382840796385281' transaction_successful: true source_account: GCNEGL4IYJ4XH2GV62QK4PQ5D4YWSYZPBC3NVF6VMNSFUMBFW3V3DKKY type: account_merge type_i: 8 created_at: '2024-07-29T19:33:23Z' transaction_hash: f8929884dfc56ff9d8bc220c7bfba9e58208943eba96f33e8a0787a5bb8a4629 account: GCNEGL4IYJ4XH2GV62QK4PQ5D4YWSYZPBC3NVF6VMNSFUMBFW3V3DKKY into: GBFAIH5WKAJQ77NG6BZG7TGVGXHPX4SQLIJ7BENJMCVCZSUZPSISCLU5 ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.