> 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/services/indirect-scheme-access/payment-collection-services/bacs-direct-debit/bacs-direct-debit-mandate-initiation-response-1.md).

# Bacs Direct Debit Mandate Cancellation Response

Mandate Acceptance Report can be requested via the [Messages service](https://docs.lhv.com/home/connect/services/messages).

{% hint style="info" %}
HTTP Header Message-Response-Type: DIRECT\_DEBIT\_MANDATE\_CANCEL
{% endhint %}

## XML Format pain.012.001.07

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

{% file src="/files/GocYRSPrv3VAAp4O0KAy" %}

See the Examples section for a [pain.012.001.07](/home/connect/services/indirect-scheme-access/payment-collection-services/bacs-direct-debit/samples.md#example-of-mandate-cancellation-response) message.

## Message structure

<table data-full-width="false"><thead><tr><th>MULT.</th><th>MESSAGE ELEMENT</th><th>XML TAG</th><th>COMMENT</th></tr></thead><tbody><tr><td>[1..1]</td><td>+GroupHeader</td><td>&#x3C;GrpHdr></td><td><strong>Mandatory</strong>, occurs once.</td></tr><tr><td>[1..*]</td><td>+UnderlyingAcceptanceDetails</td><td>&#x3C;Mndt></td><td><strong>Mandatory</strong> and repeatable. Provides information on the acceptance or rejection of the mandate request.</td></tr><tr><td>[0..*]</td><td>+SupplementaryData</td><td>&#x3C;SplmtryData></td><td><strong>Not used.</strong> Additional information that cannot be captured in the structured elements and/or any other specific block.</td></tr></tbody></table>

### Message root <a href="#message-root" id="message-root"></a>

<table data-full-width="false"><thead><tr><th>MULT.</th><th>MESSAGE ELEMENT</th><th>XML TAG</th><th>COMMENT</th></tr></thead><tbody><tr><td>[1..1]</td><td>+MessageRoot</td><td>&#x3C;MndtAccptncRpt></td><td><strong>Mandatory</strong>, occurs once.</td></tr></tbody></table>

### Group Header <a href="#group-header" id="group-header"></a>

<table data-full-width="false"><thead><tr><th>MULT.</th><th>OR</th><th>MESSAGE ELEMENT</th><th>XML TAG</th><th>COMMENT</th></tr></thead><tbody><tr><td>[1..1]</td><td></td><td>+GroupHeader</td><td>&#x3C;GrpHdr></td><td><strong>Mandatory</strong>, occurs once.</td></tr><tr><td>[1..1]</td><td></td><td>++MessageIdentification</td><td>&#x3C;MsgId></td><td><strong>Mandatory</strong>. Point to point reference, as assigned by the instructing party, and sent to the instructed party, to unambiguously identify the message.</td></tr><tr><td>[1..1]</td><td></td><td>++CreationDateTime</td><td>&#x3C;CreDtTm></td><td><strong>Mandatory</strong>. Date and time at which the message was created.</td></tr><tr><td>[0..2]</td><td></td><td>++Authorisation</td><td>&#x3C;Authstn></td><td><strong>Not used</strong></td></tr><tr><td>[0..1]</td><td></td><td>++InitiatingParty</td><td>&#x3C;InitgPty></td><td><strong>Not used</strong></td></tr><tr><td>[0..1]</td><td></td><td>++InstructingAgent</td><td>&#x3C;InstgAgt></td><td><strong>Not used</strong></td></tr><tr><td>[0..1]</td><td></td><td>++InstructedAgent</td><td>&#x3C;InstdAgt></td><td><strong>Not used</strong></td></tr></tbody></table>

### Underlying Acceptance Details

<table data-full-width="false"><thead><tr><th>MULT.</th><th>OR</th><th>MESSAGE ELEMENT</th><th width="169">XML TAG</th><th>COMMENT</th></tr></thead><tbody><tr><td>[1..*]</td><td></td><td>+UnderlyingAcceptanceDetails</td><td>&#x3C;UndrlygAccptncDtls></td><td><strong>Mandatory</strong> and repeatable. Provides information on the acceptance or rejection of the mandate request.</td></tr><tr><td>[0..1]</td><td></td><td>++OriginalMessageInformation</td><td>&#x3C;OrgnlMsgInf></td><td>Provides information on the original message</td></tr><tr><td>[1..1]</td><td></td><td>+++MessageIdentification</td><td>&#x3C;MsgId></td><td><p><strong>Mandatory.</strong> Point to point reference, as assigned by the original initiating party, to unambiguously identify the original mandate request message.</p><p><strong>In case of response to Mandate Cancellation Request</strong> GrpHdr.MsgId from original pain.011.</p></td></tr><tr><td>[1..1]</td><td></td><td>+++MessageNameIdentification</td><td>&#x3C;MsgNmId></td><td><strong>Mandatory.</strong> Specifies the message name identifier to which the message refers.<br><strong>In case of response to Mandate Cancellation Request</strong> 'pain.011.001.07'.</td></tr><tr><td>[0..1]</td><td></td><td>+++CreationDateTime</td><td>&#x3C;CreDtTm></td><td>Date and time at which the message was created.</td></tr><tr><td>[1..1]</td><td></td><td>++AcceptanceResult</td><td>&#x3C;AccptncRslt></td><td><strong>Mandatory.</strong> Provides detailed information on the acceptance result.</td></tr><tr><td>[1..1]</td><td></td><td>+++Accepted</td><td>&#x3C;Accptd></td><td><strong>Mandatory.</strong> Indicates whether the mandate request was accepted or rejected. Yes No Indicator.</td></tr><tr><td>[0..1]</td><td></td><td>+++RejectReason</td><td>&#x3C;RjctRsn></td><td>Specifies the reason for the rejection of a mandate request. Mandatory in case of rejection. </td></tr><tr><td>[1..1]</td><td>{Or</td><td>++++Code</td><td>&#x3C;Cd></td><td><a href="/pages/pC3okS66zp8T8ITo9WEX#mandate-cancellation-rejection">Code set: Bacs Direct Debit Mandate Cancellation Reject Codes.</a></td></tr><tr><td>[1..1]</td><td>Or}</td><td>++++Proprietary</td><td>&#x3C;Prtry></td><td><strong>Not used</strong></td></tr><tr><td>[0..*]</td><td></td><td>+++AdditionalRejectReasonInformation</td><td>&#x3C;AddtlRjctRsnInf></td><td>Further details on the reject reason. Is filled when code value = 'NARR'</td></tr><tr><td>[0..1]</td><td></td><td>++OriginalMandate</td><td>&#x3C;OrgnlMndt></td><td>Provides the original mandate data.</td></tr><tr><td>[1..1]</td><td>{Or</td><td>+++OriginalMandateIdentification</td><td>&#x3C;OrgnlMndtId></td><td><p>Unique identification, as assigned by the responsible party, to unambiguously identify the original mandate.</p><p><strong>In case of response to Mandate Cancellation Request</strong> Mndt.MndtId from original pain.011.</p></td></tr><tr><td>[1..1]</td><td>Or}</td><td>+++OriginalMandate</td><td>&#x3C;OrgnlMndt></td><td><strong>Not used</strong></td></tr><tr><td>[0..*]</td><td></td><td>++SupplementaryData</td><td>&#x3C;SplmtryData></td><td><strong>Not used</strong></td></tr></tbody></table>


---

# 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, and the optional `goal` query parameter:

```
GET https://docs.lhv.com/home/connect/services/indirect-scheme-access/payment-collection-services/bacs-direct-debit/bacs-direct-debit-mandate-initiation-response-1.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.