> For the complete documentation index, see [llms.txt](https://learn.withessential.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://learn.withessential.com/administration/settings/set-a-minimum-charge-for-credit-card-fees.md).

# Set processing fees and pass Stripe fees to customers

The Processing Fees card lets you configure credit card and ACH/bank fees independently. Each payment method has a picker with three choices — select one and then **Save**:

* **No fee** — the customer pays only the invoice amount.
* **Exact Stripe fee** — pass Stripe's standard fee through to the customer.
* **Custom percentage** — enter your own rate (it must be above 0; use No fee for zero).

Exact mode adds enough to the customer's total to cover Stripe's fee on the full amount, including the processing fee itself. This leaves the original invoice amount after Stripe deducts its standard fee. The standard fees are:

* Credit cards: 2.9% + $0.30 in the business's currency.
* US ACH: 0.8%, capped at $5.00.
* Canadian pre-authorized debit: 1% + CA$0.40, capped at CA$5.00.

Below the two pickers, **Allow waiving processing fees per invoice** turns on fee waivers (it is off until you turn it on, and it saves with the card's **Save**). With it on, invoices get a **Processing fees** option under **Additional options**, and customer and property billing get a **Never charge processing fees** option that makes new invoices start with fees waived. A waived invoice is paid at its invoice amount with no fee on any payment method. Turning the setting off charges your standard fees on every invoice again, including invoices that were waived; turning it back on restores those waivers. See [Waive processing fees on an invoice](/revenue/invoices/waive-processing-fees-on-an-invoice.md).

Saving the Processing Fees card or the Credit Card Fee Threshold re-prices payments customers haven't finished yet. A customer who picked a payment method on the pay page but never confirmed has an unfinished attempt at the old fee; Essential cancels those attempts when you save, and their next attempt uses the new settings. A payment the customer has already confirmed keeps the fee they were shown. If Essential can't cancel one of those unfinished attempts, the save still goes through and you'll see a message asking you to save again to retry.

The Credit Card Fee Threshold is available only while the credit card fee is set to a custom percentage — its controls are disabled otherwise. Turn on **Only apply custom credit card fees at or above a minimum**, enter the amount, and select **Save**. Charges below the threshold carry no card fee. Exact credit card fees apply to every card payment and ignore this threshold. ACH/bank fees are never affected by it.

> **Where to find it:** Settings → Invoicing → Payments, in the Processing Fees and Credit Card Fee Threshold cards

## Related guides

* [Waive processing fees on an invoice](/revenue/invoices/waive-processing-fees-on-an-invoice.md)
* [Connect QuickBooks to sync accounting](/administration/settings/connect-quickbooks-to-sync-accounting.md)
* [Connect Stripe for payments and automatic sales tax](/administration/settings/connect-stripe-for-payments-and-automatic-sales-tax.md)
* [How your customer pays an invoice online](/revenue/invoices/how-your-customer-pays-an-invoice-online.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://learn.withessential.com/administration/settings/set-a-minimum-charge-for-credit-card-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.