Skip to main content

Configuring Credit Card Processing Fees in X-1FBO

Flexible Options for Applying CC Processing Fees to Invoices

Written by Jessi McCombs

Overview

Credit card (CC) processing fees in X-1FBO can be configured in different ways depending on how your operation invoices customers and handles payment types. This guide outlines the two supported setup methods, along with when each approach may be most beneficial for your operation.

Both methods are fully supported within X-1FBO, and the best option will depend on your operational workflow and desired level of automation.

Method

Best For

Manual Control

Automation

Line Item Method

Flexible invoicing workflows

High

Partial

Tax Configuration Method

Standardized fee application

Low

High

There are two primary ways to apply credit card processing fees in X-1FBO:

  1. Line Item Method

    • Add the fee as a product/service line item

    • Optionally default it onto invoices

    • Adjust or remove it during invoicing

  2. Tax Configuration Method

    • Configure the fee under Pricing → Tax Settings

    • Apply fees automatically based on system rules


Option 1: Line Item Method

This is the most flexible and commonly used approach.

Setup Steps

Navigate to:
FBO Settings → Products & Services

Create a new Product/Service:

  • Master Name: Admin/Commissions Fee

  • FBO Item Name: CC Processing Fee (or similar)

  • Item Type: Service

Optional Default Configuration

To automatically include the fee on every invoice created fro the request:

  • Set From Request To Invoice to: Default

💡Not recommended if you only apply credit card processing fees to certain payment methods, as the fee will populate on all invoices by default regardless of the payment type used.


How It Works

If configured as a default item, the fee will automatically populate on invoices.

At the time of invoicing, users can:

  • Adjust the amount

  • Apply it selectively

  • Remove it if not applicable

This approach provides flexibility while still allowing partial automation.

If the item is not configured as a default, users will need to manually add the CC Processing Fee line item to the invoice when applicable.


⚠️ Important Notes

  • Percentage-based calculations are not fully automated

  • Users must manually enter the applicable percentage amount when needed

Best For

This method is ideal for FBOs that:

  • Only charge CC fees in certain situations

  • Need flexibility per transaction

  • Prefer staff oversight during invoicing


Option 2: Tax / Fee Configuration Method

This method uses the Taxes & Fees framework for more standardized application.

Setup Steps

Navigate to:
Pricing → Tax Settings

Create a new Tax:

  • Name: Credit Card Processing Fee

  • Configure it as a Goods & Services Tax (or similar)

Define:

  • Percentage or fixed rate

  • Applicable product/ service category

Configure Conditions:

  • Global application

  • Payment method–specific rules

  • Other applicable conditions


How It Works

The fee is automatically applied based on the configured rules and behaves similarly to taxes within the system.

Updates to the fee configuration function like pricing or tax changes and will not retroactively update existing invoices.


⚠️ Important Notes

  • Requires careful initial configuration

  • Minimal manual effort is required after setup

Best For

This method is ideal for operations that:

  • Prefer automated fee application

  • Use standardized billing workflows

  • Want minimal staff interaction during invoicing


Summary

Whether your operation prefers greater control during invoicing or a more automated fee application process, X-1FBO provides multiple configuration options to support different billing workflows and operational preferences.

The Line Item Method is commonly used by operations that want flexibility at the invoice level, while the Tax Configuration Method is often preferred by operations seeking more standardized and automated fee application.


Need more help? Contact X‑1FBO Support for further assistance

Did this answer your question?