Skip to content
Wooligan Plugins

Why Shoppers Don't Recognize Your WooCommerce Charge — and How to Fix the Statement Descriptor

Unrecognized charges are a leading, preventable cause of WooCommerce disputes. Here is how to set, test, and explain your statement descriptor across Stripe, PayPal, and WooPayments.

· 6 min read

A shopper opens their banking app, sees a line they do not recognize, and has two reasonable options: search their email, or call the bank. The second path is a chargeback. By the time you hear about it, the fee and the deadline are already in motion, and the goods may already have shipped.

WooPayments is direct about this. A clear statement descriptor "can help reduce refunds and disputes," and the first item in its prevention guide is to set one (statement descriptor requirements; Preventing disputes). This is one of the cheapest prevention steps in payments, and one of the most often left at a default.

This post is the practical version: what a descriptor is, how the main WooCommerce gateways handle it, how to test what customers actually see, and how to explain the charge on the receipt so the bank never has to.

What a statement descriptor is, and what it is not

The statement descriptor is the short text that appears on a shopper's card or bank statement for a charge — and, usually, for a refund of that charge. It is not your invoice number, not your email subject line, and not your store's display name unless you have set it that way.

Rules vary by processor, but the pattern is similar:

  • Length is tight. WooPayments documents a range of 5 to 22 Latin characters for the descriptor, with tighter limits on suffix characters depending on the country (WooPayments descriptor requirements). Stripe's own docs use a similar short window. You will not fit a slogan.
  • Character set is limited. Special characters, emoji, and some punctuation get stripped or rejected.
  • The legal entity may still appear. Some issuers prepend or append a doing-business-as, a phone number, or a city. You do not fully control the printed line.
  • Banks rewrite things. The text you send is a request, not a guarantee of typography.

That last point matters. You cannot promise a shopper the exact typography of their bank app. You can promise a recognizable name, and you can tell them what you send.

Why the default is so often unrecognizable

WooCommerce stores are frequently named one thing in the theme, another in the legal paperwork, and a third in the domain. A common pattern:

  • Storefront: "Northside Supply"
  • Domain: northsidesupplyshop.com, truncated
  • Legal entity: NS Holdings LLC
  • Descriptor default: something inherited from the Stripe account, a truncated URL, or the legal name

A shopper who bought a week ago, maybe on a shared household card, has no reason to connect "NS HOLDINGS" to a sweater. That is not fraud in the usual sense. It is a missed recognition problem, which is why it shows up so often next to friendly fraud and chargebacks.

Subscriptions make this worse. A recurring charge weeks later has even less context than a one-time checkout. If you sell subscriptions, the descriptor and the reminder email have to do more work, not less.

Set the descriptor on every gateway you actually use

One store can take payments through WooPayments, a direct Stripe account, PayPal, a bank transfer plugin, and a second processor for a fallback. Each of those has its own settings screen. Changing the name in WooCommerce → Settings → General does not automatically fix them all.

Work through a checklist:

  1. List every live gateway and the environment (live versus test, plus any additional Stripe accounts).
  2. Open each processor's statement descriptor field. In WooPayments, that is documented under Bank statement descriptor. Stripe has account-level defaults and, in some setups, a per-payment suffix. PayPal and others have their own fields and limits.
  3. Choose a name a customer would say out loud. Prefer the storefront name over the legal entity if the rules allow it. If the legal name must appear, put the storefront name in the suffix or in the "soft descriptor" if your processor offers one.
  4. Avoid truncated domains. "NORTHSIDESUPPLYS" is worse than "NORTHSIDE SUPPLY" if you can have the space, or "NORTHSIDE" if you cannot.
  5. Add a phone or URL if the field allows it. WooPayments' prevention guide includes support details as a companion step. A number that reaches you is more useful than a marketing URL that 404s.
  6. Do this again when you add a gateway. Fallback processors are easy to forget, and they are often the ones used when a first payment fails — exactly when the shopper is already a little confused.

Descriptor Shield is being built to audit the descriptor on each connected gateway, warn when one is missing or unrecognizable, and keep a record of what was sent on each order. It is not for sale yet. Get notified at launch. Until it ships, a spreadsheet of gateways and a quarterly review is enough to stop the worst misses.

Place a real test order, then wait

The only reliable test is a charge on a card you control, in live mode (a small amount is fine), followed by a look at the actual statement. Test-mode dashboards do not show issuer rewriting.

When the line appears:

  • Would you recognize it without opening your email?
  • Does a refund of that charge use a similarly recognizable credit line?
  • Does a subscription renewal, if you have one, look the same?

If the answer is no, change the descriptor and test again. Do not assume a setting you saved last year is still what the processor sends.

Tell the shopper before they have to ask

The descriptor only works if the shopper can match it to the purchase. Put the same text in three places:

  • The checkout and the receipt. "This charge will typically appear as NORTHSIDE SUPPLY." WooPayments already recommends something in this spirit. Say "typically" because banks rewrite.
  • The shipping or download email. Repeat it there, with the order number and a support address.
  • A public "what is this charge?" page. A lookup by last four digits, amount, and date is more useful than a static FAQ, and it should be rate-limited so it cannot be used to fish for other people's orders. If no match is found, still offer a way to contact you.

Descriptor Shield is planned to show the descriptor on checkout and receipts and to host that lookup. You can publish a simpler version of the page today: explain the usual wording, link to support, and ask for the date and amount.

Support Snap is planned to put the same wording into a ready support reply, so "what is this charge?" does not require searching settings. Coming soon; get notified at launch.

When an unrecognized-charge dispute still arrives

Prevention is not a guarantee. When a dispute reason is "I do not recognize this charge":

  • Respond on time. WooPayments is clear that doing nothing is an automatic loss, including on cases the customer later withdrew (Managing disputes).
  • Include the descriptor you used, a copy of the receipt that mentioned it, and any "what is this charge?" exchange.
  • Include delivery or download proof if the goods already went out.
  • If the customer contacts you at the same time, a refund may still be cheaper than the dispute fee — but coordinate so you do not refund and lose the dispute, or vice versa, without a record.

Dispute Desk is planned to assemble that pack and watch the deadline. Coming soon; get notified at launch. The chargebacks post covers the rest of the evidence workflow.

A short monthly habit

Once a month, or whenever you add a payment method:

  1. Confirm the descriptor on every live gateway.
  2. Place or review one live test charge if anything changed.
  3. Confirm the receipt and the "what is this charge?" page still match.
  4. Glance at recent disputes whose reason is an unrecognized charge. If they cluster after a descriptor change, you have a clue.

This is unglamorous work. It is also one of the few chargeback controls that does not require a new fraud model, a new policy, or a new fee. Make the line on the statement say the name of the store the shopper thought they were buying from. Then say it again on the receipt, so they never have to guess.