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
  • Request
  • Headers
  • Body
  • Response
  • Headers
  • Body
  • XML Format pain.012.001.07
  • Message structure
  • Message root
  • Group Header
  • Underlying Acceptance Details

Was this helpful?

  1. Service Catalogue
  2. Indirect Scheme Access
  3. Payment Collection Services
  4. Bacs Direct Debit

Bacs Direct Debit Mandate Initiation Response

The ISO 20022 Mandate Acceptance Report is sent to the LHV by the customer to accept or reject Mandate Initiation Request.

PreviousBacs Direct Debit Mandate Initiation RequestNextBacs Direct Debit Mandate Initiation Response Confirmation

Last updated 1 month ago

Was this helpful?

Request

POST https://connect.lhv.com/direct-debit/bacs-mandate-accept

The request message format is a ISO 20022 Mandate Acceptance Report XML (pain.012 message, see below).

Headers

Name
Value

Content-Type

application/xml

Client-Code

customer value

Client-Country

customer value

Body

Response

Headers

Name
Value

Content-Type

application/xml

X-Bank-Code

LHVUK

Body

Request accepted - no content

Error code and description

<Errors>
    <Error>
        <ErrorCode>FORBIDDEN</ErrorCode>
        <Description>Description</Description>
    </Error>
</Errors>

XML Format pain.012.001.07

LHV Bank uses the standard version of the pain.012.001.07 XML schema.

Message structure

MULT.
MESSAGE ELEMENT
XML TAG
COMMENT

[1..1]

+GroupHeader

<GrpHdr>

Mandatory, occurs once.

[1..*]

+UnderlyingAcceptanceDetails

<Mndt>

Mandatory and repeatable. Provides information on the acceptance or rejection of the mandate request.

[0..*]

+SupplementaryData

<SplmtryData>

Not used. Additional information that cannot be captured in the structured elements and/or any other specific block.

Message root

MULT.
MESSAGE ELEMENT
XML TAG
COMMENT

[1..1]

+MessageRoot

<MndtAccptncRpt>

Mandatory, occurs once.

Group Header

MULT.
OR
MESSAGE ELEMENT
XML TAG
COMMENT

[1..1]

+GroupHeader

<GrpHdr>

Mandatory, occurs once.

[1..1]

++MessageIdentification

<MsgId>

Mandatory. Point to point reference, as assigned by the instructing party, and sent to the instructed party, to unambiguously identify the message.

[1..1]

++CreationDateTime

<CreDtTm>

Mandatory. Date and time at which the message was created.

[0..2]

++Authorisation

<Authstn>

Not used

[0..1]

++InitiatingParty

<InitgPty>

Not used

[0..1]

++InstructingAgent

<InstgAgt>

Not used

[0..1]

++InstructedAgent

<InstdAgt>

Not used

Underlying Acceptance Details

MULT.
OR
MESSAGE ELEMENT
XML TAG
COMMENT

[1..*]

+UnderlyingAcceptanceDetails

<UndrlygAccptncDtls>

Mandatory and repeatable. Provides information on the acceptance or rejection of the mandate request.

[0..1]

++OriginalMessageInformation

<OrgnlMsgInf>

Provides information on the original message

[1..1]

+++MessageIdentification

<MsgId>

Mandatory. Point to point reference, as assigned by the original initiating party, to unambiguously identify the original mandate request message. In case of response to Mandate Initiation Request GrpHdr.MsgId from original pain.009.

[1..1]

+++MessageNameIdentification

<MsgNmId>

Mandatory. Specifies the message name identifier to which the message refers. In case of response to Mandate Initiation Request 'pain.009.001.07'.

[0..1]

+++CreationDateTime

<CreDtTm>

Date and time at which the message was created.

[1..1]

++AcceptanceResult

<AccptncRslt>

Mandatory. Provides detailed information on the acceptance result.

[1..1]

+++Accepted

<Accptd>

Mandatory. Indicates whether the mandate request was accepted or rejected. Yes No Indicator.

[0..1]

+++RejectReason

<RjctRsn>

Specifies the reason for the rejection of a mandate request. Mandatory in case of rejection.

[1..1]

{Or

++++Code

<Cd>

[1..1]

Or}

++++Proprietary

<Prtry>

Not used

[0..*]

+++AdditionalRejectReasonInformation

<AddtlRjctRsnInf>

Further details on the reject reason. Is filled when code value = 'NARR'

[0..1]

++OriginalMandate

<OrgnlMndt>

Provides the original mandate data.

[1..1]

{Or

+++OriginalMandateIdentification

<OrgnlMndtId>

Unique identification, as assigned by the responsible party, to unambiguously identify the original mandate. In case of response to Mandate Initiation Request Mndt.MndtId from original pain.009.

[1..1]

Or}

+++OriginalMandate

<OrgnlMndt>

Not used

[0..*]

++SupplementaryData

<SplmtryData>

Not used

See the Examples section for a message.

๐Ÿ“–
๐Ÿ”—
๐Ÿงพ
๐Ÿ’ท
pain.012.001.07 MandateAcceptanceReportV07
pain.012.001.07
36KB
pain.012.001.07.xsd
Code set: Bacs Direct Debit Mandate Reject Codes.