#zac-b_best-practices
thin siloBOT
đ 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/1351235694189740237
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
quick sequoia
I would recommend using a saved Payment Method instead of some sort of token. What Checkout Screen are you referring to here?
Also, this would require using the same Customer object for all these transactions, since the Payment Method would need to be saved to a Customer in order to be re-usable.
tawny jay
Ah so in order for this to work, we need to have the same customer object.
So I can't have 5 different emails (customers) who can use either a personal card, or the same stored company. Similar to this
quick sequoia
That is a mobile sheet, which has it's own restrictions too.
And correct, you cannot have a "company card" that is shared across multiple customers, unless you create and save those same card details for each Customer
tawny jay
Can we automate that creation and saving to specific users when we sign them up or invite them?
quick sequoia
They would need to provide the card details
But let's take a step back. How is your integration organized? Is this a single Stripe Account?
tawny jay
Thanks Snufkin, yes, one stripe account. We use connected accounts and are running a marketplace but I do not think that is the solution or relevance.
We will have some customers that sign up a business account, and some as regular customers. We have both app and web deployed front end UIs, custom API builds for the most part.
Ultimatly, what we are trying to achieve is a way to charge a top level account with usage from invited staff. It can be instant or we could do monthly billing if that is simplere or makes more sense. Can we do that somehow using stripe?
quick sequoia
Okay so, for the Payment Sheet (the mobile photo above), the saved payment method is also local to that device. So you could not present the same saved PM on a different phone.
I think you can do it but it would require creating a Customer that acts as the top level account and you would need to track the invited staff somehow in your integration
tawny jay
That makes some sort of sense. Thank you.
Could we use payment_intents to store and charge these at the end of the month in bulk. It feels like a pretty solid no, each transaction has one charge. But I thought I would ask. We are also right at the end of our build so looking for low effort workarounds, even if they are manual at first.
quick sequoia
If you are not processing a charge when you first get the payment method details, I recommend using Setup Intents to save the Payment Method and attach to a customer.
thin siloBOT
quick sequoia
You could keep your own running totals of what you are owed and process it as a single Payment Intent but that puts a lot of burden on your integration
It might make more sense to use Stripe Invoices/Subscriptions.
tawny jay
I looked into the save and reuse, it did not seem to fit. I think the same problem, each Setup Intent is tied to one payment method.
How could we use this kind of group purchasing behaviour with invoices or subscriptions? Each booking could be a different value and volume.
quick sequoia
As I said, each Customer would represent the entire account. Also you would need to use only 1 payment method so Setup Intents would still work.