#Akram - Sub Statement Descriptor

1 messages · Page 1 of 1 (latest)

cunning tangle
#

No the Subscription API does not support adding Statement descriptors. I'm guessing you would want this to propagate down to the Invoices and Payment Intents so the Bank could display it.

cyan basin
#

Correct

cunning tangle
cyan basin
#

is it the same for payment intents? if I update it (as soon as get created), it will change on the the bank statement when posted?

#

Or maybe add it to the checkout session?

cunning tangle
#

Are you using the Checkout Session to collect payment method information?

cyan basin
#

Yes

cunning tangle
#

Checkout session does not accept a Statement Descriptor parameter

cyan basin
#

if subscription, does updating the invoice will it update on the bank end when posted?

cunning tangle
#

It will update the information we provide to the bank. But not all banks are consistent in how they choose to render this information. You can read more detailed information about how we use statement descriptors here: https://stripe.com/docs/statement-descriptors

cyan basin
#

Thank you so much for you help @cunning tangle

cunning tangle
#

Sure thing. You can set a statement descriptor on your whole Account that will get used whenever you do not specify anything on individual Objects. That might be more what you are looking for.

cyan basin
#

nope it should be dynamic as I wanted to appear with the connected account name but for limits from Stripe I have to collect the funds and then do transfers

cunning tangle
#

Okay, that makes perfect sense.

#

I would try some test subscription/invoice creation and updates. Take a close look at the calculated_statement_descriptor property in your developer logs.

cyan basin
#

Oh that's great to know, thank you for the tip