> 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/get-started/anedot-101/payment-methods.md).

# Payment Methods

See which donor payment methods Anedot supports, including cards, ACH, Apple Pay, Google Pay, PayPal, and Bitcoin, and how to turn each one off for a page.

**Anedot** supports multiple payment methods, so donors can give with the option that works best for them. Most options are on by default, and you manage them in **Action Page Builder > Finance > Payments**.

## Available Methods

| Method                 | Notes                                                          |
| ---------------------- | -------------------------------------------------------------- |
| Credit and debit cards | Visa, Mastercard, Discover, and American Express               |
| ACH (bank draft)       | Direct payments from a donor's checking or savings account     |
| Apple Pay              | Apple devices using Safari                                     |
| Google Pay             | Compatible browsers and Android devices                        |
| PayPal                 | PayPal account or linked card                                  |
| Bitcoin                | Optional (through OpenNode), enabled in **Finance > Payments** |

## Apple Pay

Apple Pay is available to all Anedot customers with no setup required. It appears automatically on donation forms when the donor is eligible.

Donor requirements:

* An Apple device (iPhone, iPad, iMac, or MacBook).
* The Safari browser.
* Apple Pay enabled on the device.

How it works:

* Anedot handles the SDK, encryption, and security policies.
* Apple Pay doesn't work in embedded forms (iFrame) because of Apple's security restrictions. Supporters are redirected to a hosted page to complete the purchase.

If Apple Pay shows an error, the donor's Apple Pay profile may be missing their Full Name, Email, Phone, or Address.

To turn off Apple Pay, go to **Action Page Builder > Finance > Payments**.

## Google Pay

Google Pay is on by default and appears automatically for eligible supporters.

Donor requirements:

* A compatible Android device or web browser.
* A Google account.
* A standalone hosted form. Google Pay isn't available on embedded forms.

How it works:

* If you promote Google Pay outside Anedot, follow the Google Pay Web Brand Guidelines and API Terms of Service.
* Google Pay doesn't work in embedded forms (iFrame). Supporters are redirected to a hosted page.

If Google Pay fails, the donor's Google account may be missing their Full Name, Email, Phone, or Address.

To turn off Google Pay, go to **Action Page Builder > Finance > Payments**.

## PayPal

Donors can give from a PayPal account or with a card through PayPal. PayPal is on by default for fundraising accounts.

* You don't need to set up a PayPal account.
* PayPal donations appear in your Anedot balance and transfer as usual.

If a donor has trouble with PayPal:

* Make sure every donation form field is filled in.
* Refresh the page or try another browser.
* Turn off popup blockers if the PayPal window doesn't open.

To turn off PayPal, go to **Action Page Builder > Finance > Payments**.

## Bitcoin (Via OpenNode)

Bitcoin is optional and off by default. Enable it in **Action Page Builder > Finance > Payments**. You don't need to contact Anedot.

How it works:

* Bitcoin is only available for supporters who aren't signed in to DonorID.
* It's displayed under Express Checkout when enabled.
* The final payment processes on OpenNode's secure platform.
* Bitcoin can't be used for recurring donations.
* Bitcoin gifts are one-time only, and the amount uses the real-time exchange rate.

### Bitcoin Refunds and Underpayments

* Bitcoin donations can't be voided or refunded through Anedot. Organizations manage refunds manually.
* Underpayments may happen because of fees or miscalculations. The donor may complete the remaining amount through OpenNode or request a refund, or Anedot may accept the underpaid amount and adjust the donation in your records.

To learn more, see [OpenNode underpayments help](https://help.opennode.com/en/articles/3706323-underpayments-aka-partial-payments).

## Related Articles

* [Pricing](https://docs.anedot.com/get-started/anedot-101/pricing.md)
* [Donor Covers Fees](https://docs.anedot.com/action-pages/advanced-features/donor-covers-fees.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/get-started/anedot-101/payment-methods.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.
