Set statement descriptors with Connect

Statement descriptors explain charges or payments on bank statements and include information that banks and card networks require to help customers understand their statements. Familiarize yourself with the requirements for statement descriptors.

Set the static component for a connected account

Statement descriptors can be static in one of two ways:

• The entire statement descriptor is static (static descriptor).
• The first half of the statement descriptor is static (static prefix) and the second half is dynamic.

The static component refers to either the static prefix or the static descriptor, and is set on the platform or connected account, depending on how your platform sets up charges.

For Standard accounts, the connected account sets the static components in the Dashboard.

For Express and Custom accounts, the platform account sets the static descriptor with the settings[payments][statement_descriptor] argument and the static prefix with the settings[card_payments][statement_descriptor_prefix] argument on the Account object.

curl https://api.stripe.com/v1/accounts \
  -u "
sk_test_4eC39HqLyjWDarjtT1zdp7dc
:" \
  -d type=custom \
  -d country=US \
  -d business_type=company \
  -d "capabilities[card_payments][requested]"=true \
  -d "capabilities[transfers][requested]"=true \
  -d "settings[payments][statement_descriptor]"="RUNNER CLUB"

Express and Custom accounts can’t set or update their own statement descriptors, so aren’t presented with a statement descriptor field in hosted onboarding.

The customer’s statement uses the connected account’s static component for the following charge types:

• Direct charges
• Destination charges with on_behalf_of
• Separate charges and transfers with on_behalf_of

Using the static component on connected accounts requires the card_payments capability.

The customer’s statement uses the platform account’s static component for the following charge types:

• Destination charges without on_behalf_of
• Separate charges and transfers without on_behalf_of

Any additional information that’s displayed on a customer’s statement is also provided by the account that provides the static component (for example, support address or support phone number). If the connected account hasn’t provided this information, on_behalf_of charges use the platform account’s information.

If you use a dynamic suffix on a charge that uses the connected account’s static descriptor, you can set a prefix to ensure the complete statement descriptor appears as intended.

curl https://api.stripe.com/v1/accounts \
  -u "
sk_test_4eC39HqLyjWDarjtT1zdp7dc
:" \
  -d type=custom \
  -d country=US \
  -d business_type=company \
  -d "capabilities[card_payments][requested]"=true \
  -d "capabilities[transfers][requested]"=true \
  -d "settings[card_payments][statement_descriptor_prefix]"=RUNCLUB

The prefix must contain between 2 and 10 characters, inclusive. The complete statement descriptor can contain up to 22 characters, including the * symbol and the space that concatenates the prefix and suffix.

Set the statement_descriptor and statement_descriptor_prefix for flexibility in setting statement descriptors on charges.

If the statement descriptor is set on card charges and no prefix is set, Stripe truncates the account statement descriptor as needed to set the prefix value.

Set a dynamic suffix for connected account charges

Dynamic suffixes are supported only for card charges by using the statement_descriptor_suffix parameter. You can read more about dynamic suffixes or see the concatenated statement descriptors (prefix* suffix) in the Dashboard.

curl https://api.stripe.com/v1/payment_intents \
  -u 
sk_test_4eC39HqLyjWDarjtT1zdp7dc
: \
  -d "payment_method_types[]"=card \
  -d amount=1000 \
  -d currency="usd" \
  -d statement_descriptor_suffix="Custom suffix" \
  -H "Stripe-Account: {{CONNECTED_STRIPE_ACCOUNT_ID}}"

Set Japanese statement descriptors

We recommend setting the static components of kanji and kana statement descriptors for Japanese connected accounts.

You can set all descriptors and their corresponding prefixes when creating a Japanese Custom connected account as follows:

curl https://api.stripe.com/v1/accounts \
  -u "
sk_test_4eC39HqLyjWDarjtT1zdp7dc
:" \
  -d type=custom \
  -d country=JP \
  -d business_type=company \
  -d "capabilities[card_payments][requested]"=true \
  -d "capabilities[transfers][requested]"=true \
  -d "settings[card_payments][statement_descriptor_prefix]"="example prefix" \
  -d "settings[card_payments][statement_descriptor_prefix_kanji]"="漢字プリフィックス" \
  -d "settings[card_payments][statement_descriptor_prefix_kana]"="カナプリフィックス" \
  -d "settings[payments][statement_descriptor]"="example descriptor" \
  -d "settings[payments][statement_descriptor_kanji]"="漢字明細" \
  -d "settings[payments][statement_descriptor_kana]"="カナメイサイ"

You can set dynamic kanji and kana suffixes when creating card charges with payment_method_options[card][statement_descriptor_suffix_kanji] and payment_method_options[card][statement_descriptor_suffix_kana].

curl https://api.stripe.com/v1/payment_intents \
  -u "
sk_test_4eC39HqLyjWDarjtT1zdp7dc
:" \
  -d amount=1000 \
  -d currency=jpy \
  -d "payment_method_types[]"=card \
  -d statement_descriptor_suffix="example descriptor" \
  -d "payment_method_options[card][statement_descriptor_suffix_kanji]"="漢字サフィックス" \
  -d "payment_method_options[card][statement_descriptor_suffix_kana]"="カナサフィックス"

See Japanese statement descriptors for more details.