#jd_best-practices

1 messages · Page 1 of 1 (latest)

lyric shoreBOT
#

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

📝 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.

faint ingot
#

Thank you in advance, and apologies for a lot of text, I just wanted to make sure as I am new to implementing payment gateways and stripe particularly

near pecan
#

👋 That sounds like the right set of conditions, but you might also want to check details_submitted https://docs.stripe.com/api/accounts/object#account_object-details_submitted
For connect readiness, I'd say listening to account.updated should be sufficient
eventually_due isn't necessarily a readiness blocker. These are future regulatory requirements that Stripe will promote to currently_due when collection is actually needed
And in relation to the OAuth callback, best to call it immediately

lyric shoreBOT