#knuppi_api

1 messages · Page 1 of 1 (latest)

hexed dawnBOT
#

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

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

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.

umbral robin
#

This conversation continues where I left off yesterday

left pierBOT
umbral robin
#

Hi Toby

#

Don't know if you remember our conversation from yesterday

idle cloud
#

I'm not sure what you're referring to by "payment descriptor" here

umbral robin
#

I was planning to update the payment_descriptor day-by-day, but received this (undocumented) error from the API:

I1016 13:55:42 _util <stripe:128> message='Request to Stripe api' method=post url=https://api.stripe.com/v1/accounts/acct_1MizxUQ1KtFWbldN
I1016 13:55:44 _util <stripe:128> message='Stripe API response' path=https://api.stripe.com/v1/accounts/acct_1MizxUQ1KtFWbldN response_code=400
I1016 13:55:44 _util <stripe:128> error_code=None error_message='You cannot change `settings[payouts][statement_descriptor]` via API once an account has been activated. Please contact us via https://support.stripe.com/contact if you need to change the information associated with this account.' error_param=settings[payouts][statement_descriptor] error_type=invalid_request_error message='Stripe API error received'
idle cloud
#

Ah, gotcha.

#

Oh yeah, you're using Standard Connected Accounts, forgot about that.

umbral robin
#

We were trying to not use manual payments just yet, because it will demand more work - not only from the platform, but perhaps from the client (the connected account) as well

idle cloud
#

I'm afraid I gave you bad advice yesterday because I forgot you were using Standard Connected Accounts, which control a lot of this on their own rather than letting you exclusively control it as the platform.

umbral robin
#

OK,
With this new knowledge, what would your advice be instead?

idle cloud
#

Depends on where you're at in your implementation. Are you already live and trying to figure out how to adapt your flow to accomplish this? Or are you still in the initial planning/building phase?

umbral robin
#

We're already live with existing paying customers

idle cloud
#

I don't think there is a good way to accomplish this then.

umbral robin
#

So creating manual payouts with a custom payment_descriptor is also out of the question?

#

If so, could you please create a feature request(?), telling Stripe to expose the payment_descriptor with the random characters as well?

idle cloud
#

I think so. Because I think the Connected Accounts would A) have the ability to switch their payout schedule on their own and B) create their own payouts if they switch to manual payouts.

idle cloud
umbral robin
#

Please check 👌🏾

idle cloud
#

Ah, glad I checked, I filed different feedback and forgot to go back to +1 this one. Handling that now.

umbral robin
#

Another (related) question:
Is it possible to see/know the exact stripe fee in each transaction (which is included in a Payout)?

idle cloud
#

Yup, each Balance Transaction object contains fee and fee_details fields for understanding that:
https://docs.stripe.com/api/balance_transactions/object#balance_transaction_object-fee
and when using Automatic Payouts you can list all Balance Transactions included in a Payout:
https://docs.stripe.com/api/balance_transactions/list#balance_transaction_list-payout

One point of clarification though, can you remind me whether you're using Direct Charges or Destination Charges?

List all balance transactions | Stripe API Reference

Complete reference documentation for the Stripe API. Includes code snippets and examples for our Python, Java, PHP, Node.js, Go, Ruby, and .NET libraries.

The Balance Transaction object | Stripe API Reference

Complete reference documentation for the Stripe API. Includes code snippets and examples for our Python, Java, PHP, Node.js, Go, Ruby, and .NET libraries.

umbral robin
#

Hmm, don't remember which type of charge. Where can I read about those again?

idle cloud
#

Just wanted to make sure because with Destination Charges the fees are on a different account and getting to them is a bit more involved. What I shared should work for your flow, but let me know if it doesn't give you the details you're looking for.

umbral robin
#

I'm pretty sure we're using Direct Charges with application fee

#

Do you know if we can fake payout.paid webhooks through the Stripe CLI?

idle cloud
#

I know that you can't, and just ran stripe trigger payout.paid to confirm as much.

umbral robin
#

I think we'll try to collect the payment fees for each transaction and do some reverse work in trying to match the payout with the transactions in our systems

idle cloud