You are provided multiple APIs to search and filter transactions. This document explain the key concepts behind search APIs and help you integrate with search in ways that best suite your needs.
Whenever a sale or refund is executed it is attached to payment object. Payment is a logical grouping of related transactions such as a sale and refund.
Payment - Logical grouping of related transactions
Transaction - A sale or a refund with processing information.
Understanding Payment and Transaction IDs
Transaction detail API works with both paymentId and transaction IDs. Since every transaction is part of a payment the response remains the same regardless of how the API is called.
1. Searching Transaction
Transactions can be searched using Transaction Search API. Based on the search criteria the result is always presented as an array of transactions where very item contains id attribute that is the payment ID that transaction belongs to; and transactionId is the unique transaction ID with its own processing data.
Using either the id that is payment ID or transactionId from the search (or even from the sale response) Transaction Detail API can be called to get the payment details.
The detail object id that is data.id represents Payment ID and each item in details is a transaction that is part of this Payment. The id attribute of each entry in the details object is a unique Transaction ID. In a typical case, a payment will only have a single transaction with one or more refund transactions.