The Get a Related Transaction endpoint allows you to retrieve child transactions associated with a parent transaction. Child transactions include voids and refunds linked to the original transaction. This is useful for tracking the history and changes made to a transaction.

Key Features

Retrieve all child transactions related to a specific transaction.
Understand the sequence of actions taken on a transaction.
Access details of voids and refunds associated with the transaction.

Usage Notes

Valid Transaction ID: Only works with charge transaction IDs. Voided and refunded transaction IDs will not return related transactions.

Response Data: The response includes an array of child transactions, each with its own details.

Tracking Changes: Use this endpoint to audit the actions taken on a transaction over time.

Response Structure

Code	Response	Reason
200	Success	Returns an array of child transaction objects related to the original transaction.
400	Bad Request	Invalid transaction ID format.
401	Unauthorized	Authentication failed.
404	Not Found	Transaction ID does not exist or has no related transactions.
500	Internal Server Error	An unexpected error occurred on the server.

Important Considerations

Data Integrity: Use related transactions to ensure data consistency and accurate financial reporting.

Error Handling: Implement proper error handling for scenarios where no related transactions are found.

Permissions: Ensure the user or API key has the necessary permissions to access transaction details.