#poison-legacy
latent dove
hello, what do you mean by legacy Stripe?
Regardless, it should work, so I assume something isn't working or an API call isn't being made
sharing request IDs would be a good start
severe vault
https://stripe.com/docs/payments/checkout/migration
The one migrated away from here, haha
The modal version
latent dove
I'd recommend sharing https://dashboard.stripe.com/test/logs/ logs from this page to see what /v1/tokens and /v1/charges requests are being made
severe vault
I don't see /v1/charges in the tests, so that could be a problem
But I do see /v1/tokens
Request ID of the latest token from test mode is: req_hEEMMiyihGonUX
And the latest token in live mode that returned successfully was: req_FT3ZKOzVJb8bEH
The one in live mode still did not charge though
mortal magnet
@severe vault Is your code creating a Charge though or just using/showing Legacy Checkout?
Looking at our logs for example you never tried to use the Token id tok_1JYD4oGlsdN3sDOJeHljB6mA to charge a Card/Customer
severe vault
You know, I was just assigned to this today, so let me look around to see, I was assuming that the legacy checkout took care of that possibly
Is there documentation for the legacy checkout around somewhere? I couldn't find it earlier
mortal magnet
yeah Legacy Checkout is just a UI to collect card details, nothing else. That's why we built the new version that creates the charge for you and is way better
So after Checkout creates a Token you submit it to your server where your code would call https://stripe.com/docs/api/charges/create to charge that card, which is the part that doesn't happen right now
I don't think we have docs left for this today it's been deprecated for 3 years now
severe vault
Oof ok, I should probably look into adding the new one then, I'm trying to add it in Coldfusion and it looked like it would be a pain
mortal magnet
We don't support Coldfusion but we have a stripe-java library
severe vault
Yeah I saw, that's why I was attempting to continue to use the Legacy version. I might be able to find a wrapper or something for it though it probably will be a complete pain
Thanks for your help though! I didn't realize that we had to make a charge separately, I'll probably try to use PhP or something to process charges instead
mortal magnet
Overall even with Legacy Checkout you need server-side code in Coldfusion
severe vault
Yeah, so I think just switching the server-side processing to one of the officially supported languages would be best, I can try to implement a custom-flow payment with the new checkout version as well if I do
mortal magnet
awesome!