Jasperste | Stripe Developers | Page 1

willow zephyrBOT Oct 18, 2022, 12:03 PM

#

echo barn Oct 18, 2022, 12:04 PM

#

Hi there!

#

Can you share a PaymentIntent ID with that issue?

round merlin Oct 18, 2022, 12:05 PM

#

Connect an account via Standard (Stripe Connect)
Set the statement descriptor via the dashboard within that account
Initiate a payment and PaymentIntentData.statement descriptor to a value

the value of 3 is used on the bank statement, the value of 2 isnt visible

#

pi_3Ln1UQR3LSvDToux0oijyEHd

echo barn Oct 18, 2022, 12:16 PM

#

This PaymentIntent comes for a Checkout Session created by the platform account on the connected account (a direct charge). Here's the creation request: https://dashboard.stripe.com/logs/req_4zMuM5MhZYRr6m

#

There you directly set a statement descriptor.

#

What statement descriptor where you expecting to see instead in the PaymentIntent?

round merlin Oct 18, 2022, 12:20 PM

#

The actual deduction on the bank statement didn't contain any info from the account profile of the connected account (in this case HET BAZIGE BROODJE). We were expecting the statement descriptor to take as 'name'. It now only showed the paymentIntent statement descriptor and a phone number (maybe due to Apple Pay (?))

#

The screenshot of the bank app shows 'Tegenrekening naam' which basically means account name where the money goes to. Which shows the paymentIntent statement descriptor

echo barn Oct 18, 2022, 12:32 PM

#

Thanks for the additional details. Give me a few minutes to look into this.

#

You set payment_intent_data.statement_descriptor when you created the Checkout Session. But I think you should have used payment_intent_data.statement_descriptor_suffix instead if you want the dashboard statement description to be used.
https://stripe.com/docs/api/checkout/sessions/create#create_checkout_session-payment_intent_data-statement_descriptor_suffix

round merlin Oct 18, 2022, 12:39 PM

#

I read in the docs that the statement is only visible for card payments https://stripe.com/docs/account/statement-descriptors

Statement descriptors

Learn how statement descriptors work.

#

Aha, but reading further is also mentions; For non-card charges, if you set a value only for statement_descriptor on a payment intent, Stripe uses it in place of the account statement descriptor (static descriptor).

#

So it's at least expected behaviour, it's quite a complex thing, especially since banks interprete it differently

echo barn Oct 18, 2022, 12:42 PM

#

That's correct.

round merlin Oct 18, 2022, 12:46 PM

#

Thanks. Is there a common way of doing this correctly and consistently that you know of?

We want at least the account statement descriptor on the bank descriptor, but preferably include some reference to the actual payment/order as well. We support several payment methods, so both card, but also for example iDeal

#

We use the Stripe checkout flow for payments (so no custom checkout forms). So we do not know the payment method in advance (otherwise we could adhere to what the docs state about card vs non-card descriptors)

patent nexus Oct 18, 2022, 1:17 PM

#

Hi 👋 I'm jumping in as my teammate needed to step away. I think the best approach here is for you to explicitly set the statement_descriptor for each Checkout Session you create. So rather than just adding information about the order to the statement_descriptor field, also add the desired reference to your Connected Account as well.

round merlin Oct 18, 2022, 2:10 PM

#

Thanks!
We can't set the dashboard stament descriptor for Connect Standard accounts. Would this mean that if we would like to set something relevant for each checkout session we would have to pull in the statement descriptor set by a connected account (or keep track via update events) and use that as part of the statement descriptor, each time?

#

For example for Ideal payments, if a connected account has set the static statement descriptor in the account and we would like to add a reference to the order to the statement descriptor, how would that work.
https://stripe.com/docs/connect/statement-descriptors seems like it only describes this for cart payments

Set statement descriptors with Connect

Learn how statement descriptors work for charges with Connect.

patent nexus Oct 18, 2022, 2:20 PM

#

Apologies for the delay, but yes.

round merlin Oct 18, 2022, 2:23 PM

#

Can you confirm if we would only have card payments we only have to set the dynamic part via statement_descriptor_suffix and it would have worked to achieve what we want?

patent nexus Oct 18, 2022, 2:27 PM

#

Yes, if your Connected Accounts are setting their statement descriptor prefix for their accounts (field is labeled "Shortened descriptor" in the dashboard), which is a separate field from the statement descriptor.

round merlin Oct 18, 2022, 2:30 PM

#

All right. Thanks. We will think out something to have this work consistenly and clear enough for Standard Connect Accounts with both card and non-card payments. Probably by keeping track of the descriptor edited in the dashboard and prepending that when setting statementDescriptor on the paymentIntent

#Jasperste