> ## Documentation Index
> Fetch the complete documentation index at: https://docs.firmhouse.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Disable charging non-paying customers

> Stop Firmhouse from triggering new charges on subscriptions marked as non-paying to avoid expensive chargeback fees on repeatedly failing accounts.

To prevent expensive chargeback fees, you can configure your Firmhouse project so that it will not attempt to trigger charges for subscriptions that have the **Non Paying** status.

Especially when using a payment method like SEPA direct debit, costs could add up to between €7.50 - €15 per initiated transaction if your customer turns out to be out of funds or the customer or bank deliberately declines your SEPA transaction.

When your project is configured in this mode, all billing and invoicing processes will still run as normal. Your customer will still get an email on every billing cycle, and Firmhouse will still generate an invoice in your project. From a revenue and service standpoint, the customer is still entitled to pay and the invoice will still be generated. The payment status of the invoice will be marked as "open" and will be treated as an outstanding invoice. Instead of charging the customer's payment method, Firmhouse will skip this step.

In this mode, Firmhouse will not initiate the transaction at the PSP during the billing cycle. Thus your customer will be required to pay for their invoices manually via payment link.

## How to Disable Automatic Charging

### Steps

1. From the **Settings** section in your Firmhouse project sidebar, go to **Payment Dunning**.

2. Scroll down to the **Non-paying status** section.

3. Under **Recurring payments**, disable the checkbox to **Attempt to charge non-paying customers**.

![Payment Dunning settings with non-paying status section](https://mintcdn.com/firmhousebv/g8bqJWr1zBQmcUn3/images/docs-configure-payment-dunning-disable-charging-non-paying-settings-dev-bg3-aa.png?fit=max\&auto=format\&n=g8bqJWr1zBQmcUn3\&q=85\&s=afa57a319ede1b7fb81f72694b9c719f)

4. Click **Save changes**.

## Continue charging virtual products

You can make an exception for invoices containing only virtual products:

1. In **Settings → Payment Dunning → Non-paying status → Recurring payments**, disable **Attempt to charge non-paying customers**.
2. Enable **Continue charging non-paying customers for virtual products only**.
3. Click **Save changes**.

This exception is disabled by default. Its checkbox is only available when **Attempt to charge non-paying customers** is turned off. A virtual product has **Requires shipping** turned off in its product settings. Firmhouse uses the shipping requirement recorded when each invoice line was created, so later product edits do not change whether that invoice qualifies. Physical products elsewhere on the subscription do not affect the exception.

Invoices containing physical products remain uncharged, including invoices that mix physical and virtual products. Discounts and promotions do not prevent a virtual-only invoice from being charged. Invoices containing charges without an identifiable product, such as a standalone plan fee, do not qualify for the exception. Older invoice lines without a recorded shipping requirement do not qualify either.

## Adding Content to Your Email for Non-Paying Customers

Every billing cycle email will still be generated as normal. If the virtual-products exception is disabled, you can tell non-paying customers that their invoices will not be charged automatically.

If the exception is enabled, non-paying status alone does not mean the current invoice will remain uncharged: an eligible virtual-only invoice can still be charged. Use neutral wording that applies in either case when adding content with the `{{subscription.marked_as_non_paying?}}` Liquid tag:

```liquid theme={null}
{% if subscription.marked_as_non_paying? %}
<p>We have been unable to collect one or more previous payments. Please review any outstanding invoices in your account.</p>
{% endif %}
```


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.