While LHV UK and EE services are mostly similar and using also similar file formats there are differences in details.
{% endhint %}
### Request
**Headers**
| Name | Value |
| -------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Content-Type | `application/xml` |
| Client-Code | `customer value` |
| Client-Country | `customer value` |
| X-Bank-Code | LHVUK, LHVEE
For more information, see /pages/itRjoiSbC0SvpAZ12lTu#override-option-for-lhv-uk-or-lhv-ee-services
|
#### **Body**
[pain.001.001.09 CustomerCreditTransferInitiationV9](/home/connect/services/payments/pain.001.001.09-format.md)
We do support older version of payment initiation, [pain.001.001.03](/home/connect/services/payments/initiate-a-pending-or-direct-payment/pain.001.001.03-format.md), but it will be phased out soon.
### **Response**
**Headers**
| Name | Value |
| ------------ | ----------------- |
| Content-Type | `application/xml` |
| X-Bank-Code | `LHVUK`, `LHVEE` |
#### Body
{% tabs %}
{% tab title="202" %}
{% hint style="success" %}
Request accepted - no content
{% endhint %}
{% endtab %}
{% tab title="403" %}
{% hint style="danger" %}
Error code and description
{% endhint %}
<Errors>
<Error>
<ErrorCode>FORBIDDEN</ErrorCode>
<Description>User doesn't exist</Description>
</Error>
</Errors>
{% endtab %}
{% endtabs %}
## Payment Initiation Response Message
The Customer Payment Status Report XML ([pain.002 message](/home/connect/services/payments/response.md)) provides updates on the status of submitted payments. A single payment can have multiple statuses, which means that more than one status may be returned for the same payment.
Pain.002 messages can be requested via the [Messages service](/home/connect/services/messages.md).
{% hint style="info" %}
HTTP Header Message-Response-Type: PAYMENT
{% endhint %}
The specific version of the pain.002 message corresponds to the initiation message used to submit the original payment.
When payment is initiated using pain.001.001.09, then pain.002.001.10 is provided in response. If payment is initiated using the legacy pain.001.001.03 format, the response will be pain.002.001.03.
## Examples
List of different payment cases and scenarios are covered - with related request and response messages: [Payment Example Library](/home/connect/services/payments/payment-examples.md)
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.lhv.com/home/connect/services/payments.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.