Changes statement descriptor behaviors for card payments created with ChargesBreaking changes
What’s new
Changes statement descriptor behaviors for card payments created through /v1/charges. To learn more, see our guide on statement descriptors.
- Instead of using the platform’s statement descriptor, charges created with
on_
orbehalf_ of destination
now use the descriptor of the connected account. - The full statement descriptor for a card payment is no longer provided at charge creation. Dynamic descriptors provided at charge time are now prefixed by the descriptor prefix set in the dashboard or through the new
settings[card_
parameter in the Accounts API.payments][statement_ descriptor_ prefix] - If an account has no
statement_
set, the account’s business or legal name is used as the statement descriptor.descriptor - Statement descriptors can no longer contain
*
,, and
"`.
Impact
This change alters how statement descriptors are handled for card payments created through the Charges API, providing more accurate branding for connected accounts and standardize descriptor formatting.