How to Fix a Stripe Connect Statement Descriptor Mismatch After a Rebrand

· 2 min read

A rebrand can change what customers recognize without changing the legal entity that receives payments. In Stripe Connect, that distinction matters when you change what customers see on their card or bank statements. Stripe checks whether the statement descriptor is close to the business profile name, the business URL, or the company or individual name. It also checks whether a configured prefix is sufficiently similar to the descriptor or these business identifiers.

Compare the descriptor with the account profile

Start with the connected account's actual descriptor and prefix. Compare them with the profile name customers encounter when purchasing. Read the legal-entity name and business URL as separate fields. If one field still shows the old brand, reconcile the profile first so that the descriptor is supported by a source the customer can recognize. A change made to the descriptor alone can leave an otherwise inconsistent identity record in place.

Error category What it refers to What to check
Business mismatch The descriptor does not resemble the business Business profile, legal name and website
Prefix mismatch The prefix lacks a reasonable association Prefix compared with the descriptor and business identifiers
Denylisted text Generic or well-known business names Make the text specific to the business that actually charged the customer
Length The descriptor text is too short The reported requirement and the planned customer-visible text

Work through a merchant's rebrand

Suppose the website has changed from one shop name to another and the company registration is unchanged. The merchant edits the main descriptor but keeps a prefix from the previous brand. Compare that prefix with the updated profile and descriptor. If it no longer corresponds to the business the customer interacted with, select a supported prefix. Keep corporate identity evidence separate from customer-facing text.

Verify the result on the right account

Review the latest connected-account requirements after saving the change. If the reason still points to a descriptor field, confirm that you updated the intended account and that the prefix and main descriptor are consistent. Preserve a record of which brand name and URL supported the update so the team can explain the statement text if customers ask about an unfamiliar charge.

Official sources

  1. Handle verification with the API
  2. Identity verification for connected accounts