#skammerens-datter_api
1 messages ยท Page 1 of 1 (latest)
๐ Welcome to your new thread!
โฒ๏ธ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.
โฑ๏ธ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.
๐ This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1283048283253510310
๐ Have more to share? Add more details, code, screenshots, videos, etc. below.
hi there!
To clarify, the API call returns "Payout", whereas the actual bank statement is "Payout UNIQUE ID"
hello soma ๐
can you share an example Payout (po_xxx) with this issue?
actually, looking at some of Stripe's documentation on payment.statement_descriptor I infer it might be statement_descriptor_suffix I'm looking for to get the appropriate part?
yes, po_1Pob3eGdU9daq3qWCDartB7u
Thanks for that, taking a look
Thank you
the suffix that is seen on the bank statement is "Z6Z5X9", if that helps you
Ok, this is something we append due to special requirements for that bank that the descriptor is unique
okay, so programatically add a suffix to the payout itself, what should we be doing then? We'd like our customers (connected accounts) to have their payout tied together with the bank statement other than the date and amount
A far as I can tell, this random suffix is not exposed via the API. You can advise your users they may see that for this particular bank.
i understand the following, but the payout is typically bundled with several payments into a total bank transfer:
$stripe->paymentIntents->create([
'amount' => 1099,
'currency' => 'dkk',
'payment_method_types' => ['card'],
'statement_descriptor_suffix' => 'example descriptor',
]);
whereas this would be on the individual payment?
Yes if you're using automatic payouts this would be bundle with other payments
And the payment descriptor is unrelated to the payout descriptor
okay, so should we intercept the payout and change its descriptor, or what would be the way to ensure a unique id, that is retrievable via the api, is added to the payout?
We add that automatically, you don't need to do anything
I can share feedback that you'd like to see this exposed via the API to share with your users, but otherwise this is internal behaviour for payouts
I would like to know how to set a unique id to the statement descriptor for the payout (which is comprised of bundled payments) and how to retrieve it, so that our product can show the relevant payouts, their dates, status and descriptor that would then match the information on the bank account statement (now we have date and amount, but not descriptor)
most preferably Stripe should create a suffix automatically tied to the payout (which happened in po_1Pob3eGdU9daq3qWCDartB7u) as mentioned for all cases, but the suffix should be available on the payout object
is there some way to achieve this
You cannot manually set a unique descriptor for automatic payouts
You can set your platform or connected account default as shown here: https://docs.stripe.com/connect/payout-statement-descriptors
Which you've already done.
But this is used for all automatic payouts. The example you're example about is a special case.
If you want to set your own unique descriptors per payout, you can only do that with manual payouts
But is that your real goal, or are you trying to tie payouts to payments?
I'm going to share feedback that we should expose the random suffix in this case, or the complete descriptor used, i agree with you on that. It's just not available today.
Not sure how to explain it, my real goal is to have my customer know that a specific payout is this specific bank statement
Yep, so today you can use the date & amount from the payout object
I've shared feedback about the random suffix in this case, but its not available today
Okay, thank you