> 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/support.md). # Support #### Contact Channels * **** – Connect API Team Technical questions related to API integration, implementation details, and issue investigation. * **** – Payment Operations Team Payment-related matters, including payment confirmations, investigations, and payment tracing. * **** – Relationship Management Team General onboarding and relationship matters, contractual and legal topics, and billing-related questions. #### Submitting Technical or Incident Requests To ensure faster and more accurate resolution of technical inquiries or incident reports, the following information should be included: * Involved service(s) * Exact timeframe of the issue (e.g. when the payment was initiated or when the error occurred) * Relevant request and response identifiers to support investigation, preferably Message-Request-Id and Message-Response-Id header values * Exact error messages received and any relevant logs Providing complete and precise information significantly improves investigation speed and resolution quality. --- # 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: ``` GET https://docs.lhv.com/home/connect/support.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.