> For the complete documentation index, see [llms.txt](https://docs.lhv.com/home/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.lhv.com/home/connect/services/account-reports/get-transaction-by-reference.md).

# Get Transaction by Reference

### Service Description

This service provides a way to check the status or details of a payment without fetching a full account statement. It is synchronous and optimized for recent transactions (within the last 14 days). The service is available only for payments processed in LHV Bank UK.

When to Use:

* To track the status of a payment without requesting an account statement.
* As a fallback when credit/debit notifications are unavailable.
* For reconciliation, debugging, or investigation purposes.

### Request

`GET` <https://connect.lhv.com/accounts/{accountNumber}/transactions/{accountServicerReference}>

#### Path Parameters

| Name                     | Description                                                                                                                                                                                                                                                                                                |
| ------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| accountNumber            | <p>The IBAN of the account held with LHV Bank.</p><p>Use the master account, virtual IBANs (VIBANs) and indirect scheme participant accounts are not supported.</p>                                                                                                                                        |
| accountServicerReference | <p>The unique payment ID assigned by LHV Bank. This reference is included in the payment status report message (pain.002), account statement (camt.053), and credit/debit notification (camt.054).</p><p>Example: 80FA866CFC3F482CB74EFE0A047DA86D. The value can be provided with or without hyphens.</p> |

#### Headers  <a href="#body" id="body"></a>

Applicable for service providers and service provider users.

| Name           | Description      |
| -------------- | ---------------- |
| Client-Code    | `customer value` |
| Client-Country | `customer value` |

#### Body <a href="#body" id="body"></a>

This request doesn't have a body.

### Response

#### Successful Response

If the payment is found, the response includes full payment details such as status, amount, counterparties, and payment description.

* For debit transactions, receiver (creditor) details are included.
* For credit transactions, sender (debtor) details are included.
* For virtual account (VIBAN) payments, if either the sender or receiver was a VIBAN, the field IsVirtualAccountPayment: `true` is returned and the related virtual account details are added to the response.

#### No Transaction Found

If the transaction cannot be found, a 404 response is returned.

This may happen if:

* payment has not yet been processed (no reservation exists),
  * payment has been cancelled
* the account servicer reference is invalid, or
* the payment is older than the 14-day lookup window.

#### Payment Status

Statuses in the response are simplified for clarity:

* Pending – The payment is being processed but has not yet been booked on the account.
* Booked – The payment has been fully processed and the account has been debited or credited.

Examples

{% tabs %}
{% tab title="200 - payment status and details" %}

```json
{
  "EndToEndId" : "EndToEndId123456",
  "IsVirtualAccountPayment" : false,
  "Amount" : {
    "Amount" : "1.00",
    "Currency" : "GBP"
  },
  "CreditDebitIndicator" : "Debit",
  "Status" : "Booked",
  "BookingDateTime" : "2025-10-31",
  "ValueDateTime" : "2025-10-31",
  "CreditorAgent" : {
    "SchemeName" : "BIC",
    "Identification" : "LHVBGB2LXXX"
  },
  "CreditorAccount" : {
    "Identification" : "GB80LHVB04030700012345",
    "Name" : "Connect Demo Company"
  },
  "TransactionId" : "A5A7DFE0-C65A-4F89-AA4B-EBE944E749E7"
}
```

{% endtab %}

{% tab title="404 - payment not found" %}
{% code overflow="wrap" %}

```json
"No transaction record was found. This may happen if the account servicer reference is invalid, the payment is cancelled or older than 14 days, or it is scheduled for a future date"
```

{% endcode %}
{% endtab %}

{% tab title="403 - no rights to account" %}

```json
"Access denied for the account associated with this IBAN"
```

{% endtab %}
{% endtabs %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.lhv.com/home/connect/services/account-reports/get-transaction-by-reference.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.