Loading saved preview data.

HomeBriefingAccounts

Stripe Statement Descriptors, Receipts and What the Cardholder Sees

How Stripe statement descriptors, receipts and checkout names cause unrecognised-charge disputes, and why they must name the real seller.

Updated 7 November 2026 · 8 min read · Accounts

On this page

Cardholders do not read your about page when a line appears on their statement. They read five to twenty-two characters, the amount, and the date. If those characters are a holding company they have never heard of, they tap dispute. The dispute reason is fraudulent or unrecognised. You may have shipped the goods. You still lose, because the customer is telling the truth about what they saw.

Four names that have to agree

  • The checkout. The name next to the button, before they pay, is the name they will look for later.
  • The receipt. The email or page after payment should repeat it, with a support address that answers.
  • The statement descriptor, including the shortened form some banks show. Read it in capital letters. Banks often display it that way. A clever mixed-case word becomes noise.
  • The support path. The phone or URL a statement can carry should reach a person who knows the charge. An empty voicemail is how a query becomes a dispute.

The legal entity can be quieter, in the footer and the terms, and still must be true. The brand can be prominent, and still must be a brand the account is allowed to charge under. What you cannot do is show one seller in the advertisement and a different, unrelated seller on the statement, then act surprised by the fraud reports.

Changing a descriptor during trouble

After a wave of disputes, the temptation is to rotate the descriptor so the next campaign “looks new”. Customers who were billed last month still see the old one. New customers see a name that matches neither your site nor your company. Radar and the dispute book do not forget the account underneath. A new descriptor is a labelling change. It is not a new merchant, and it is not a response to a freeze.

If you rebrand for a real reason, change the site, the receipt, the descriptor and the terms together, and keep answering the old support path. Tell Stripe what the brand is if the account is under review. A review is a bad week to look as if you are trying not to be recognised.

Partnerships live or die on this detail

In any arrangement where two businesses touch one charge, write down what the customer sees before anyone writes down a percentage. Who is named at checkout? Who is named on the receipt? Who is named on the statement? Who answers the phone? If the answers are “we’ll see what converts”, you are planning the next unrecognised-charge spike on purpose.

RevRouters treats that customer-facing identity as part of the assessment, not as creative. An introduction does not include a descriptor you can borrow. If the only commercial logic of a partnership is that one firm’s familiar Stripe name will front another firm’s unknown product, the logic is the problem.

Test with a real card

Before you scale a checkout, pay a small amount with a card you control and read the statement line on the bank’s app, not in Stripe’s preview. Banks truncate. The preview is not the artefact the cardholder disputes.

What this briefing is not

It is not legal, tax or card-scheme advice, and it is not Stripe’s policy. Your notice and Stripe’s terms control the account. RevRouters does not process payments, does not lift a freeze, and does not offer another business’s account as a remedy.

Questions on this note

What is a statement descriptor?

The short text that appears on the cardholder’s bank or card statement beside the charge. It is one of the main ways a customer decides whether they recognise the payment. If they do not, they dispute it. Stripe lets the account set it within network rules. It is not a place for a joke, a hidden brand, or another company’s name.

Can the descriptor show my brand if the Stripe account is a partner’s?

Only if that is actually permitted and the customer is not being misled about who they paid. A descriptor that hides the account holder, or invents a seller the account does not belong to, manufactures unrecognised charges and a terms problem at the same time.

We have a high “unrecognised” dispute rate. Where do we look first?

The descriptor, the name on the checkout button, the receipt email, and the domain they visited. Those four should be the same business the customer remembers. Then look at delayed descriptors from a previous brand you no longer trade as.