#dokosatchii_best-practices

1 messages ยท Page 1 of 1 (latest)

undone apexBOT
#

๐Ÿ‘‹ 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/1386832352231035031

๐Ÿ“ Have more to share? Add more details, code, screenshots, videos, etc. below.

regal tundra
#

hello! i see a list of docs and subjects, do you have any specific questions?

sage solar
#

We wanted to get an assessment if the way we are setting up the relatonship between customer -> CaterPlace <- Caterer is correct

Specifically, we seem to only be able to send a portion of a payment to a connected account if the product is in the main account, but that would require us to register every product in our main account.

#

We also can't see how to authorize and then capture payments in the UI/dashboard when creating payment links

#

This is a lot to put down in text, please let me know whatever context you need

regal tundra
#

are you doing direct charges or destination charges? for direct charges you create the charge directly on the connected account, and thus you would create the price in the connected account too. for destination charges the oppposite is true, you create all charges and products in your platform and then transfer funds to the connected accounts
https://docs.stripe.com/connect/payment-links

sage solar
#

Yes, we want to do destination charges

regal tundra
#

ok cool, then yes you would need to create all products in your platform account

sage solar
#

Cool, thats what we are doing

#

that said, there doesn't seem to be an easy way to filter the products

#

in the product catalog

#

ideally by some metadata value

regal tundra
#

ok cool - i can't remember off the top of my head if payment links support manual capture but let me double check

sage solar
#

It was confusing, it didn't initially

#

but I think the API updated

#

Docs are a bit conflicting on the destination charge page vs payment links pages

regal tundra
sage solar
#

Yes, so this can't be done manually in the dashboard as well?

regal tundra
#

i am less familiar with the dashboard, our team generally works directly with the APIs

sage solar
#

๐Ÿ˜ฅ

#

So not even sorting by name or price is possible?

regal tundra
#

i also don't see a manual capture option in the dashboard, but again i am not a dashboard expert

sage solar
#

Ok

#

I just wanted to make sure I wasn't missing something obvious

regal tundra
#

i think for these dashboard specific questions it might be best if i redirect you to our support team, they will probably know better than me

sage solar
#

Cool

#

Otherwise

#

Everything else look pretty solid?

#

I guess one more question

regal tundra
#

yep! what you've described sounds like the right approach for destination charges

sage solar
#

since all products need to be made in the main account

#

If we wanted to use Stripe dashboard as a way to organize the products per caterer, does it make sense to just create the product in both the main account and connected-account?

#

Is there a way to link them so changes are synced?

#

Would workflows be the solution here?

#

If we wanted to use Stripe dashboard as a way to organize the products per caterer, does it make sense to just create the product in both the main account and connected-account?
This is also so caterers can see their menu's in their dashboard too

regal tundra
#

you could probably do that via the API by setting up a webhook and listening for product.created, product.updated and product.deleted events then performing the corresponding action on the connected account
https://docs.stripe.com/api/events/types#event_types-product.created

and yeah, workflows might work too. our team is also not super familiar with workflows but theoretically they are just a UI that wraps our events system

sage solar
#

I like the first approach a lot better

#

ty

#

wait, so theoretically, couldn't we do the same for payment authorization? I'll leave with that question

regal tundra
#

i'm not totally sure what you mean? what would you do with payment authorization?

#

for payments the equivalent would be direct charges

sage solar
#

ahhh, payment created is a charge

#

Ok, nvm, TYVM

regal tundra
#

yep of course!

sage solar
#

Can I be forwarded to the "frontend/dashboard" team vs solution articles?

regal tundra
#

you can contact them by clicking the "contact support" button on the right side

#

you have to go through a little prompt for a bit but then you should be able to get to a person pretty quickly

sage solar
#

ty