waqas-safdar_connect-integration-architecture

[solid apex]

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

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

• waqas-safdar_api, 2 hours ago, 6 messages

[silent tiger]

Hi there 👋 I see you describing your situation, but I don't see a question in your post, what can I help with?

[twin raptor]

Hi, @silent tiger
We are developing a project that requires onboarding vendors using Stripe Connect (Express Accounts). The main challenge is determining the best approach to implement the integration while ensuring it is:

Scalable: To handle a growing number of vendors and transactions.
Secure: To protect sensitive data like API keys and vendor tokens.
Maintainable: For easy updates and future enhancements.
Aligned with Stripe Best Practices: For managing API interactions, logs, and webhooks.
Our project uses:

Laravel Backend API: Handles core logic like vendor operations (products, bookings, etc.).
Vue 3 Dashboard with Quasar: Allows vendors to manage their accounts, products, payments, etc.
We are unsure whether the Stripe Connect integration should primarily reside in the Laravel backend or the Vue.js dashboard. Each approach has implications for security, scalability, and long-term maintainability.

@silent tiger
We just want to get help in the selection of the approach to choose the tech stack for the Integration of Stripe Connect for Express Accounts.
Key Questions:

1. Should the Stripe Connect Express Integration be implemented at the Laravel API level, or should it be at the Dashboard level by creating a dedicated backend folder for Stripe operations?
2. How should the architecture be designed to maintain scalability and extensibility in the future?

[silent tiger]

I don't know, I'm not sure what each of those pieces of your stack are providing. There are also many pieces to a Connect integration, such as onboarding, processing payments, (optionally) dashboard functionality (maybe not relevant if you're going to use the Express dashboard), and others depending on the breadth of your integration.

We can help answer questions about the Stripe API, but you know your stack and the products you've selected to build it better than we do.

[twin raptor]

@silent tiger & @west sun
Basically, we've to onboard the vendors/businesses to create their stripe accounts under our dashboard's main Stripe Connect Dashboard. All the vendors/businesses will manage their payments and transactions via our developed Dashboard.
Our project's backend API is developed in Laravel and the dashboard is developed in Vue.js with the Quasar framework.
Now we're confused about which level we should integrate the Stripe Connect API to onboard the new vendors on our developed dashboard.
All the integration should be at the Laravel API level.
All the integration should be developed at the Dashboard Vue.js Quasar level by creating a separate directory for stripe-integration.

[west sun]

HI 👋

I"m not sure what you mean by "what level" you should integrate the Stripe Connect API. Some requests will require you use your Secret key which should always be at the level of server-side code where you control the runtime environment. Other components can be done on the front-end using products like Connect embedded components.

But how that is organized is up to you