Step 2: View single transaction details
Get all the details about a single transaction that has occurred on your account in standard JSON payload format. Note that in sandbox, orders are excluded from the results.There are a number of additional parameters available for you to filter your results. For more information, see the API reference.
type and id in the path. The type determines what kind of transaction you’re looking up, and the id format varies accordingly:
| Type | ID format | Example |
|---|---|---|
transaction | UUID (the transaction’s id) | 19bbf64b-ddfb-48ee-b125-66ed4455d534 |
payment | Integer (the payment’s id) | 123456 |
order | String (the originOrderId) | F6VOXCZ1AMND |
boxTransaction | UUID (the transactionBox.id) | 992e9652-d313-4ea7-aa93-b96b247627c2 |
{accountId} with your account ID and YOUR_API_KEY_HERE with your API key.
200 response containing a single transaction object.
Sample response (payment)
resourceType: "card"), the response includes cardTransaction and merchant objects. For box transactions (resourceType: "box"), the response includes transaction box details.
Example: Get a transaction by UUID
You can also look up a transaction using thetransaction type with a UUID. This is useful when you have a transaction id from the list endpoint and want to get its full details.
type=transaction, the API automatically determines the transaction subtype (card, credit/debit, or BVNK) based on the transaction’s internal type, and returns the appropriate response structure.
For full details on all response structures, see the View single transaction guide.