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
  • Message structure
  • Error codes

Was this helpful?

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

Bacs Direct Debit Mandate Initiation Response Confirmation

Mandate Initiation Response Confirmation message is sent to client to confirm or reject Mandate Response message.

PreviousBacs Direct Debit Mandate Initiation ResponseNextBacs Direct Debit Mandate Cancellation Request

Last updated 1 month ago

Was this helpful?

Mandate Initiation Response Confirmation can be requested via the .

HTTP Header Message-Response-Type: DIRECT_DEBIT_MANDATE_CONFIRM

See the Examples section for a .

Message structure

For this message, JSON format is used.

Name
Value
Description

GrpHdr.MsgId

Mandatory. Related pain.012 message id. (GrpHdr.MsgId from pain.012)

AcceptanceStatus

OK - All acceptances are processed successfully

PARTIAL - Some of the acceptances failed to process

FAILED - The file was failed to process

Mandatory. pain.012 fail processing status.

Messages.OrgnlMsgInf.MsgId

Mandatory. Original pain.009 message id. (GrpHdr.MsgId from pain.009)

Messages.Confirmed

true - response is confirmed

false - response is not confirmed

Mandatory. Mandate response status: If the value is true, the mandate response was processed successfully. If the value is false, an error occurred and the ErrorInfo section is presented with error details.

Messages.ErrorInfo.ErrorCode

Optional. Only presented when Message.confirmed is false.

Messages.ErrorInfo.ErrorDescription

Optional. Only presented when Message.confirmed is false.

All mandate responses in pain.012 have been processed successfully.

{
  "GrpHdr.MsgId": "pain012_message_id",
  "AcceptanceStatus": "OK",
  "Messages": [
    {
      "OrgnlMsgInf.MsgId": "message_id_pain009",
      "Confirmed": true
    },
    {
      "OrgnlMsgInf.MsgId": "message_id_pain009_2",
      "Confirmed": true
    }
  ]
}

Some mandate responses in pain.012 have failed to process.

{
  "GrpHdr.MsgId": "pain012_message_id",
  "AcceptanceStatus": "PARTIAL",
  "Messages": [
    {
      "OrgnlMsgInf.MsgId": "message_id_pain009",
      "Confirmed": true
    },
    {
      "OrgnlMsgInf.MsgId": "invalid_message_id",
      "Confirmed": false,
      "ErrorInfo": {
        "ErrorCode": "NOT_FOUND",
        "ErrorDescription": "Mandate not found"
      }
    }
  ]
}

Pain.012 has failed to process.

{
  "GrpHdr.MsgId": "pain012_message_id",
  "AcceptanceStatus": "FAILED",
  "Messages": [
    {
      "OrgnlMsgInf.MsgId": "pain009_message_id",
      "Confirmed": false,
      "ErrorInfo": {
        "ErrorCode": "INVALID_ACCEPTANCE_DATA",
        "ErrorDescription": "Invalid acceptance data"
      }
    }
  ]
}

Error codes

Error Code
Error Description
Comment

MANDATE_NOT_FOUND

Mandate not found

Mandate does not exist. The pain.009 id may be invalid in pain.012 message (UndrlygAccptncDtls.OrgnlMsgInf.MsgId)

MANDATE_INVALID_STATUS

Mandate is expected to be in status PENDING, but is in status ...

A mandate can be confirmed or rejected only when it is in pending status. If the mandate is already confirmed, returned, activated, etc., it can no longer be accepted or rejected.

DUPLICATE_MESSAGE_ID

Duplicate message in file

There is duplicate pain.009 message id on pain.012 file.

MANDATE_FILE_NOT_FOUND

pain.009 message file not found

Original Mandate Initiation Request does not exist. The pain.009 id may be invalid in pain.012 message (UndrlygAccptncDtls.OrgnlMsgInf.MsgId)

NO_RIGHTS_TO_DEBTOR_ACCOUNT

User have no rights to debtor account

User have no rights to debtor account.

INVALID_ACCEPTANCE_DATA

Invalid acceptance data

Acceptance data in pain.012 is invalid. Status and reason code must be filled correctly.

List of error codes can be found

List of error code descriptions can be found

๐Ÿ“–
๐Ÿ”—
๐Ÿงพ
๐Ÿ’ท
here
here
Messages service
confirmation message