#nate_express-invoicing

1 messages ¡ Page 1 of 1 (latest)

proud sandBOT
#

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

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

quartz thunderBOT
raw ruin
#

@devout rain it's going to depend a lot on your integration overall such as the type of connected accounts you're using and the flow of funds that goes with it.

devout rain
#

So when a professional signs up to enable card payments I use the gateway that creates an Express account for the professional

#

and then when creating an invoice I pass "stripe_account" => and the ID of the express account (acct_12345)

raw ruin
#

gotcha! so yeah that's all incorrect!

#

That means that all the objects (Customer, PaymentIntent, Invoice, etc.) should all live in your own platform account

devout rain
#

will this still allow all our pros to have individual dashboard access, they need to see all their invoices/payments etc.

#

our ultimate aim is to allow our pro's to see and manage their own invoices/payments, we just want to provide the mechanism to view in app e.g. statement page, create invoice/payment links

raw ruin
#

Express accounts don't see Invoices or PaymentLinks and such so that's irrelevant

devout rain
#

what other account type is best then, we don't want to be handling all of the auth/verification for a user, we used express at they have the stripe gateway for registration

raw ruin
#

Express is totally fine, we hanle the collection of PII for you. There's no reason to not use Express right now with wht you described. Just you're misunderstanding what Express users can see in their Dashboard that's all

devout rain
#

so if I continue to use express, invoices I create with a destination charge which would be the pro's account ID, and the customer e.g. the pro's end client wouldn't be specific to an express account

raw ruin
#

correct

devout rain
#

so what would the pro then have access to data wise?

#

I need to provide them some sort of dashboard so they can see what payments they have received and from who, I have already done payout request functionality

raw ruin
#

nate_express-invoicing

devout rain
#

thank you for that, i will re-implement with destination charges and run some tests