> For the complete documentation index, see [llms.txt](https://docs.gethoneycart.com/live-examples/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.gethoneycart.com/live-examples/payments/automated-charges.md).

# Automated Charges

Set whether credit cards should be charged [manually](/live-examples/payments/manual-charges-and-deposits.md) or automatically:

* set rules based on [order type](/live-examples/order-types/overview.md)
* set different rules for Active orders vs [Cancellation fees](/live-examples/catering-policies/cancellations.md)
* show a policy message during checkout so clients know when they'll be charged.

{% hint style="success" %}
**Live Demo:** place a "test" Pickup order to see a demo of [automated charges](https://hc-live-examples.gethoneycart.com/?menu=1\&order_type=2). You'll receive an email receipt for the charge.
{% endhint %}

## Credit Card Charge Policy Settings

You can set different rules for when active orders (i.e new orders or changes to existing orders) vs cancellation fees are charged.

![You can charge credit cards ASAP or customize the amount of time before/after the event the card will be charged.](/files/9xvWNy3macJSQXtKrWeL)

## Policy Message Shown at Checkout

Show clients messages that explain when their credit card will be charged.

![](/files/Wyk0vldlDxe9QC6u2tqo)


---

# 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:

```
GET https://docs.gethoneycart.com/live-examples/payments/automated-charges.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.