#PeterW
1 messages · Page 1 of 1 (latest)
let me check if we have a changelog and get back to you. Is there a reason why you're using legacy Stripe Checkout though? We'd strongly recommend switching to the latest Checkout
Yeah been meaning to switch to Elements actually, just haven't had time yet. If Stripe happened to have a Checkout example that's more focused on donation use case rather than like, selling cars and widgets, that'd also be helpful! 🙂
https://stripe.com/docs/checkout/integration-builder - you can select the pre-built checkout page or custom payment flow depending on what you want
the underlying mechanism isn't going to be different whether you're doing donations or selling items, is there perhaps some feature that you're looking for which the example doesn't provide?
Ah cool, hadn't seen that before, will take a look!
Hmm, this part - "Checkout has three modes: payment, subscription, or setup. " - I assume there's an easy way to handle presenting the option between (one-off) payment or (recurring) subscription?
if you want to offer both as an option to your donor, you would have to code that in your own form, and then pass that in as a parameter when creating the Checkout session
Thanks. Is there any example code that does that by any chance?
not in the Stripe Sample unfortunately, but there should be resources available online on how to pass in different kinds of information in your form to your backend server to process
Thanks Alex. Yeah I'll need to dig into it a bit more when I have some time (which is… limited!). Speaking of… does Stripe give their devs any spare time to help nonprofits with integrations by any chance? 🙂
if you have specific questions / integration issues, we're always here to help. If you need to hire a developer to help you from scratch though, we can point you to some of our verified partners : https://stripe.com/partners/expert-services
That's what I figured. Thanks though. For now, I'll go fix my Cypress tests that this undocumented change inflicted. 😕