# The Name on Your Customer's Statement (Descriptors)
Source: https://paymentsandrisk.com/docs/chargebacks/prevention/descriptors-and-comms

Last updated 4 November 2026.

TL;DR

-   **"I don't recognize this charge"**: check your descriptor and confirmation emails first
-   Fix your descriptor: lead with your customer-facing brand name, test on actual bank statements
-   Send confirmation emails immediately: include billing descriptor preview so they know what to expect
-   Subscription renewal reminders before the charge. Trial conversions carry their own notice duties, so check the [recurring billing rules](https://paymentsandrisk.com/docs/compliance/subscriptions/recurring-billing/). A cancellation usually costs less than a dispute you'd lose; run your own numbers
-   The descriptor fix is usually a settings change. Ask your processor what it charges, if anything, and count your own time

Your customer looks at their card statement and sees a line they don't recognize. That line is your billing descriptor, the short text next to the amount they paid. It's usually the only clue they get about who charged them. When it reads as random letters, "I don't recognize this charge" can follow. Recognition helps. It isn't proof the customer authorized the charge, and it won't stop every dispute. A customer who recognizes the charge has one less reason to file a chargeback. Confirmation emails landing in spam make recognition worse.

The fix is usually cheap to make: a settings change, plus whatever your processor charges and your own time. Track recognition-related disputes before and after it, on the same product and payment channel. Don't assume the drop. Count it.

## What Matters

1.  **Your descriptor is your first defense.** If customers can't recognize you, some will dispute first and ask later.
2.  **Post-purchase communication confirms the transaction.** Silence breeds confusion.
3.  **Subscription renewal reminders remove the surprise.** A charge the customer saw coming is harder to call unauthorized.
4.  **Dynamic descriptors add context.** Order numbers, product categories, location identifiers.
5.  **Mobile statement views are tiny.** Test what customers actually see.

* * *

## Upload Your Logo. It's Free and Takes Minutes

Do this before anything else on this page.

Ethoca is Mastercard's. It runs a free program that puts your logo beside your charge in participating banks' apps. Your customer opens the app. Sees an unfamiliar line. Sees your logo next to it. Some disputes die right there. The logo doesn't prove the customer authorized the charge, and banks that haven't switched it on won't show it.

Ethoca's own words: "We're inviting merchants around the world to upload their logos... The best part? It's free of charge!"

**Where to go:** [logo.ethoca.com](https://logo.ethoca.com/). Upload the logo, consent to its use. That's the whole job.

Two catches. Only participating issuers show it, so coverage isn't everywhere. And the logo is just the visual half of Consumer Clarity. The rest pushes itemized receipts and your contact details into the same screen. See [chargeback alerts](https://paymentsandrisk.com/docs/chargebacks/prevention/alerts/#consumer-clarity).

**Why it matters more than it sounds.** Ethoca's 2021 Consumer Clarity brochure says **77% of surveyed consumers often couldn't recognize transactions in online statements, and 96% wanted more purchase detail in their banking app**. It doesn't give the survey dates, geography or sample size. These are survey responses, not a promised dispute reduction. VENDOR [Ethoca brochure](https://www.ethoca.com/sites/default/files/documents/BROCHURE%20-%20Consumer%20Clarity%20for%20Merchants%20%28June%2029%2C%202021%29.pdf), page 2, accessed 2026-10-22.

* * *

## Fixing Your Billing Descriptor

Your billing descriptor appears on the cardholder's statement. If it doesn't clearly identify you, recognition disputes are likelier. Your own dispute list tells you how much likelier.

### What Customers See

| What You Intended | What They See | Result |
| --- | --- | --- |
| Acme Pet Supplies | ACME\* PYPMT | "What's PYPMT? I'll dispute." |
| Smith Consulting LLC | SQ \*SMITH CO | "I don't know SQ." |
| Online order from your store | STRIPE\* \[RANDOM\] | "Never heard of STRIPE." |

### Descriptor Anatomy

Many descriptors have two parts. The limits belong to your processor, the script and the payment method, not to statements in general. Stripe's published rules are one worked example:

| Component | Characters | Example |
| --- | --- | --- |
| **Static prefix** | Stripe shortened prefix: 2-10 chars | Company name or brand |
| **Dynamic suffix** | What fits in the total after the prefix and separator | Order ID, location, product |

Total length: Stripe's standard Latin descriptors run 5-22 characters, separator included. Other processors, scripts and payment methods differ, and each issuer decides how much of the text it shows. Ask your processor for your limit instead of designing to a universal one.

### Descriptor Best Practices

**Do:**

-   Lead with your customer-facing brand name
-   Include a phone number or URL if space allows
-   Test on actual bank statements (not just processor dashboard)
-   Keep it consistent where your processor lets you. Prefixes and formats can be fixed per payment method

**Don't:**

-   Use corporate entity names customers don't know
-   Let processor defaults stand ("STRIPE\*" or "SQ\*")
-   Assume what you enter is what they see
-   Use abbreviations that only make sense to you

### Testing Your Descriptor

1.  Check the descriptor in your processor's settings and supported test environment
2.  After a genuine customer purchase posts, ask what appeared on the statement
3.  Check desktop and mobile banking apps
4.  Ask: "Would I recognize this if I forgot I bought something?"

### Changing Your Descriptor

Contact your processor. Common steps:

1.  Request descriptor change in processor dashboard
2.  Submit required documentation (may need business verification)
3.  Ask when the change applies to new payments; the provider and issuer control timing
4.  Review the descriptor on new payments and compare a genuine purchase's posted statement
5.  Verify on bank statement

Ask Your Dev

"What's our current billing descriptor? Where do I change it, and how long does it take to update?"

* * *

## Dynamic Descriptors

Dynamic descriptors add transaction-specific information to help customers recognize charges, where your processor supports them. What you can vary is usually the suffix. On Stripe card charges, your account prefix stays put and the suffix changes; non-card payments and invoices behave differently. Check your own setup before designing around these examples.

### What You Can Add

| Suffix Type | Example | Best For |
| --- | --- | --- |
| **Order number** | ACME #12345 | E-commerce |
| **Product category** | ACME SHOES | Multi-product stores |
| **Location** | ACME NYC | Multi-location retail |
| **Service type** | ACME MONTHLY | Subscriptions |
| **Date reference** | ACME OCT2024 | Recurring billing |

### Multi-Brand Businesses

If you operate multiple brands under one merchant account:

| Approach | Descriptor | Trade-off |
| --- | --- | --- |
| **Parent company only** | ACME HOLDINGS | The name may not match any storefront the customer used |
| **Primary brand + product** | PETSHOP DOGFOOD | Names the storefront and what was bought, if both fit |
| **Brand as prefix** | PETSHOP\* ORDER | Puts the storefront first, if your processor lets the prefix vary |

Ask your processor what can actually vary per transaction, and under which brand or DBA rules. These strings are examples to test against your own statements, not a measured ranking. Your recognition disputes before and after are the score.

### Character Limits and Truncation

There is no universal statement width to design to. Your processor sets the input limit; each issuer decides how much it renders, on paper and on a phone alike:

| Item | Limit |
| --- | --- |
| Stripe total, standard Latin | 5-22 characters, separator counted |
| Stripe shortened prefix | 2-10 characters |
| What the customer sees | Set by the issuer's rendering. Check genuine posted statements |

**Front-load the important stuff.** Put your brand in the prefix, whatever its length limit is, because truncation eats the end first.

### Processor Support

Not all processors support dynamic descriptors. Ask:

-   "Do you support dynamic descriptors?"
-   "What's the character limit for the dynamic portion?"
-   "How do I pass the dynamic portion via API/dashboard?"
-   "Is there an additional cost?"

* * *

## Post-Purchase Communication

Confirmation emails are your receipt. If they don't arrive or don't make sense, customers doubt the purchase.

### Confirmation Email Essentials

Send immediately after successful payment:

| Element | Why It Matters |
| --- | --- |
| **Brand name and logo** | Visual recognition |
| **Order number** | Reference for support |
| **What they bought** | Line items with descriptions |
| **Amount charged** | Exact dollar amount |
| **Payment method** | "Visa ending in 1234" |
| **Billing descriptor preview** | "This will appear on your statement as ACME #12345" |
| **Support contact** | Phone, email, or chat link |

### Shipping/Delivery Confirmation

For physical goods:

| Element | Why It Matters |
| --- | --- |
| **Tracking number** | Proof of shipment |
| **Carrier and link** | Easy tracking access |
| **Expected delivery** | Sets expectations |
| **Delivery confirmation** | "Your order was delivered to \[address\]" |

For digital goods:

| Element | Why It Matters |
| --- | --- |
| **Access link** | How to use what they bought |
| **Download confirmation** | "Your download started" |
| **License/activation key** | A useful record. On its own it doesn't prove the customer received or used anything. Keep the access, download or use logs tied to the sale too |

### Email Deliverability

Your emails need to arrive. Check:

-   [ ]  Sending from your domain (not generic @gmail)
-   [ ]  SPF, DKIM and DMARC set up: email checks that help your receipts reach the inbox (ask your developer)
-   [ ]  Transactional emails separate from marketing
-   [ ]  Not triggering spam filters (test with mail-tester.com)
-   [ ]  "From" name matches your brand

Ask Your Dev

"Are our transactional emails going to spam? What's our delivery rate? Do we have SPF/DKIM set up?"

* * *

## Subscription Communication

Recurring charges draw "I didn't authorize this" disputes when the customer forgot they agreed. Communication is how you stop the surprise. Some reminders aren't optional: trial conversions and long-interval plans carry notice duties under network rules and state auto-renewal laws. Those duties live in [recurring billing](https://paymentsandrisk.com/docs/compliance/subscriptions/recurring-billing/). The cadence below is a starting point to check against them, not the rule itself.

### Renewal Reminders

Start with 7-14 days before renewal, then check it against the duties for your plans and customers:

```text
Subject: Your [Product] subscription renews on [Date]

Hi [Name],

Your [Product] subscription will renew on [Date] for [Amount].

Your payment method: Visa ending in 1234

If you want to cancel or change your subscription:
[Cancel Link] | [Manage Subscription Link]

Questions? Reply to this email or call [phone].

Thanks,
[Your Brand]
```

### Why Reminders Feel Scary, and What to Measure

Merchants worry reminders trigger cancellations. Run the comparison on your own numbers before you decide:

-   A customer who wants out cancels, or disputes. The reminder offers the cancel route first
-   A cancellation costs you the future charges. A dispute you lose can add the reversed sale, your processor's fee (minus anything a win refunds) and a count toward monitoring programs. Compare the outcome you'd actually get, not the worst case
-   Track cancellations and disputes on the same plans after you start reminding, and note anything else you changed at the same time. A before-and-after move is a signal from your shop, not proof the reminders caused it

### Annual Subscription Reminders

Annual subscriptions need more notice. This is an example cadence. Check it against the notice duties that actually cover your plans:

| Timeline | Communication |
| --- | --- |
| 30 days before | "Your annual subscription renews in 30 days" |
| 7 days before | "Renewal coming up on \[Date\]" |
| Day of | "Your subscription renewed today" |

### Renewal Confirmation

After charging:

```text
Subject: Your [Product] subscription renewed

Hi [Name],

Your subscription renewed today for [Amount].

This charge will appear on your statement as: [BILLING DESCRIPTOR]

Next renewal: [Date]

[Manage Subscription] | [Cancel] | [Get Help]
```

* * *

## Descriptor Clarity Checklist

Use this checklist to audit your descriptor and communication:

### Descriptor Audit

-   [ ]  Descriptor leads with customer-facing brand name
-   [ ]  Tested on actual bank statement (not just processor preview)
-   [ ]  Visible on mobile banking app
-   [ ]  Phone number or URL included if space allows
-   [ ]  Dynamic suffix adds useful context (order number, product), where your processor supports one
-   [ ]  Multi-brand transactions show the brand your processor's rules allow, checked on a genuine posted statement

### Communication Audit

-   [ ]  Confirmation email sends immediately on payment success
-   [ ]  Email includes brand name, order number, amount, and descriptor preview
-   [ ]  Shipping confirmation includes tracking
-   [ ]  Subscription renewal reminders sent before each charge (7-14 days is a starting point)
-   [ ]  Emails reach inbox (not spam)
-   [ ]  Easy access to support contact

* * *

## Test to Run

**2-week descriptor and communication audit:**

**Week 1: Discovery**

-   Check the descriptor in your processor's supported test environment, then ask a genuine customer what their posted statement shows. Don't run your own real card just to look: Stripe, for one, bans real payment details for live testing
-   Review confirmation email content and delivery
-   Audit subscription renewal communication
-   Check email deliverability metrics

**Week 2: Fixes**

-   Update descriptor to include brand name clearly
-   Add billing descriptor preview to confirmation emails
-   Implement or improve renewal reminders
-   Fix any email deliverability issues

**Success criteria:** the descriptor shows your brand name. Confirmation emails include a descriptor preview. Renewal reminders are on for every subscription, and you've tested all three.

* * *

## Scale Callout

| Volume | Focus |
| --- | --- |
| **Under $100k/mo** | Fix your descriptor and confirmation emails. Usually a settings change; ask about any processor charge, and measure the result |
| **$100k-$1M/mo** | Add dynamic descriptors. Implement renewal reminders. Track "unrecognized charge" disputes separately. |
| **Over $1M/mo** | Segment descriptor strategy by product line. A/B test communication timing. Analyze dispute reduction by communication type. |

* * *

## Where This Breaks

1.  **Payment facilitators with limited descriptor control.** If you're on Square, Stripe, or similar, your descriptor options are limited. Push for maximum customization within their constraints.

2.  **Legacy billing systems.** If your billing system is old, a descriptor change means development work. Price that work against your recognition disputes before you put it first.

3.  **International customers.** Descriptors can look different on non-US statements. If you've got real international volume, check what genuine customers in those markets see on their posted statements, with their consent.


* * *

## Analyst Layer: Metrics to Track

| Metric | What It Tells You | Target |
| --- | --- | --- |
| **"Unrecognized charge" dispute %** | Descriptor effectiveness | Compare the same product and payment channel before and after the fix |
| **Email open rate (confirmations)** | Engagement signal; privacy tools can distort it | Track your own baseline alongside delivery and support contacts |
| **Email click rate (renewal reminders)** | Customer awareness | Compare the same reminder type and customer segment |
| **Chargeback ratio change after descriptor fix** | Observed change, not proof of cause | Note anything else you changed in the same window |
| **Customer service "what is this charge" tickets** | Leading indicator | Trending down |

### Pre/Post Comparison

When you make descriptor or communication changes:

1.  Record the dispute count and sales count for one product and payment channel before the change
2.  Implement change
3.  Compare with the same segment after the change, allowing the same time for disputes to arrive
4.  Calculate the rate change. Small counts can swing it sharply
5.  Model the money: disputes you estimate were prevented, times the incremental cost each would have added (fees and handling, not the sale twice), minus what the change cost to build and run. That's a net benefit estimate. Divide by the spend only if you want an ROI, and say which spend you used

* * *

## Next Steps

**Fixing "unrecognized charge" disputes?**

1.  [Audit your descriptor](https://paymentsandrisk.com/docs/chargebacks/prevention/descriptors-and-comms/#descriptor-audit) - What customers see
2.  [Test on actual statements](https://paymentsandrisk.com/docs/chargebacks/prevention/descriptors-and-comms/#testing-your-descriptor) - Desktop and mobile
3.  [Add descriptor preview to emails](https://paymentsandrisk.com/docs/chargebacks/prevention/descriptors-and-comms/#confirmation-email-essentials) - Set expectations

**Improving subscription communication?**

1.  [Set up renewal reminders](https://paymentsandrisk.com/docs/chargebacks/prevention/descriptors-and-comms/#renewal-reminders) - Before the charge; 7-14 days is an example cadence, and the duties that bind you are in [recurring billing](https://paymentsandrisk.com/docs/compliance/subscriptions/recurring-billing/)
2.  [Send renewal confirmations](https://paymentsandrisk.com/docs/chargebacks/prevention/descriptors-and-comms/#renewal-confirmation) - After charging
3.  [Handle annual subscriptions](https://paymentsandrisk.com/docs/chargebacks/prevention/descriptors-and-comms/#annual-subscription-reminders) - Extra notice needed

**Measuring impact?**

1.  [Track key metrics](https://paymentsandrisk.com/docs/chargebacks/prevention/descriptors-and-comms/#analyst-layer-metrics-to-track) - Unrecognized charge %
2.  [Run pre/post comparison](https://paymentsandrisk.com/docs/chargebacks/prevention/descriptors-and-comms/#prepost-comparison) - Measure reduction
3.  [Check email deliverability](https://paymentsandrisk.com/docs/chargebacks/prevention/descriptors-and-comms/#email-deliverability) - Reach the inbox

* * *

## Related Pages

-   [Chargebacks](https://paymentsandrisk.com/docs/chargebacks/) - The chargebacks hub
-   [Chargeback Prevention](https://paymentsandrisk.com/docs/chargebacks/prevention/) - Prevention hierarchy
-   [Subscriptions and Recurring](https://paymentsandrisk.com/docs/payments/subscriptions-recurring/) - Recurring billing setup
-   [Winning Evidence](https://paymentsandrisk.com/docs/chargebacks/winning-evidence/) - What wins disputes
-   [Chargeback Ratio Crisis](https://paymentsandrisk.com/docs/chargebacks/zero-point-nine-panic/) - Emergency response
-   [Chargeback Alerts](https://paymentsandrisk.com/docs/chargebacks/prevention/alerts/) - Pre-dispute resolution
-   [Chargeback Lifecycle](https://paymentsandrisk.com/docs/chargebacks/lifecycle/) - Full dispute flow
-   [Friendly Fraud](https://paymentsandrisk.com/docs/fraud/types/friendly-fraud/) - First-party abuse
-   [Reason Codes](https://paymentsandrisk.com/docs/reference/reason-codes/) - Dispute categories
-   [Representment](https://paymentsandrisk.com/docs/chargebacks/representment/) - Fighting chargebacks
-   [Chargeback Metrics](https://paymentsandrisk.com/docs/chargebacks/metrics/) - Tracking your chargeback ratio
-   [Network Programs](https://paymentsandrisk.com/docs/chargebacks/reference/network-programs/) - VAMP, ECM thresholds
-   [Refund Policy](https://paymentsandrisk.com/docs/chargebacks/refund-policy/) - Policy design and customer-facing language
-   [Refund Strategy](https://paymentsandrisk.com/docs/chargebacks/refund-strategy/) - Refund or fight, in dollars
