> For the complete documentation index, see [llms.txt](https://docs.peakcommerce.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.peakcommerce.com/product/settings/organization/acknowledgements-overview.md).

# Acknowledgements & Consents

Acknowledgements let you capture a customer's explicit consent during a purchase or account change — for example agreeing to **Terms of Service**, a **Privacy Policy**, **Auto-Pay**, **Payment Terms**, or a **stored-credential** mandate (to meet payment requirements such as 3DS2).

## Why it matters

Consents create an auditable record that a customer agreed to your terms at the moment of purchase. That record is both a compliance safeguard (proving terms were presented and accepted) and a payment requirement: card networks and 3DS2 expect an explicit stored-credential acknowledgement before a card can be saved and reused for future charges. Without it, recurring billing and one-click purchases may be declined.

## How it works

Consents are presented as part of the buying flow: the customer checks a box to agree before the order completes, and the agreement is recorded against their account. You add and configure consent capture on the relevant [pages](/product/journeys-and-pages/pages.md) and [journey](/product/journeys-and-pages/journey-basics/journeys-overview.md) steps, so each flow shows exactly the acknowledgements it needs.

## How to use it

1. Decide which acknowledgements a flow requires (T\&C, Auto-Pay, stored-credential, etc.).
2. Add the consent capture to the appropriate page or journey step.
3. Confirm the box must be checked before the order can complete.

## Gotchas

* A required acknowledgement should **block order completion** until accepted — otherwise you lose the auditable record.
* The **stored-credential** acknowledgement is tied to saving a payment method for reuse; see [Stored-Credential Acknowledgement](/product/using-peakcommerce/payments-and-payment-methods/stored-credential-acknowledgement.md) for how it pairs with stored-credential transactions.


---

# 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.peakcommerce.com/product/settings/organization/acknowledgements-overview.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.