> For the complete documentation index, see [llms.txt](https://docs.anedot.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.anedot.com/action-pages/page-builder/payment-methods-and-fees.md).

# Payment Methods and Fees in the Page Builder

Choose payment methods, turn on Bitcoin, set who covers processing fees, and set minimum and maximum gift amounts in Finance > Payment of the Page Builder.

**Payment** controls how donors pay on your page. You'll find it in the Page Builder under **Finance > Payment**. This article covers payment methods, Bitcoin, the Cover the fees options, and transaction limits.

{% hint style="info" %}
Payment is available on Donation Pages and Event Pages. Lead Pages don't take payments, so they don't have Payment.
{% endhint %}

## Open Payment

To open Payment:

1. Go to **Action Pages > Pages**.
2. Hover over the page you want to edit.
3. Click **⋮ > Edit**.
4. Select **Finance > Payment**.

## Choose Payment Methods

Check the box next to each method you want to offer, and uncheck the ones you don't. Then click **Save**.

**Primary payment methods** (at least one is required):

* Credit card
* Business direct debit (ACH)
* Personal direct debit (ACH)

**Additional payment methods:**

* Apple Pay
* Google Pay
* PayPal and Venmo
* Bitcoin

New pages start with every method on except Bitcoin.

* **Venmo:** Venmo doesn't have its own checkbox. It's offered automatically when PayPal is on and your account's PayPal merchant account is active.
* **Bitcoin:** Bitcoin is optional and off by default. To offer it, check **Bitcoin** and click **Save**. You don't need to contact Anedot to turn it on.

{% hint style="warning" %}
If you turn off PayPal on a page that has PayPal recurring gifts, those gifts can't process on their next dates. Check your recurring gifts before you turn off a method.
{% endhint %}

To learn more about each method, see [Payment Methods](/get-started/anedot-101/payment-methods.md).

## Set Who Covers Fees

**Cover the fees** controls whether donors can cover the processing fee on their gift. Choose one:

* **Organization pays fees (default):** No fee option shows on the page.
* **Donor can opt out of paying fees:** The fee checkbox shows and starts checked.
* **Donor can opt in to paying fees:** The fee checkbox shows and starts unchecked.
* **Donor always pays fees:** The fee is added to every gift, with no checkbox.

See [Donor Covers Fees](/action-pages/advanced-features/donor-covers-fees.md).

## Set Transaction Limits

**Transaction limits** set the smallest and largest gift allowed on the page.

* **Per transaction minimum:** At least $1. New pages start at $1.
* **Per transaction maximum:** Up to your account's limit. New pages start at $25,000.

The maximum must be greater than the minimum. When a donor covers fees, the total with fees counts toward the limits.

{% hint style="info" %}
To accept gifts above your account's maximum, contact our Support team.
{% endhint %}

## Related Articles

* [Payment Methods](/get-started/anedot-101/payment-methods.md)
* [Donor Covers Fees](/action-pages/advanced-features/donor-covers-fees.md)
* [Giving Amounts and Frequencies](/action-pages/page-builder/giving-amounts-and-frequencies.md)
* [Page Builder Overview](/action-pages/page-builder.md)


---

# 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://docs.anedot.com/action-pages/page-builder/payment-methods-and-fees.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.