#johnvdenley-legacycheckout
1 messages · Page 1 of 1 (latest)
Where is the screenshot you're looking at from?
Also is this a new integration, or one that you already have that you're trying to update? I ask because you're using a very old product that we no longer recommend, so if this is a new integration I'd recommend using something else
johnvdenley-legacycheckout
@frosty magnet Did you see my questions?
The Screen shot is from my live application, it was written by some Russian coders back in 2020, but the original code for the application was written back in 2009 (by me) but we were previously using PayPal and I got them to modify my code to make it work with Stripe, but there's a number of problems, so I might be open to looking at alternative options!
the problem is I have not done any coding for years, so I may struggle to implement something new from scratch!
gotcha!
So starting off with your description question - the code you sent over is just the frontend code while the description from the screenshot would be controlled by your server-side code (whatever is creating the Charges)
In terms of things I'd suggest as alternatives there's a number of alternatives - you could look into stripe-hosted pages (like Checkout or PaymentLinks) which require less coding work or your could look into building a custom payment flow (see https://stripe.com/docs/payments/accept-a-payment?platform=web&ui=elements)
If you're interested in Checkout we have specific docs talking about how to migrate off your legacy version (https://stripe.com/docs/payments/checkout/migration)
Checkout sounds handy and I guess that would also solve the problem I have with this:
Yeah that's one of the reasons we don't recommend what you're using anymore (we call is Legacy Checkout)
The new Checkout solution we have would handle 3DS for you
OK cool, thanks. I will check out that doc and see if it makes sense to me... I am actually planning to change how I charge my clients anyway and pretty much allow them to create their own package price... so I need to consider that too moving forward
If you need customers to be able to pay what they want you may also want to look into these docs as well:
oh thanks, yes maybe, essentially they get to say "I want to buy 35 text credits" or "I want to buy 420 text credits" and the potential would be the more you buy the less per unit you pay (I guess its a "bulk order" scenario)
Got it - you'll probably want those adjustable quantity docs then combined with tiered pricing (https://stripe.com/docs/products-prices/pricing-models#tiered-pricing) definitely try those out and see how it goes
thanks, PHEW, tough weekend ahead!! LOL I Thought my coding days were behind me!