#colin-subscription-multiple
hoary steppe
Hey @fiery seal ! It depends a bit how you plan to integrate with our products and APIs as there are many ways to do recurring payments. Assuming you use our Billing product where we automatically charge the customer's payment method details on each cycle (say each month) then you would create a Subscription that has the right set of "Products and Prices" associated with it.
See https://stripe.com/docs/billing/subscriptions/multiple-products
colin-subscription-multiple
fiery seal
Thanks, I'll check those docs out. Does it make a difference if this is not any sort of recurring payment, but rather a once-a-year charge that's more along the lines of annual school fees rather than eg Netflix?
hoary steppe
Kind of, you can still do "yearly Subscriptions" in that case and each year decide how much to pay. But you're also allowed to just charge for the total amount at the start of the school year either by creating a one-off Invoice (which usually has separate line items for what is being bought) or just using our PaymentIntents API to charge the total amount without any breakdown
fiery seal
PaymentIntents sounds like what I'm looking for. In that case, would I need to bother with product objects at all?
hoary steppe
correct
in that case you likely want this guide https://stripe.com/docs/payments/accept-a-payment?platform=web&ui=elements
jade socketBOT
fiery seal
So everything I'm seeing in the docs looks way more heavy-handed than I'm expecting. All the UI for card entry etc. already exists. Literally the only thing we want to do is say "here's a card number and amount". There shouldn't be any need for anything Stripe-related at all at the client application level.
hoary steppe
yeah that's not how things work really. You're not supposed to have the card number on your end at all. You have to use our UI to collect card details to meet PCI requirements, it was likely the same on Paypal. See https://stripe.com/docs/security/guide#validating-pci-compliance so really you have to switch to our UI components
My colleague @oblique vine is taking over if you have follow up questions
fiery seal
it was likely the same on Paypal
That is defintely not the case. I get the cc details from a form we wrote, and shuffle them along to paypal on the backend.
hoary steppe
Are you a PCI level 1 company? If not, you likely... got lucky
fiery seal
no, they're just a little 501c3 that organizes sporting events for kids
hoary steppe
Yeah then you should never have built it this way, you likely break most PCI rules 😅
I highly recommend reading https://stripe.com/docs/security/guide#validating-pci-compliance carefully and related information on PCI compliance. But really getting raw card numbers server-side is extremely dangerous for your/their business
fiery seal
we don't store any cc info at all. It only ever lives in memory
hoary steppe
even then, this comes with extremely strict rules