FAQ

How to Set Up Dynamic Billing Descriptors on Stripe

How to set up dynamic billing descriptors on Stripe

Steven Petteruti
Steven Petteruti
Content Creator
Published November 17, 2026
5 min read
Updated November 17, 2026

Only merchants accepting Stripe payments via the Payment Intents API are able to modify their billing descriptor. Depending on your Stripe implementation, it may not be possible to set dynamic billing descriptors. Currently, merchants processing through Stripe Elements or Stripe Checkout are unable to modify their billing descriptor programmatically.

In order to set up a dynamic billing descriptor, you may use the statement_descriptor_suffix field. Note that this currently only applies to rebills/subsequent transactions on a subscription — it does not apply to a customer's first transaction.

const stripe = require('stripe')('sk_test_51NLHQAJ4S0qxxxxxxxxHc0dOYC1');

const paymentIntent = await stripe.paymentIntents.create({
  amount: 2000,
  currency: 'usd',
  automatic_payment_methods: {
    enabled: true,
  },
  statement_descriptor_suffix: 'XXXX' // random 4 digit alpha-numeric code
});

Since the suffix changes with every transaction, our matching algorithm can't match on your full descriptor string. Instead, you'll need to enroll the fixed prefix of your descriptor (the part before the dynamic suffix) as a "starts with" match at app.chargeblast.com/settings/descriptors. Prefixes are limited to 13 characters. If different products or processors use different prefixes, enroll each one separately as a descriptor variation — and if Stripe generates a shortened version of your descriptor, enroll that shortened version as a "starts with" match as well.

After enrolling your prefix, submit a support ticket to Chargeblast requesting that dynamic descriptor matching be enabled on your account. This step is required before our algorithm will match alerts against a variable suffix — it is not enabled automatically just by adding the suffix in Stripe.

This feature currently supports Stripe only. Only new alerts going forward will benefit once dynamic matching is enabled — pending alerts at the time of enrollment are not retroactively matched, and there's no fixed turnaround time for when matching takes effect.

Was this article helpful?

Help us improve our documentation