New in Chargebee: Explore Reveal and understand your payment performance end-to-end.Try Now
Docschargebee docs
HomeBillingPaymentsRevRecGrowthReveal
Support

Product Updates

  • Release Notes

Payment Methods

  • Payment Methods Overview
  • Cards
  • Direct Debit
  • Bank Based Payments
  • Wallets
  • Vouchers
  • Articles and FAQ

Payment Gateways and Configuration

  • Payment Gateways Overview
  • Chargebee Test Gateway
  • Stripe
  • PayPal Payment Services
  • Chargebee Pay
  • Adyen
  • Authorize.net
  • Bambora (formerly Beanstream)
  • Bank of America
  • BluePay
  • BlueSnap
  • Braintree
  • Checkout.com
  • CyberSource
  • dLocal
  • EBANX
  • Ecentric
  • Elavon
  • E-xact Direct Integration
  • eWay Rapid
  • Global Payments
  • GoCardless
  • J.P. Morgan Mobility Payment Solutions
  • Metrics Global
  • Mollie
  • Moneris
  • Network Merchants Incorporated (NMI)
  • Nuvei
  • Orbital (Chase Paymentech)
  • Pay.com
  • Paymill
  • Paystack
  • Pin Payments
  • QuickBooks Payments
  • Razorpay
  • Sage Pay
  • Solidgate
  • Tempus
  • Twikey
  • Windcave
  • Worldline Online Payments(formerly Ingenico)
  • Worldpay
  • Articles and FAQ

Level 2/3 Data Support

  • Level 2/3 Data Support

Advanced Routing

  • Advanced Routing

Dunning

  • Dunning
  • Articles and FAQ

Offline Checkout

  • Offline Checkout
  • Articles and FAQ

Transaction Sync & Invoice Mapping

  • Transaction Sync and Invoice Mapping

Fraud Management

  • Fraud Management

Error Handling

  • Errors with Root Cause and Troubleshooting

Payment Lifecycle Logs

  • Payment Intents
  • Transactions
  • Gateway Activity Logs
  • Gateway Webhook Logs
  • Articles and FAQ

Others

  • Reach (Merchant of Record)
  • Payment Verification
  • Bulk Deletion of Payment Methods
  • Custom Payment Methods
  • Payment Initiator Parameter
  • PSD2 and Strong Customer Authentication
  • RBI e-Mandate
  • RBI Tokenization Regulations
  • Chargeback Management
  • Transaction Descriptors
  • Payment Preferences
  • Visa Trial Rules
  • Mastercard Trial Rules
  • Co-badged Card Compliance
  • Articles and FAQ
  1. Payments
  3. Others
  5. Articles and FAQ
  6. Transaction Descriptors
  1. Payments
  3. Others
  5. Articles and FAQ
  6. Transaction Descriptors

Understanding Statement Descriptors in Stripe via Chargebee

Problem Statement

This article helps you understand understanding statement descriptors in stripe via chargebee.

Solution

When reviewing transaction details in Chargebee, you may notice two parameters related to the statement descriptor:

  • statement_descriptor
  • statement_descriptor_suffix

This 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.

How Statement Descriptors Work

  1. Stripe Prefix
  • The part before the asterisk (*) is set directly in the merchant's Stripe dashboard.
  • Example: "CHARGEBEE*"
  1. Chargebee-Sent Descriptor
  • The part after the asterisk (*) comes from Chargebee's configuration:
    • For card transactions → Stripe uses statement_descriptor_suffix.
    • For non-card transactions → Stripe uses statement_descriptor.
  • Example: "CHARGEBEE PRIME"

Common Misunderstanding

Some merchants believe seeing “CHARGEBEE” twice in the descriptor means Chargebee is sending duplicate values. This is not the case.

  • Prefix: "CHARGEBEE*" → from Stripe (set in the merchant's dashboard).
  • Suffix: "CHARGEBEE PRIME" (or a truncated version) → from Chargebee.

Character Limit Consideration

Stripe enforces a 22-character limit for card transaction descriptors, including the asterisk * and spaces.

Example calculation:

  • Prefix: "CHARGEBEE*" - 9 characters
  • Suffix: "CHARGEBEE PRIME" - 15 characters
  • Combined: "CHARGEBEE* CHARGEBEE PRIME" - 24 characters

Since this exceeds the limit, Stripe truncates the suffix, causing "CHARGEBEE PRIME" to be cut off.

Recommended Approach

To ensure compliance with Stripe's limits and maintain brand clarity:

  1. Send only the meaningful suffix (e.g., "PRIME") from Chargebee via statement_descriptor.
  2. The final output will be: CHARGEBEE* PRIME
  • Length: 16 characters
  • Well within Stripe's 22-character limit
  • Preserves brand visibility on the customer's card statement

Information

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.

Related Articles

Can I use multiple currencies with my Chargebee account?
Does Chargebee automatically update an expired card?
How can customers add or update their payment information in Chargebee?

Was this article helpful?