Ozow Hub
GEThttps://one.ozow.com/v1/payments/{id}/transactionsProduction
Build with AI 2 packages

A build package is every page for one task, with the API operations they use. Copy the prompt into a coding assistant, or hand it the package itself: slim links to each page, full inlines all of them in one document.

  • Take a paymentEverything needed to take a payment end to end with One API, from credentials through the hosted page to the webhook that confirms it, and the test cases that prove each outcome before you go live.
    View package
  • Migrate a payin from the Payments API to One APIEverything needed to move an existing redirect payin onto One API, with the legacy guide and its One API counterpart side by side.
    View package

List the transactions associated with the payment request with the specified id. An id matching no payment answers 200 with an empty result list rather than 404, so check whether a transaction came back rather than reading the status code.

Authentication

  • OAuth 2.0
    scopespayments

Path parameters

  • id string required

    The unique identifier of the payment.

    example497f6eca-6276-4993-bfeb-53cbbbba6f08

Query parameters

  • limit integer

    The maximum number of items to return.

    min1max50default50
  • offset integer

    The number of items to discard in this paging operation.

    min length0min0default0
  • fromDate string required

    The date from which to filter, inclusive. Whole days only, so any time sent with it is discarded.

    example2026-01-15
  • toDate string required

    The date to filter up to, inclusive. Whole days only, so any time sent with it is discarded.

    example2026-01-31

Header parameters

  • Idempotency-Key string

    The unique key idempotency keyIdempotency A request is idempotent when sending it twice has the same effect as sending it once. It matters most where a retry after a timeout could otherwise take a payment twice.IETF draft as per the following IETF Draft

  • X-Correlation-ID string

    Optional correlation id for the request, if not supplied a new one will be generated and passed onto all underlying requests and returned as a header.

Responses

200 OK.
  • X-Correlation-ID header

    The correlation id for the request that was processed.

  • Standard JSON API pagination links. Each link repeats the query that produced the collection and carries its own limit and offset. Follow the link rather than building the next URI. The example below is the second of three pages.

    Fields of PaginationLinks
    • self string uri

      The current page of data.

    • first string uri

      The first page of data.

    • last string uri nullable

      The last page of data. Null when the whole collection fits on one page.

    • prev string uri nullable

      The previous page of data. Null on the first page.

    • next string uri nullable

      The next page of data. Null on the last page.

    Open PaginationLinks on its own page
  • Fields of Transaction
    • Fields of TransactionLinks
      • self string uri required

        The unique URI for this resource.

      • refund string uri

        The refund operation for this transaction. This is a POST operation.

      Open TransactionLinks on its own page
    • id string uuid required

      The transaction id of the payment.

    • amount Amount

      The amount that was requested.

      Fields of Amount
      • currency string required

        The ISO 4217ISO 4217 The three-letter currency codes, such as ZAR for the South African rand. Always uppercase.Wikipedia current code.

        min length3max length3
      • value number float required

        The amount in the currency specified.

        min0.01
      Open Amount on its own page
    • merchantReference string required

      The merchant's reference for the transaction.

      max length50
    • siteCode string required

      The merchant site codeSite code The unique code for a site registered under a merchant. A site is a place to transact: a website, or a branch of a store. A merchant can have several, and each transaction names the one it belongs to, so sending the wrong code files the payment against the wrong place. in use for this payment.

      max length50
    • institution string required

      The institution for the transaction.

    • status TransactionStatus required

      The status of the transaction.

      values"Incomplete""Successful""Error""Pending""Refunded"
    • reason string

      Payment status reason.

    • createdDate string date-time required

      The date the transaction was created.

    • completedDate string date-time

      The date the transaction was completed.

    Open Transaction on its own page
  • Fields of PaginationMeta
    • totalPages integer required

      The total number of pages available.

    • totalItems integer required

      The total number of items available.

    Open PaginationMeta on its own page

Guides