#mckay_best-practices
mossy sunBOT
đ 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/1417282631292162130
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
reef rampart
hello! fyi i am juggling a few threads but i will get back to you asap
digital kernel
No worries, this isn't super urgent so please take your time @reef rampart
reef rampart
ok, sorry for the delay, looking into this now
digital kernel
No problem, thank you!
Let me know if any clarifications are needed, I also have a stripe account ID I can give you to our sandbox if needed.
We're in the final stages of the sales process but were provided two terminals from stripe to begin integrations
mossy sunBOT
sick jetty
Hi @digital kernel I'm taking over this thread. Give me a sec to catch up
Thanks for waiting. The paid_out_of_band param is only applicable for invoices API, not payment intents API that you use for terminal integration.
So basically you want to collect a card_present payment with a terminal reader, and mark another invoice paid_out_of_band ?
digital kernel
So basically you want to collect a card_present payment with a terminal reader, ...
Yes yep. Ideally still attached to the same customer
sick jetty
Ok. if you specify a customer when creating a paymentIntent, then the payment is associated with the customer.
When you create the invoice, one thing you might want to take note is to set auto_advance to false so that Stripe won't automatically charging the customer if they have a default payment method for invoicing.
digital kernel
Okay thank you I will do that
One more question Jack, when creating the invoice, it seems like the minimum number of days is 1 for when the payment is due
But the business usage of our application kind of requires a matter of hours. Example
Customer drops car at dealership
Car is ready, vehicle is ready for payment, stripe invoice created (due on day of invoice generation if possible)
invoice can be paid via hosted url OR
customer decides to pay via Physical Terminal, invoice is marked as "paid_out_of_band" and then a terminal checkout is created with that customers stripe ID... what if the customer doesn't yet exist in stripe? Will we generate a customer ID first?
I just want to make sure that the metadata associated with the original invoice, through our API calls, is able to be associated with the terminal transaction as well. These are essentially "line items" for services recieved.
Example - oil change, tire rotation
sick jetty
Yes you 'll need to create a customer before creating a invoice.
digital kernel
Okay will do
digital kernel
But the business usage of our application kind of requires a matter of hours. Ex...
Does this sound like i'm on the right track
sick jetty
Yes it looks good to me. So you'll want to create/retrieve the customer first before creating an invoice.
Also the auto_advance param that I talked earlier is for invoice with collection_method=charge_automatically. You can ignore it since your are creating invoices with collection_method=send_invoice