---
title: "Discussion on \"\"What is this charge on my card?\" Fix your statement descriptor before that email turns into a dispute.\" | Hashnode"
description: "Discussion on \"\"What is this charge on my card?\" Fix your statement descriptor before that email turns into a dispute.\". The bank statement line is the first thing a customer sees from you each month. Here's how to read yours, fix it in Stripe, and answer the email when it comes."
url: "https://hashnode.com/posts/what-is-this-charge-statement-descriptor/6af41625fbc27a1c8d4671b3"
---

[Feed](https://hashnode.com/feed) /

Discussion

# ["What is this charge on my card?" Fix your statement descriptor before that email turns into a dispute.](https://praneetbrar.hashnode.dev/what-is-this-charge-statement-descriptor?utm_source=hashnode&utm_medium=feed)

The bank statement line is the first thing a customer sees from you each month. Here's how to read yours, fix it in Stripe, and answer the email when it comes.

Nov 11 · 7 min read · praneetbrar.hashnode.dev  
Read the article

-   [#saas](https://hashnode.com/tag/saas)
-   [#stripe](https://hashnode.com/tag/stripe)
-   [#customer-support](https://hashnode.com/tag/customer-support)
-   [#indiehackers](https://hashnode.com/tag/indiehackers)
-   [#payments](https://hashnode.com/tag/payments)

## Written by

[Praneet Brar](https://hashnode.com/@praneetbrar)

@praneetbrar · Delhi, India

  
[View profile](https://hashnode.com/@praneetbrar)

Building cool things like launch platforms

## Responses 2

Markdown supported · ⌘↵ to post

[Paul Hartness](https://hashnode.com/@retryfix)

[6d ago](https://hashnode.com/posts/what-is-this-charge-statement-descriptor/6af41625fbc27a1c8d4671b3/comment/6af5837bb354e8da918b34cb)

The suffix maths in Step 2 was new to me. Stripe accepting a longer suffix without an error and then quietly cutting off the end is exactly the kind of thing you only learn from a confused customer. Step 4 matters for failed renewals too: the charge that finally goes through after a "your payment failed" email is the same subscription invoice, so it lands under the same Product or account descriptor. If that email uses the product name and the statement shows the holding company, a payment you just recovered can still come back as "what is this?", so I'd treat the dunning email as part of your Step 6.

[Praneet Brar](https://hashnode.com/@praneetbrar)

[6d ago](https://hashnode.com/posts/what-is-this-charge-statement-descriptor/6af41625fbc27a1c8d4671b3/comment/6af5837bb354e8da918b34cb#reply-6af5ab9a9e632a67d6ec083c)

Thanks Paul, treating the dunning email as part of Step 6 makes sense. A recovered payment that shows up under a different name than the email used is exactly how it turns into a "what is this?" ticket. When the retry succeeds, do you send a short confirmation that names the charge the way the statement will show it?
