Skip to main content

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.
This endpoint requires a type and id in the path. The type determines what kind of transaction you’re looking up, and the id format varies accordingly: In this example, we’re retrieving a payment transaction by its ID. Replace {accountId} with your account ID and YOUR_API_KEY_HERE with your API key.
If your request is successful, you’ll receive a 200 response containing a single transaction object.
Sample response (payment)
The response structure varies depending on the transaction type. For card transactions (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 the transaction type with a UUID. This is useful when you have a transaction id from the list endpoint and want to get its full details.
When using 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.

Get payment files

For SWIFT and CHAPS payments, you can also download the proof of payment. This is the original bank message for the payment, provided as either an MT103 or an ISO 20022 pacs.008 document. To include it in the response, add paymentFiles to the include query parameter.
When a proof is available, the response includes a paymentFiles array on the transaction. Each item describes one downloadable file.
Example response for paymentFiles
  • fileType tells you the document format (MT103, PACS008, PAIN001, or PDF).
  • url is a secure link to download the file.
  • expiresAt is the date and time when that link stops working.
Payment files are available for SWIFT and CHAPS payments only, and cover both outbound payments (type=payment) and inbound credits (type=boxTransaction). The download link expires after a short time, so retrieve the file promptly. If the link has expired, request the transaction again to get a new one. If no proof is available yet, paymentFiles will be empty. For full details, see the View single transaction guide.