knuppi_payout-descriptors

[quartz remnant]

👋 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/1295759291093094411

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

[wind rain]

Hi Toby

[fair tartan]

Hi there 👋 the doc you linked to explains this. Do you have a question about something you're seeing in that doc and/or in practice?

[wind rain]

The problem we're facing is that we have a client (connected account) which is receiving payouts from you every day

The problem is, if you follow the related request ID, that every data.object.description has the same value

is there a way to create a unique value, for each payout? the client needs to be able to differentiate the contents of each payout

[fair tartan]

Are you using manual payouts?

[wind rain]

automatic daily payouts at the moment

[fair tartan]

Then the only thing I can think of that might work there, is to update the Account's settings.payout.statement_descriptor field every day to the value you want to use that day:
https://docs.stripe.com/api/accounts/update#update_account-settings-payouts-statement_descriptor

[wind rain]

1. multiple end-user makes purchases through our platform to the connected account
2. we save all receipts in our platform with the payment_id ("pi_xxx")
3. within a few days, the payout is triggered from Stripe
4. we read the webhook and collect information of which payment_intents are inside the payout
5. we tag the receipts in our platform with which payout they belong to

problem is; when the client checks their bank account, they see payment descriptors such as this:

[quartz remnant]

knuppi_payout-descriptors

[wind rain]

Please see the line in the PDF which says ("CONCEPTO")

[fair tartan]

Removing your file as it appears to be a real screenshot from your users bank, and this is a public forum.

Is that the Payout's statement descriptor?

[wind rain]

Yes, where it says "STRIPE H0W2U1"

[fair tartan]

There isn't a way to have those descriptors change automatically every payout, you would need to implement that logic. But I'll file feedback with our teams that this is something you'd be interested in seeing provided in the future.

[wind rain]

If we take this approach, will this update what's being sent to the bank as the "CONCEPTO"?

[fair tartan]

I'm not sure. I don't know how exactly the bank is building what they show to their customers. Do you have an example Payout object that we can take a closer look at to see if we can spot what statement descriptor was used?

[wind rain]

This is the payout object I think: https://dashboard.stripe.com/acct_1NvFsKQ6t7QQwXAB/payouts/po_1Q7RqJQ6t7QQwXABypIb6VoI

I haven't been able to find a public API property where I've found the bank statement

This is an older bank statement from the same client

As you can see, the "CONCEPTO" is changing slightly

An alternative solution could be; is it possible to initiate a Payout for every payment the connected account receives? (I assume not)

[fair tartan]

Yeah, you could do that, if you switch to manual payouts.

Then you can also specify the statement descriptor for every Payout you create

[wind rain]

Would we be able to trigger multiple payouts per day?

[fair tartan]

As far as I know

I'd suggest testing in testmode to confirm

[wind rain]

We'll consider this solution

But wrt my original question, have you found an answer?

[fair tartan]

I do believe that's the field that would change. Can you confirm whether you settings.payout.statement_descriptor on the Account is set to anything? And if not confirm whether you set a default statement descriptor at your Platform level?

Because it looks like we're using STRIPE as the statement descriptor as described in the doc you linked for behavior for automatic payouts, plus some random value that I wasn't aware of.

[wind rain]

This is what we've set on the platform level: https://dashboard.stripe.com/settings/connect/payouts/statement-descriptor
PRE:MIND payout

[wind rain]

Are you able to talk to lvl2 support on whether this randomized value can be defined?

[fair tartan]

Gotcha, but that doesn't apply because you're using Standard accounts I see.

No, for more details on how these Payout descriptors behave I'd suggest reaching out to our Support team:
https://support.stripe.com/?contact=true
Since they're not controlled by the code in your integration it isn't something we're too familiar with here in this forum.

[wind rain]

This is what we have on the account:`

    "payouts": {
      "debit_negative_balances": true,
      "schedule": {
        "delay_days": 3,
        "interval": "daily"
      },
      "statement_descriptor": null
    },

[fair tartan]

Gotcha, so statement_descriptor isn't set.

[wind rain]

Thus, we have two options:

1. (perhaps easiest), we update the statement_descriptor every day with a known value
2. (perhaps more work), we enable manual payout, create a cronjob to run those, and then we set the statement_descriptor for each Payout

Do you agree with my assesment?

[fair tartan]

Yup

[wind rain]

I see, thank you for your help! We will work with these solutions

[fair tartan]

Any time!

[wind rain]

Is this how we create Payouts? https://docs.stripe.com/api/payouts/object

And how do we set to manual payouts?

[fair tartan]

Yup. Our guide for switching to and using manual payouts can be found here:
https://docs.stripe.com/connect/manual-payouts