Docs
You are viewing:
Product Catalog 2.0
When reviewing transaction details in Chargebee, you may notice two parameters related to the statement descriptor:
statement_descriptorstatement_descriptor_suffixThis article explains how these parameters interact with Stripe, why merchants may see what looks like a duplicated descriptor, and how to configure them correctly to comply with Stripe's character limits.
"CHARGEBEE*"statement_descriptor_suffix.statement_descriptor."CHARGEBEE PRIME"Some merchants believe seeing “CHARGEBEE” twice in the descriptor means Chargebee is sending duplicate values. This is not the case.
"CHARGEBEE*" → from Stripe (set in the merchant's dashboard)."CHARGEBEE PRIME" (or a truncated version) → from Chargebee.Stripe enforces a 22-character limit for card transaction descriptors, including the asterisk * and spaces.
Example calculation:
"CHARGEBEE*" - 9 characters"CHARGEBEE PRIME" - 15 characters"CHARGEBEE* CHARGEBEE PRIME" - 24 charactersSince this exceeds the limit, Stripe truncates the suffix, causing "CHARGEBEE PRIME" to be cut off.
To ensure compliance with Stripe's limits and maintain brand clarity:
"PRIME") from Chargebee via statement_descriptor.CHARGEBEE* PRIMEInformation
Transaction details in Chargebee may show both statement_descriptor and statement_descriptor_suffix. This does not mean Chargebee is duplicating values—it reflects how Stripe processes descriptors based on transaction type.
Note:
Always ensure the suffix is short and brand-relevant. Overly long suffixes will be truncated by Stripe, potentially leading to unclear or misleading descriptors on customer statements.
Was this article helpful?