Accept a payment 

Same here. I however have a Squarespace shop and am wanting to understand how to set this up. This video is very confusing since it doesn't explain how to do this through Squarespace.

Sorry for any confusion, @Michał. Happy to chat on Twitter (@cjav_dev) if you have specific questions.

The `line_items` field on a Checkout Session is an array of hashes, so you can pass in a maximum of 100 items with prices/products: stripe.com/docs/api/checkout/sessions/create#create_checkout_session-line_items

To clarify, by one time payment we mean that the charge is not a subscription/recurring payment!

Hey Sukhjeet-thanks for flagging this with us. We can take a deeper look into what's going on with you-would you mind sending an email to us at heretohelp@stripe.com?

Hey Debbie, great question. Ultimately this depends on where your Stripe account is located, alongside some additional factors such as your bank's processing times. We have more details on how payouts with us work here: stripe.com/docs/payouts#payout-schedule.

Hey Omar: this is information you'd typically store in your own database associated with the payment intent id. You can also use the payment intent metadata to store something like an order_id from your own systems so that you can look it up directly upon receipt of the webhook event.

@@nolan-stripe3628 thank you so much for answering! So, the flow goes like this: every time the checkout page is loaded on my e-commerce site, I fetch a payment intent from the server and I pass in the shopping cart data: (items, quantity, price, etc), then on the server I verify that the prices are in fact correct (since I can’t trust the client data), and I create a pending order in my database and store the verified items, prices and total along with the paymentIntentId, and when the payment is completed and I get the web hook event, I look up the pending order associated with that payment intent, mark it as paid and initiate my fulfillment process. This seems like it would work but I was not sure that was the best practice since that means I have to store in my database a pending order every single time a customer visits the checkout page, even when they don’t plan to actually buy, and also storing a different pending order even when they just go back and forth or refresh the checkout page since I’m creating a payment intent when the page loads. Just seem like a lot of data to store but I surely can do if it is considered a good practice. It just felt wrong to me because all the pending orders I could end up storing, or is there something I’m missing in my understanding of how the flow should be?

@@omarsuriel1112 That sounds about right. If you don't want to store these pending orders you'd need to change your business logic to persist a temporary order for a customer and have a payment intent associated with it. Alternatively, you could defer creating the order/payment intent until the customer expresses intent to pay. Eg make the server call after they click whatever buttons you have. A "pay now" button can retrieve the payment intent client_secret from your server just before using confirmCardPayment.

@@nolan-stripe3628 thank you so much Nolan! Thanks to your advise I almost have the whole payment thing completed! I ended up creating a potential_order tables and storing a JSON + other normalized data including the paymentIntent. And then retrieving the potential order and making it into a real order when the payment is made. But I also followed the best practice listed in the documentation and I am using the same payment intent for the same customer shipping cart and what I’m doing it is updating it if they already have one and also updating the potential_order related to that paymentIntent. That way I’m not saving a new potential_order every time the checkout page render. Thank you so much!!!!!

@@omarsuriel1112 Glad it was helpful! Sounds like your integration is now in a much better place :)

How to upload on control panel

@@rozinulhaq6301 I'm afraid I'm not sure what your question is. Would you mind writing into support directly at support.stripe.com/contact ?

Hey Jayda, This is if you're building a custom integration. The simpler path is to use Stripe Checkout. Feel free to reach out to @cjav_dev on twitter :)

Hey Xuan-we're sorry to hear if this was your experience with us. We'd like to help-could you send us an email at heretohelp@stripe.com so we can investigate things further with you?