#aj_connect-understanding

1 messages · Page 1 of 1 (latest)

desert pythonBOT
#

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

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

azure thicket
#

👋 taking a look

humble seal
#

thank you

azure thicket
azure thicket
#

To clarify, our channel is scoped for addressing developer questions relating to the use of our API and SDK's in an integrations code for a specific scenario more so than broad advice and integration patterning. I do apologize for the misplaced redirect from support. I'll see if we can have that point clarified with their team.

I think more generally, a good start would be reviewing our platform integration guide https://docs.stripe.com/connect/interactive-platform-guide, our broader Connect integration recommendations https://docs.stripe.com/connect/integration-recommendations, and onboarding docs https://docs.stripe.com/connect/onboarding in addition the the charges documentation I linked earlier to build a foundational understanding of connect so you can make decisions that align best with your goals. Support should also be able to help you make general pattern recommendations as well.

If you have questions as they relate to the use of our API or SDKs in your code for a specific situation or scenario our team is much better equiped to help with that so please keep us in mind as you move forward with the development of your integration. 🙂

desert pythonBOT