# How to identify `transactionReference`?

## Instore transactions

For instore transactions, `transactionReference` is the ID generated by the POS system.

### Classic transactions performed via the terminal

You can check that the value of the `transactionReference` that you want to send in the API request is what we expect it to be, by verifying the correct value in the Tyro Portal. After you access a specific transaction, look up the field called `Integrated Transaction ID`. This is the `transactionReference` we would expect for this transaction.

figure
img
figcaption
Figure 1: Sample Transaction - Integrated Transaction ID
### Transactions performed via PayInstore API

For the PayInstore API, we expect you to pass the same value as you did in the `origin.transactionId` field while creating a pay request. In the GET Pay Request response payload, it would be the following field:

figure
img
figcaption
Figure 2: Pay Instore - Pay Request
That value will also be visible in the Tyro Portal as `Integrated Transaction ID`.

## Online transactions

### Online transactions performed via PayApi

For the PayApi, we expect you to pass the `id` of the Pay Request that is to be refunded. Additionally, the `originChannel` should be set to `ONLINE_CHECKOUT` in the refund request. You can find the Pay Request ID in the response of the create Pay Request API call, as shown below:

p
img
### Online transactions performed via Payment Links

You can check that the value of the `transactionReference` that you want to send in the API request is what we expect it to be, by verifying the correct value in the Tyro Portal. After you access a specific transaction, look up the field called `Online Payments order ID`. This is the `transactionReference` we would expect for this transaction.

p
img