#onetruesunbro

1 messages · Page 1 of 1 (latest)

main roverBOT
#

Hello! We'll be with you shortly. Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.

stone flare
#

pi_3OAxeZD6uXFQvsKv1jx8yAVs

grizzled depot
#

Got it. Taking a look now

stone flare
#

thank you!

grizzled depot
#

What is the the customer seeing on their statement?

stone flare
#

this is a screenshot from the payment intent page

grizzled depot
#

That looks like what I would expect it to look like. What are you wanting it to look like?

stone flare
#

i need it to look like this:

#

CRSTCLB PleasantGroves

grizzled depot
stone flare
#

so here is the problem

#

i only need it to show CRSTCLB PleasantGroves for one connected account

#

all the other connected accounts should show the other way

#

basically we need a customizable prefix

grizzled depot
#

Ahhh, okay. That would only be possible if you were using on_behalf_of one your Payment Intents, which makes the Connect account the Merchant of Record (MOR). Since you're using Destination payments without on_behalf_of, the statement descriptor prefix uses your platform account's default statement descriptor prefix.

That's mentioned here: https://stripe.com/docs/connect/statement-descriptors#statement-descriptor-usage

Learn how statement descriptors work for charges with Connect.

stone flare
#

ahhh, i see I see

#

i was wondering about that, we do that in some other cases but not this case

#

so the MOR descriptor prefix will always be used?

grizzled depot
#

If it is set on the account, yes

stone flare
#

perfect, that clears things up for me

#

thank you!

#

that's what I needed to know

grizzled depot
#

Happy to help!