#x-LegacyCheckout

1 messages · Page 1 of 1 (latest)

drowsy knot
untold lark
#

oo

drowsy knot
#

Hello, checkout.js is a legacy flow. Could you elaborate on why wouldn't you just use the newer Checkout Product?

untold lark
#

because its too hard for me to code

#

i dont know alot 😐

#

im fine with this old layout i will just change whole theme of my modern website

drowsy knot
#

The newer Checkout should be easier and have a lot more support (= less headache) Could you tell what do you want to achieve?

untold lark
drowsy knot
#

what popup are we talking about?

untold lark
#

it has a modal pop up

#

i want that with the new modern stripe look

#

i couldnt find anything on github

#

😐

#

?

#

@drowsy knot this is it but its gonna be hard changing html

#

why getpublickey function

#

if its already defined in the js

drowsy knot
#

Let me take some time looking at it. (will be back)

untold lark
#

oki

#

ping me when you are back im gonna be trying myself

#

also how would i add

#

custom customer email input

drowsy knot
#

In the step "Templates" I see you can define CSS rules to control the look and feel. I think the Github repo does the same

#

then in the script block I see data-amount which let me to think that it wouldn't be able to add an amount field yourself

untold lark
#

oh

drowsy knot
#

Normally Checkout doesn't provide that level of flexibility. If you want to have control over fields, you would normally want Elements/PaymentElements

untold lark
#

uhoh

#

i will just keep 😐 the

#

old layout

#

um i like it anyway 😭

#

i will try yours

untold lark
#

i tried a while ago and it was deemed risky after i donated to myself to test out the page

#

😭

#

also @drowsy knot when i use checkout.stripe.com/checkout.js thats all i need for the payment it does the rest for me like i just put the secret key and thats it?

#

no backend just that

drowsy knot
#

You still need backend. Like the guide above states

#

Either new Checkout of this legacy flow, you still need backend. That's why new Checkout is better

untold lark
#

with the custom checkout page

#

like a non coder 😭

#

i just want a modal

drowsy knot
#

The newer Checkout is only one API call to create the Session, and one redirection to its URL

untold lark
#

i saw that one

drowsy knot
#

Even easier, there is PaymentLink that doesn't require backend, but you will need to do some manual work from Dashboard

untold lark
#

what kind of work from dashboard

drowsy knot
#

Taking the link from Dashboard. But it will be redirection anyway. Is your problem that you want a modal?

untold lark
#

if im using stripe for a portfolio to accept donations what category would my business be

#

or industry i would put donations but thats risky i dont wanna not get approved

#

hey they accepted it

#

@drowsy knot pci client is stripe.js right?

drowsy knot
#

stripe.js is pci compliant, if that's what you are asking 🙂

untold lark
#

im trying to test this integration stuff

untold lark
#

now my account is actinve

#

what to do 🤔

#

setup the custom payment

#

the backend part is

#

payment intent api i found that on stripe github repo

#

so i just have to implement that somehow and i can accept donations

#

im on stripe dev yt page 😭 idk whats going on

#

shouldve gotten my degree in cs 😔

drowsy knot
#

Do you really want to go for the Legacy Checkout integration path? It has way less example/support at this moment. For easier get it working I would recommend with the new checkout flow

#

It would be way easier for you

untold lark
#

i just want it on my url idk i just dont want it on stripe.com 💀

#

it looks clean when you have stripe integrated

drowsy knot
#

i just want it on my url idk i just dont want it on stripe.com

#

That would comes down to PaymentElement integration. But because it's not prebuilt by Stripe anymore, it would requires more work

untold lark
#

oh

#

im watching the

#

Accept a payment - Create a PaymentIntent with Node.js

#

its so many files

untold lark
#

the payment intent

untold lark
#

@drowsy knot i have made my choice

#

i want to use the legacy api

#

now i have the back end and frontend done

#

how to i implement backend in frontend

drowsy knot
untold lark
#

ok

#

ok thanks* will learn

#

@drowsy knot it says test mode

#

im using live keys though?

#

oh nvm

#

it auto filled test key from example

#

oh ok so how would i do backend

#

@drowsy knot this is worse you got any good docs for custom payment elements

drowsy knot
#

You mean normal Payment Elements, not Legacy Checkout?

untold lark
#

i have it down

#

but i want to know how to create a charge

drowsy knot
untold lark
#

not a payment intent

#

i think i need to create a token

#

and then a charge?

#

@drowsy knot a payment intent is just a hold not a charge right?

#

this is hard

#

its just using payment intent on youtube

#

i want to charge 😭

drowsy knot
#

PaymentIntent is newer API and recommended. You wouldn't want to go over charge/token which is legacy stuff

untold lark
#

oh

#

so does paymentintent charge?

#

"status": "requires_payment_method",

drowsy knot
#

PaymentIntent contain a Charge object inside.

untold lark
#

what i got whe nusing live mode

#

so i have to create a payment method

#

then request payment intent?

#

@drowsy knot document.getElementsByClassName('submit')[0].addEventListener('click', function(e) {

#

i could use to make a payment

#

method?

#

and have it hidden