Transactions represent the movement of funds generated through payment activity. The endpoints below let you find and inspect transactions after a payment has been created, as well as simulate transaction status changes while building and testing in sandbox.
| Endpoint | What It Does | When to Use It |
|---|---|---|
| Get a List of Transactions | Returns transactions associated with a user or payment request. | Finding transactions for a userId, or tracing the transactions associated with a particular requestId or extRequestId. |
| Get Single Transaction Details | Returns the details of a specific transaction. | Inspecting an individual transaction after you have its transactionId. |
| Simulate Transaction Flow in Sandbox | Moves a sandbox transaction through supported transaction statuses. | Testing how your integration responds to different points and outcomes in the transaction lifecycle without waiting for real funds movement. |
📘 Note: Payment Requests and Transactions serve different purposes. A Payment Request defines the payment to be made, while Transactions let you track the resulting movement of funds.