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.002.001.14
  • Message structure
  • Message root
  • Group header
  • Original Group Information And Status
  • Original Payment Information And Status

Was this helpful?

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

Direct Debit Collection Notification Response

The ISO 20022 Customer Payment Status Report is sent to LHV by the customer to accept or reject Incoming Collection Initiation Request.

PreviousDirect Debit Incoming Collection Notification RequestNextDirect Debit Collection Notification Response Confirmation

Last updated 1 month ago

Was this helpful?

Request

POST https://connect.lhv.com/direct-debit/bacs-collection-reject

The request message format is a ISO 20022 Customer Payment Status Report XML (pain.002 message)

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.002.001.14

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

Message structure

MULT.
MESSAGE ELEMENT
XML TAG
COMMENT

[1..1]

+GroupHeader

<GrpHdr>

Mandatory, occurs once.

[1..1]

+OriginalGroupInformationAndStatus

<OrgnlGrpInfAndSts>

Mandatory. Original group information concerning the group of transactions, to which the status report message refers to.

[0..*]

+OriginalPaymentInformationAndStatus

<OrgnlPmtInfAndSts>

Mandatory and repeatable. Information concerning the original payment information, to which the status report message refers.

[1..*]

+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

<CstmrPmtStsRpt>

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, assigned by the instructing party and sent to the next party in the chain, to unambiguously identify the message.

[1..1]

++CreationDateTime

<CreDtTm>

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

[1..1]

++InitiatingParty

<InitgPty>

Not used

[0..1]

++ForwardingAgent

<FwdgAgt>

Not used

[0..1]

++DebtorAgent

<DbtrAgt>

Not used

[0..1]

++CreditorAgent

<CdtrAgt>>

Not used

Original Group Information And Status

MULT.
OR
MESSAGE ELEMENT
XML TAG
COMMENT

[1..1]

+OriginalGroupInformationAndStatus

<OrgnlGrpInfAndSts>

Mandatory, occurs once. Original group information concerning the group of transactions, to which the status report message refers to.

[1..1]

++OriginalMessageIdentification

<OrgnlMsgId>

Mandatory. Point to point reference, as assigned by the original instructing party, to unambiguously identify the original message. GrpHdr.MsgId from original pain.008.

[1..1]

++OriginalMessageNameIdentification

<OrgnlMsgNmId>

Mandatory. Specifies the original message name identifier to which the message refers. 'pain.008.001.11'

[0..1]

++OriginalCreationDateTime

<OrgnlCreDtTm>

Not used

[0..1]

++OriginalNumberOfTransactions

<OrgnlNbOfTxs>

Number of individual transactions contained in the original message.

[0..1]

++OriginalControlSum

<OrgnlCtrlSum>

Total of all individual amounts included in the original message, irrespective of currencies.

[0..1]

++GroupStatus

<GrpSts>

[0..*]

++StatusReasonInformation

<StsRsnInf>

Provides detailed information on the status reason.

[0..1]

+++Originator

<Orgtr>

Not used

[0..1]

+++Reason

<Rsn>

Specifies the reason for the status report.

[1..1]

{Or

++++Code

<Cd>

[1..1]

Or}

++++Proprietary

<Prtry>

Not used

[0..*]

+++AdditionalInformation

<AddtlInf>

Further details on the status reason.

[0..*]

++NumberOfTransactionsPerStatus

<NbOfTxsPerSts>

Not used

Original Payment Information And Status

MULT.
OR
MESSAGE ELEMENT
XML TAG
COMMENT

[0..*]

+OriginalPaymentInformationAndStatus

<OrgnlPmtInfAndSts>

Mandatory and repeatable. Information concerning the original payment information, to which the status report message refers.

[1..1]

++OriginalPaymentInformationIdentification

<OrgnlPmtInfId>

Mandatory. Unique identification, as assigned by the original sending party, to unambiguously identify the original payment information group. PmtInf.PmtInfId from original pain.008.

[0..1]

++OriginalNumberOfTransactions

<OrgnlNbOfTxs>

Number of individual transactions contained in the original payment information group.

[0..1]

++OriginalControlSum

<OrgnlCtrlSum>

Total of all individual amounts included in the original payment information group, irrespective of currencies.

[0..1]

++PaymentInformationStatus

<PmtInfSts>

[0..*]

++StatusReasonInformation

<StsRsnInf>

Provides detailed information on the status reason.

[0..1]

+++Originator

<Orgtr>

Not used

[0..1]

+++Reason

<Rsn>

Specifies the reason for the status report.

[1..1]

{Or

++++Code

<Cd>

[1..1]

Or}

++++Proprietary

<Prtry>

Not used

[0..*]

+++AdditionalInformation

<AddtlInf>

Further details on the status reason.

[0..*]

++NumberOfTransactionsPerStatus

<NbOfTxsPerSts>

Not used

[0..*]

++TransactionInformationAndStatus

<TxInfAndSts>

Provides information on the original transactions to which the status report message refers.

[0..1]

+++StatusIdentification

<StsId>

Not used

[0..1]

+++OriginalInstructionIdentification

<OrgnlInstrId>

Not used

[0..1]

+++OriginalEndToEndIdentification

<OrgnlEndToEndId>

Unique identification, as assigned by the original initiating party, to unambiguously identify the original transaction. DrctDbtTxInf.PmtId.EndToEndId from original pain.008.

[0..1]

+++OriginalUETR

<OrgnlUETR>

Not used

[0..1]

+++TransactionStatus

<TxSts>

[0..1]

+++StatusReasonInformation

<StsRsnInf>

Provides detailed information on the status reason.

[0..1]

++++Originator

<Orgtr>

Party that issues the status.

[0..1]

++++Reason

<Rsn>

Specifies the reason for the status report.

[1..1]

{Or

+++++Code

<Cd>

[1..1]

Or}

+++++Proprietary

<Prtry>

Not used

[0..*]

++++AdditionalInformation

<AddtlInf>

Further details on the status reason.

[0..*]

+++ChargesInformation

<ChrgsInf>

Not used

[0..1]

+++Tracker Data

<TrckrData>

Not used

[0..1]

+++Acceptance Date Time

<AccptncDtTm>

Point in time when the payment order from the initiating party meets the processing conditions of the account servicing agent. This means that the account servicing agent has received the payment order and has applied checks such as authorisation, availability of funds.

[0..1]

+++Account Servicer Reference

<AcctSvcrRef>

Not used

[0..1]

+++Clearing System Reference

<ClrSysRef>

Not used

[0..1]

+++Original Transaction Reference

<OrgnlTxRef>

Not used

[0..*]

+++Supplementary Data

<SplmtryData>

Not used

See the Examples section for a message.

Specifies the status of a group of transactions. .

Reason for the status. If Group Status is RJCT, then mandatory.

Specifies the status of the payment information group.

Reason for the status. If Group Status is RJCT, then mandatory.

Specifies the status of a transaction.

Reason for the status. If Group Status is RJCT, then mandatory.

๐Ÿ“–
๐Ÿ”—
๐Ÿงพ
๐Ÿ’ท
pain.002.001.14 CustomerPaymentStatusReportV14
See possible statuses
See list of possible codes.
See possible statuses.
See list of possible codes.
See list of possible codes.
See list of possible codes.
pain.002.001.14
61KB
pain.002.001.14.xsd