> For the complete documentation index, see [llms.txt](https://help.brickspacelab.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.brickspacelab.com/slab/content/blocks/cart/checkout-agreement.md).

# Checkout agreement

<figure><img src="https://3723856256-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGnixyIfIYFWroNtVmZo6%2Fuploads%2Fgit-blob-ac7d41944191dacced25adb9670914c0aec9f02b%2Fimage.png?alt=media" alt=""><figcaption></figcaption></figure>

## Overview

A customizable checkout approval checkbox that controls whether checkout is enabled for the customer. When unchecked, it prevents proceeding to checkout.

## Common use cases

* Use clear, concise text in the label to explain what the customer is agreeing to
* Consider legal requirements when using this for terms acceptance
* Test on both mobile and desktop views to ensure proper visibility
* Enable preselect checkbox if you want the checkbox checked by default

## Block settings

### General

| Setting                | Description                 | Options                   |
| ---------------------- | --------------------------- | ------------------------- |
| Show advanced settings | Reveals visibility settings | Checkbox (default: false) |

### Content

| Setting                   | Description                                    | Options                  |
| ------------------------- | ---------------------------------------------- | ------------------------ |
| Label                     | Label text for the checkbox                    | Rich text input          |
| Enable preselect checkbox | Automatically checks the checkbox on page load | Checkbox (default: true) |

### Spacing

| Setting                   | Description                                 | Options                   |
| ------------------------- | ------------------------------------------- | ------------------------- |
| Enable horizontal padding | Adds horizontal padding around the checkbox | Checkbox (default: false) |
| Enable top padding        | Adds top padding around the checkbox        | Checkbox (default: false) |
| Enable bottom padding     | Adds bottom padding around the checkbox     | Checkbox (default: false) |

### Display

| Setting    | Description                        | Options                                                                                                                            |
| ---------- | ---------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------- |
| Visibility | Controls when the block is visible | <p>• All (default)<br>• Mobile only<br>• Desktop only</p><p><br><br>Visible when <strong>Show advanced settings</strong> is on</p> |


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.brickspacelab.com/slab/content/blocks/cart/checkout-agreement.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.