# Surcharge

Add a separately disclosed fee to eligible credit card payments.

Surcharge allows an enabled merchant to add a separately disclosed fee to an eligible credit card payment. The fee is intended to help the merchant offset credit card acceptance costs.

The surcharge is added to the amount authorized to the customer and is paid with the transaction to the merchant’s banking on file.

**Legal Notice**

This document is implementation guidance, not legal advice. Merchants should confirm current state and card-brand requirements with legal counsel and the applicable compliance owners.

### Key Benefits

- Lets eligible merchants recover part of their credit card acceptance cost where permitted.
- Provides card-type eligibility handling so debit and prepaid cards are not intentionally surcharged.
- Supports customer disclosure before payment submission and separate surcharge visibility in transaction notifications.
- Offers managed calculation in Deluxe-hosted experiences and a calculation workflow for direct API integrations.


### Capabilities

| Capability | Current Behavior | Developer Responsibility |
|  --- | --- | --- |
| Merchant-level configuration | Surcharge must be enabled and configured for the merchant. Product-level percentages are not supported today. | Confirm merchant onboarding and configuration before enabling the checkout experience. |
| Eligibility check | The surcharge calculation workflow evaluates the supplied amount and payment method against configured rules. | For direct API flows, check eligibility before displaying a surcharge. |
| Percentage-based fee | Merchant-defined percentage configuration, subject to the configured and permitted cap. | Do not hard-code a rate. Use the configured calculation result. |
| Customer disclosure | The surcharge must be displayed before the payment is submitted. | Show the surcharge and total clearly and allow the customer to stop the payment before submission. |
| Payment application | Direct API integrations submit the calculated surcharge with the payment. Hosted experiences calculate and apply it when configured. | Preserve the calculation result and submit the expected fee object for API payments. |
| Transaction notification | The Transaction webhook includes a Surcharge field. | Store the surcharge separately for receipts, support, and downstream reconciliation. |
| Refund handling | The surcharge object is not submitted on a refund. Merchant configuration governs whether the surcharge can be refunded; the developer submits the intended refund amount. | Apply the approved refund policy and do not assume automatic proration. |
| Channel automation | Embedded Payments can automatically calculate, display, and apply surcharge for eligible manual card entry. Hosted Payment Form includes calculation when an amount is provided and the merchant is configured. | Use the channel behavior described below and avoid duplicating fee logic. |


### Supported Channels

| Channel | Calculation and Application Model |
|  --- | --- |
| Direct Payments API | Call the surcharge calculation endpoint with the amount and payment method. The endpoint calculates the surcharge but does not add it to a payment. Submit the returned or calculated value with the authorization or sale. |
| Hosted Payment Form (HPF) | When an amount is provided and the merchant is configured for surcharge, HPF includes surcharge calculation. |
| Embedded Payments | For an enabled merchant, the SDK calculates, displays, and applies surcharge after an eligible card number is entered. |


### Eligibility and Payment Method Rules

- Only eligible credit card transactions may be surcharged.
- Debit and prepaid cards must not be surcharged, regardless of how they are processed.
- Embedded Payments does not apply surcharge to ACH or wallets.
- The direct API integrator should determine eligibility before presenting the fee to the customer.
- Does not support a separate product-level surcharge percentage.
- American Express is not supported for Surcharge.
- Surcharge is tied to an eligible credit card payment and merchant compliance obligations. It is not a replacement for split settlement, partner fees, or convenience fees.


### Compliance and Customer Experience

Surcharge rules vary by jurisdiction and card brand. The integration must treat compliance as a merchant and program requirement, not only as a calculation task.

| Checkout Stage | Required Experience |
|  --- | --- |
| Before implementation | Merchant verifies jurisdictional legality, program eligibility, notification requirements, and the permitted rate with the appropriate legal and compliance resources. |
| Payment-method entry | Collect enough card information to determine whether the card is surcharge-eligible. |
| Before submission | Display the base amount, surcharge, and total before the payment is submitted. The customer must be able to cancel the payment after seeing the surcharge. |
| Receipt | Show the surcharge as a separate line item. |
| Ongoing operations | Monitor rule changes, configured rates, cost-of-acceptance limits, and program compliance. |


### How the Amount Flows

For an eligible payment, the surcharge is added to the customer-facing total.

The full authorized amount, including the surcharge, is processed to the merchant banking on file.

The partner does not separately receive the surcharge merely because it provided the software integration.

| Value | Example |
|  --- | --- |
| Base transaction amount | $100.00 |
| Configured surcharge rate | 3.00% |
| Calculated surcharge | $3.00 |
| Customer total | $103.00 |


**Illustrative Calculation Only**

Use the surcharge calculation result from the configured Deluxe workflow. Do not rely on the arithmetic example as the source of truth for rounding, precision, currency, or cap enforcement.

### Ready to Implement?

**Explore the [Surcharge Implementation Guide →](/products/merchant-services/developer-resources/developer-guide/surcharge-integration)**