#forressveyn_best-practices

1 messages ¡ Page 1 of 1 (latest)

brisk cairnBOT
#

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

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

tidal waveBOT
drowsy timber
#

Which connected account type do you use? Standard, Express or Custom?

steel elbow
#

I was already working on API integration when the client decided to utilize stripe components and I was almost done with the invoicing API, connected accounts API and registering customers. The best-case scenario for us will be to

  • Connect accounts
  • Create customers
  • Utilise stripe components for the invoicing and account dashboard
  • Utilise stripe components for the customer dashboard (that's where I'm stuck because we have multiple customers for one user in the system)
#

Standart accounts

drowsy timber
#

If Standard connected account is used, the customers list should be visible in the Stripe Dashboard after logging into the connected account

#

Which "Stripe components" are you referring to here? Can you illustrate in an example?

steel elbow
#

This is the idea for the account side. But I'm out of ideas what we can use to do the same for the client side. I was thinking about setting up a customer portal but we have multiple customers for one client.

drowsy timber
steel elbow
#

Got it, thanks