#tim_api

1 messages · Page 1 of 1 (latest)

raven steppeBOT
#

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

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

rain remnant
#

Hi there

ripe garnet
#

Hi there

#
  • Is this the recommended approach, or should we consider other endpoints or best practices?
rain remnant
#

I recommend reviewing this in full to confirm whether Separate Charges & Transfers is right for you. There are different implications re: merchant of record, who's responsible for Stripe fees, refunds, and chargebacks

ripe garnet
#

Ahh okay perfect I will review it, thank you very much. Stripe makes it really easy with this extremely good API documentation but it does feel a bit overwhelming with this huge amount of cases that Stripe needs solutions for and to find the right fit. But as far as I understand it you would confirm that my approach seems right for my case and that I should just check the charge flow out and how to handle that? Sounds like good tips but I would just like to confirm that I am doing the right stuff from Stripe 😄

rain remnant
#

It generally makes sense but if Direct or Destination charges make more sense, you'd never actually make calls to /v1/transfers. Similarly, if you opt to use automatic payouts, you'd never make calls to /v1/payouts yourself

ripe garnet