> For the complete documentation index, see [llms.txt](https://docs.sensepass.com/sensepay/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sensepass.com/sensepay/partners/partner-dashboard/surcharge.md).

# Surcharge

Surcharge settings are set for the merchant and inherited by each location. On the location level you can override them.

1. In the left menu, open **Management** and click **Surcharge**. Check the merchant and location at the top of the page.
2. The page shows whether the location inherits the merchant settings, for example "Merchant surcharge (applied to this location): Disabled".
3. To use different settings for this location, turn on **Override Merchant Surcharge Configuration**. The settings below appear.
4. Set the options and click **Save Configuration**. To go back to the saved values, click **Reset**.

<figure><img src="https://3556089516-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MbqMA3Kf8t2xEX9F6y9%2Fuploads%2FK4kMDcTh41kgLVzqslKs%2Fp-surcharge-1.png?alt=media" alt="Surcharge page with Override Merchant Surcharge Configuration turned on"><figcaption><p>Surcharge page with Override Merchant Surcharge Configuration turned on</p></figcaption></figure>

| Setting                | What it does (text shown in the dashboard)                                                                                                                                                                              |
| ---------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Enable Surcharging     | When enabled, surcharge rules are applied to transactions based on payment method.                                                                                                                                      |
| Location Type          | **E-commerce**: customers select their US state at checkout, and that state is used for surcharge rules. **In-store**: surcharge is calculated using the state you select, even when billing is enabled.                |
| Surcharge Display Name | The text customers see for the additional charge, for example "Processing Fee", "Card Fee", "Convenience Fee" or "Surcharge".                                                                                           |
| Refund Configuration   | **Full Refund**: the customer gets back the original amount plus the surcharge. **Partial Refund**: the customer gets back the original amount only.                                                                    |
| Surcharge Rules        | Click **+ Add Rule** to add a rule per gateway and card brand or wallet: Gateway, Surcharge Target, Type, Value and Apply To. Cards with an unknown funding type (credit or debit not determined) are never surcharged. |
| Preview                | **Customer Payment Page Preview** and **Preview Calculator** show the surcharge for a sample amount, gateway and target.                                                                                                |

{% hint style="warning" %}
**Important:** You are responsible for making sure that surcharges and service fees comply with card network rules and local laws. SensePass does not provide legal advice.
{% endhint %}


---

# 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.sensepass.com/sensepay/partners/partner-dashboard/surcharge.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.
