#aivanopoulos-Payout
elder willow
Hi there! Could you elaborate a bit more on the context? Which Payout type are you using ? (Auto/Manual) and is that Trace ID a value from your system?
scenic drum
Pretty sure we use manual auto, and no, the Trace ID is something from Stripe? When looking at the details of a payout within a connect account, it looks like this:
We can get the payout ID just fine, but that trace ID isn't something that's available, and I would love for it to be. Because it also seems that our customers can't take the trace ID from their bank statement and search for it in the Stripe dash either?
And I guess to round it all out, that Payout trace ID value is what appears in the description in the customers bank statement... so the ideal flow for us would be for them to get that id from their statement, search their payouts in our app using that trace ID, get the payout associated with it, and they can see all the related charges from there and do their reconciliation
If they could search the stripe dash using that trace ID, I think that would at least alleviate some issues as well.
elder willow
I see/can somewhat get your point. But let me ask some quick questions so I can better understand the scenario
What type is your Connected account? (express/custom/standard)? It sounds like custom to me
And where in the detail of payout you are seeing that screenshot? By your platform Dashboard?
And also would be easier if you can give me the connected account id, so I can quick check by myself
scenic drum
For sure!
- So yeah I would assume these might fall under custom... we use the original oauth way of onboarding everyone, so they're accounts that get made separately that they then link, we're looking at the moment to move to the standard / express stuff.
- So this appears on the payout details screen. That value is available when looking at our own payouts, but, we can see it if viewing a connected account and looking at their payouts as well.
- Yeah so the example I'm kinda poking at right now is acct_1KWyOcE7sICag24x
elder willow
Ok so they are Standard and your platform is acct_18c3RZClStGc5XwO, correct?
Looking
elder willow
Oh I see it's this one
scenic drum
Yeah that's the one
elder willow
So I did a research and I think, for Standard Accounts that are created before you connected to them via Oauth, you can't include a custom string for each of the Payout. That thing is called "dynamic descriptor" But I (any my team here) are not expert on this area, so I suggest contacting Support and they might have a concrete answer
As far as I can see, this Trace ID is not something to included in the statement descriptor in Payout
scenic drum
Ah interesting... that's good to know. So if we moved over to the new account link way of onboarding folks (my understanding is that the stripe account in that case is somewhat specific to our platform), we'd be able to specify something custom to flow through to the statement? That's cool
Is statement_descriptor_suffix something we could potentially use per-charge in the mean time?
Ah wait no that'd just be on the charge itself to the end user, ignore me 🙂
elder willow
Yeah that one is for customer
for a new standard account created via link, you can specify the default statement descriptor via https://stripe.com/docs/api/accounts/create#create_account-settings-payouts-statement_descriptor (vs. already existed account connected via OAuth you can't even set this). But again, you still can't make it dynamic as far as I know
In the end your feedback was correct. We supports dynamic descriptor on Charges for customer, but we really don't support dynamic descriptor for Payout. Sorry about all the back and forth. I was trying to understand the ask correctly
scenic drum
No worries at all... is there any plans to allow a dynamic descriptor for payouts?
That isn't necessarily important, I'd mostly just want to know the one Stripe is using already, that'd be enough, really
elder willow
I don't have a timeline to share. But will record your feedback