Glossary · Account · 4 min read

Doing Business As (DBA)

A DBA lets you do business under a name different from your personal or legal entity name. It can connect your public-facing brand to your business, but it does not create a new entity or directly change card-processing rates.

Also called: Trade name, Trading as

What a DBA is

A Doing Business As name is the name you use with customers when it differs from your personal name or your business’s formal legal name. A sole proprietor named Jordan Lee, for example, could operate a bakery as Cedar Street Bread. An LLC or corporation can also use a different public-facing name.

A DBA is a name, not a separate business entity. Registering one does not create a new company, provide liability protection, or give you trademark rights. Trademark rules still apply, and another business in your state could use the same DBA. Treat the name as a way to identify your business, not as exclusive ownership of a brand.

Your DBA helps customers recognize your business, but it does not create a company or lower card-processing rates.

Where registration fits

Registration rules depend on your business structure and location. A state, county, or city can require a filing, and most states require registration when you use a DBA. There is no single nationwide filing process or deadline in the research available here, so identify the requirement through the local government office that handles business names before you use the name.

A DBA can also help align your public-facing name with your business banking and payment activity. The SBA notes that a DBA and federal tax ID number can support opening a business bank account. A DBA alone does not guarantee account approval or establish a new legal identity.

How it shows up in payments

When you set up card acceptance, the name you provide can be used to identify your business on a customer’s card statement. That statement name is often called a descriptor. The DBA and descriptor are connected, but the exact text a cardholder sees depends on how the payment is configured and displayed.

Use a name customers recognize from your storefront, website, or receipt. If a customer pays Cedar Street Bread but sees an unfamiliar legal entity name on a statement, they could mistake the charge for fraud and dispute it. A clearer business name helps customers connect a transaction to their purchase. This is a dispute-prevention step, not a way to lower interchange or network fees.

What it means for your costs

A DBA does not change the three components of card-processing cost: interchange, network fees, and processor markup. The research notes identify no standard DBA-specific processing charge. Local filing costs are separate from card fees, and the research does not establish a single registration price.

If you are reviewing a payment statement, compare the name customers see with your checkout brand and receipts. Also check whether the statement lists a separate DBA-related charge before assuming it is a standard card-network fee. A DBA itself does not make your transaction rates cheaper or more expensive.

What you can actually change

  1. Confirm local filing rules. Check the state, county, or city office responsible for business-name registration. Requirements depend on your location and business structure.
  2. Match the customer-facing name. Use a name on payment records that customers can connect to your storefront, website, and receipt. Review a test transaction’s card statement display if available.
  3. Separate name from fees. If a processor lists a DBA-related charge, identify the exact line item and amount. Do not confuse a local registration fee with interchange, network fees, or processor markup.

Frequently asked questions

Does a DBA create a separate business?

No. A DBA is an operating name, not a separate legal entity. It does not create liability protection or trademark rights, so the underlying owner or business entity remains responsible for the business.

Do I have to register a DBA?

That depends on your business structure and location. A state, county, or city may require registration, and most states require it when you use a DBA. Check the relevant local government office for the rule that applies to you.

Does a DBA change my payment-processing fees?

A DBA does not change interchange, card-network fees, or processor markup. The research identifies no standard DBA-specific processing fee. A local name-registration charge, if applicable, is separate from your card-processing costs.

Will my DBA appear on a customer's card statement?

The business name you provide for payment processing can be used to identify your business on a card statement, often through the transaction descriptor. The exact text depends on how the payment is configured and displayed.

Readytostartsaving?

Tell us about your volume and we'll estimate what you could save. Free, with no obligation. If you save nothing, we charge nothing.

Customer type
Current processor
How do you take payments?
Net effective rate0.00%