LogoLogo
Connect
Connect
  • ๐ŸกWelcome to LHV Connect API
  • ๐Ÿ“บNews and Updates
    • ๐Ÿ“ˆPerformance and Stats
    • ๐Ÿ””Notice of Change
  • ๐ŸงญQuick Start Guide
  • ๐ŸŽฅConnect Fundamentals
    • Authentication and Certificates
    • Environments
    • Messaging Pattern
    • Service Provider model
    • Technical limitations
    • Encoding and Languages
    • Response Compression
    • Dates and Time Zones
    • Response Codes and Error handling
    • Onboarding
    • Live Proving
    • LHV UK and Estonia integrations
    • FAQ and Tips
  • ๐Ÿ“–Service Catalogue
    • ๐Ÿ’šHeartbeat
      • Heartbeat - GET
      • Heartbeat Advanced - GET
    • ๐Ÿ“ฉMessages Services
      • Get next message
      • Get list of messages
      • Get list of messages V2
      • Get message by response ID
      • Get list of requests
      • Get request by request ID
      • Count number of messages
      • Mark message as processed
      • Mark batch of messages as processed
      • Mark batch of messages as processed V2
      • Messages Metadata
      • Get compressed message for testing
    • ๐Ÿ’ฐAccount Information Services
      • Account Balance
      • Account Statement
      • Transaction Notification
        • Incoming Bacs Credit Notification
    • ๐Ÿ’ธPayment Initiation Services
      • Pain.001.001.09
      • Pain.002.001.10
      • Samples
      • Authentication methods
      • Payment Scheme Selection
      • Payment Return Initiation
      • Payments Service Idempotency
      • Payments Originating Overseas
      • Legacy documents
        • pain.001.001.03 format
    • โœ…Confirmation of Payee Services
      • Confirmation of Payee - Requester
      • Confirmation of Payee - Responder
    • ๐Ÿ˜ถโ€๐ŸŒซ๏ธVIBAN Services
      • VIBAN Open
      • VIBAN Bulk Open
      • VIBAN Modify
      • VIBAN Info
      • VIBAN Close
      • VIBAN Notification
    • ๐Ÿ”—Indirect Scheme Access
      • Agency Account Synchronization
      • RTF - Routing Table Files message
      • ๐ŸงพPayment Collection Services
        • ๐Ÿ’ทBacs Direct Debit
          • Bacs Direct Debit Mandate Initiation Request
          • Bacs Direct Debit Mandate Initiation Response
          • Bacs Direct Debit Mandate Initiation Response Confirmation
          • Bacs Direct Debit Mandate Cancellation Request
          • Bacs Direct Debit Mandate Cancellation Response
          • Direct Debit Incoming Collection Notification Request
          • Direct Debit Collection Notification Response
          • Direct Debit Collection Notification Response Confirmation
          • Direct Debit Reversal Notification Request
          • Examples
    • ๐Ÿ“จWebhooks
      • Webhook Format and Processing
      • Managing Webhook Configurations
      • Webhook Security
      • Webhook Metadata
      • Full Bodied Webhooks
  • ๐Ÿ—“๏ธReference
    • Glossary
    • Code Reference Tables
      • Balance Type Codes
      • Credit and Debit Transaction Codes
      • Payment Scheme Codes
      • Direct Debit Scheme Codes
      • Payment Reject Codes
      • Payment Return Codes
      • Bacs Direct Debit Mandate Reject Codes
      • Bacs Direct Debit Reject Codes
      • Bacs Direct Debit Reversal Reason
      • Bank Transaction Codes
      • Transaction Purpose Codes
      • Category Purpose Codes
      • Private Person Identification Codes
      • Organisation Identification Type Codes
      • Payment Priority Codes
      • Charges Bearer Codes
  • โ˜Ž๏ธSupport
    • Contact
Powered by GitBook
On this page

Was this helpful?

  1. Support

Contact

Please use following contacts for different requests you might have:

  • connect@lhv.ee - Connect API team: questions about technical details, issues with integration

  • fpsoprations@lhv.ee - Payment Operations team: specific payment related matters, payment confirmations, tracing of payments

  • fi-support@lhv.co.uk - Relationship Managers team: general onboarding and relationship questions, contractual and legal matters, general billing

When submitting support requests for technical help or incident resolving, please follow these guidelines:

  • Specify the involved services

  • Specify the timeframe - when exactly did the issue occur, problematic payment was initiated etc.

  • Provide request and response ID's that help us trace the issue. Best option is the Message-Request-Id and Message-Response-Id header values mentioned here.

  • Provide exact error messages you received or additional logs you have related to the issue.

Providing this valuable information and details helps us resolve your questions faster and better!

PreviousSupport

Last updated 1 year ago

Was this helpful?

โ˜Ž๏ธ