Stripe caps the complete card statement descriptor at 22 characters, built from a 2-to-10-character prefix plus an optional per-charge suffix, and it must reflect your business or DBA name (Stripe statement descriptor docs, checked Nov 2026). That small space decides whether a customer recognizes your charge or calls their bank.
A billing descriptor is the text on a card or bank statement that tells a customer who charged them. We treat it as a consistency check across the storefront, the DBA, the underwriting file and every payment route.
An honest match to the business the processor approved is the only version that works.
Peptide Marketing HQ builds and reviews research-use-only stores for a living, so we see the same descriptor problems again and again. A store has a primary route and a backup route, and the two bill under different names. The site says one thing, the application says another, and the bank statement says a third.
This post gives you a descriptor register and a WooCommerce test plan to catch those gaps. We also say plainly what we won't do: we don't pick descriptors to hide a product type.
What do customers actually see on a statement?
Most "I don't recognize this charge" disputes start with a mismatch. The customer remembers the brand on the website. The statement shows something else, so they assume fraud and dispute it.
Ranking pages blur four terms together. Keep them apart:
- Billing descriptor: the general name for the text a customer sees on a card or bank statement.
- Statement descriptor: the label many processors use for that same customer-facing text, which they set at the account or charge level.
- Merchant name: the name field in the card network record for the charge.
- Payout statement name: the text on your own bank deposit. This is a different field. Shopify, for example, has a payout statement name that is separate from the customer billing statement.
The first three can all appear on a customer's card statement. The fourth never does. Founders who see one name on deposits, another in the processor dashboard and a third on customer statements are usually looking at these separate fields.
Network limits are not the whole story
In the clearing record your processor sends to the card networks, the merchant name field typically holds 25 characters. A separate 13-character field often carries contact details for online or phone sales. That contact field can hold a phone number, URL or email.
Issuers can shorten or reformat what they display. The same charge can look different at two banks. No single format is safe everywhere, which is why we test instead of assuming.
For the wider dispute playbook, read our earlier post on peptide chargeback prevention. This one stays on the descriptor itself.
Character limits and descriptor types by route
The descriptor is not one setting. Each route has its own fields, limits and owners.

Static versus dynamic descriptors
A static descriptor is one fixed piece of text set at the account level. Every charge shows the same name. A dynamic or soft descriptor adds a per-transaction piece, such as an order or product reference, where the route supports it.
Static is simpler and easier to audit. Dynamic can help a customer match a charge to an order. It also adds one more thing to test. We would not tell every store to use it.
Processor by processor
Stripe separates the account-level prefix from the per-charge suffix on card charges. The full descriptor runs 5 to 22 characters, the prefix 2 to 10, and the prefix and suffix are joined with “* ” inside that same 22-character limit. Dynamic suffixes only apply to card payments, so other payment methods show the full static descriptor.
Shopify Payments allows a customer billing statement name of 2 to 19 characters, and it has to reference your store, legal or DBA name, or URL (Shopify Help Center, checked Nov 2026). PayPal often adds its own PP* or PAYPAL * prefix before a shortened seller name. That prefix eats into the space you have, so a name that fits on one route may not read the same on another.
Acquirer-managed routes
On a high-risk acquiring route, the acquirer or gateway sets the descriptor fields and decides who may change them. A limit that applies to Stripe does not carry over to a second route. You may need to submit a request instead of editing a dashboard field.
We set up peptide payment processing with a backup route, and the descriptor is one of the first things we map for each one. Because this is route-specific, confirm the exact configuration with each processor. Dynamic suffixes may be unavailable on some payment methods or wallets, and that is where many surprises come from. If you are adding a second route, our guide to a high-risk payment gateway covers what to check first.
How much control you get over your descriptor depends on the processor. Our guide to the best high risk payment processors for peptide brands lists what to ask before you sign.
Pick the name, URL or phone number
Here is the decision rule. The descriptor should match the business the processor approved. It should also match the name on the storefront, footer, invoices and checkout. When those line up, customers recognize the charge and underwriting sees a consistent file.
Brand, DBA or legal entity
Say your store trades as Example Labs and customers see that name everywhere on the site. A good descriptor is a short version of that name, plus a support URL where the route allows it. The customer reads it and thinks, "That's the store I ordered from."
A bad descriptor is an unrelated legal-entity name or an ISO name that appears nowhere on the site. The customer has never seen "HOLDCO SERVICES LLC" and has no reason to link it to the order. Avoid unexplained parent-company names for the same reason.
If your legal entity and your trading name differ, the DBA is usually the bridge. The DBA record, the site footer and the descriptor should all tell the same story.
Should you add a URL or phone number?
Yes, where the field and the route allow it. A support URL or phone number lets a customer contact you before they call the bank. That one step can save you a dispute.
The contact field has its own length limit, so a long URL often has to be shortened. Pick a short, clean support domain or path that you actually monitor. Test how it displays before you commit.
What we won’t do
We do not choose or suggest a misleading descriptor to hide the product type from a processor, a bank or a platform. It backfires for three reasons:
- It breaks the match between the application and the live charges.
- Mismatch between the two is exactly what a reviewer looks for.
- It tends to end in a terminated account and a held balance.
A descriptor is not a way around underwriting. Swapping in an unrelated name does not lower your risk. It adds a visible inconsistency to the file.
Run a billing descriptor audit across every route
An audit takes an afternoon and catches most of the problems. Start with a register, then reconcile it against everything the underwriter can see.

Build the register
Keep one row per processor, gateway, merchant ID and backup route. Each row records:
- The live descriptor, including any prefix or suffix
- The DBA and the legal entity on that account
- The support phone, URL or email shown
- Who has permission to change it, and how
- The date of the last test charge
A store with a primary and a backup route often ends up with two different statement names without noticing. Each account was set up at a different time, by a different person, with different defaults.
Reconcile against the file
Compare the register with these items, in this order:
- Website header and footer
- DBA records
- Order confirmation emails and invoices
- Return policy
- The customer-service number
Compare against what the processor sends to the card networks, not just what the dashboard shows. The clearing data is the record that counts, not the settings screen.
This also matters for alert tools. Chargeback alert systems such as Ethoca and CDRN may rely on descriptor matching. Enrolling in an alert service usually means supplying your billing descriptor and every variation of it. Your register is the document you hand them.
Can you change it without reopening underwriting?
Policies differ by acquirer. A change is usually a request to the processor, and it may involve a review. Ask before you edit anything, and keep the approved application on file so you can show what was disclosed.
Treat the backup route as a first-class route
A different descriptor on a backup processor causes trouble. Customers billed under an unfamiliar name on a failover route are the ones most likely to dispute. The backup deserves the same match to the storefront as the primary. If a different name is unavoidable on some route, say so in the order and support experience instead of surprising the customer.
Fixing WooCommerce so every charge matches
The WooCommerce receipt can show one name while the bank shows another. The store name lives in WooCommerce settings. The descriptor lives in the gateway or processor account. Nobody syncs them for you.
The places a descriptor is felt
Check each of these for name, support contact and wording:
- Order confirmation and shipping emails
- Subscription renewal emails and renewal charges
- Refund emails and refund statement lines
- Digital wallet payments
- Packing slips
- Support scripts, so your team can say "you will see this name" and name it
Test with real charges
Place a low-value live charge on each route. Check it with more than one issuing bank and at least one wallet. Record what each statement actually shows. If it does not match the plan, fix the register and the route settings, then test again.
Finish this before you scale ads or email sends. A bad descriptor multiplies disputes along with volume. Testing first costs a few small charges.
Know the limit
A clean descriptor helps customers recognize a charge and supports your dispute evidence. It cannot fix prohibited product claims, human-use positioning or an inaccurate merchant application. It cannot cure a processor-policy problem either. If the file is wrong, the name on the statement is not the issue.
That is why our free store audit and compliance review look at the descriptor together with the site copy and the underwriting file.
We are one accountable team for the whole chain a peptide store needs to stay live: a compliant site that passes underwriting, high-risk payment processing with a backup route, SEO, email, labels and packaging.
If you want a second set of eyes on your billing descriptor register before you scale, ask for the free store audit and we will go through it with you.

