#Aby

1 messages · Page 1 of 1 (latest)

normal geodeBOT
thin onyx
#

hi! just to clarify, what specifically are you referring to when you say 'payment link'

shell plover
#

Stripe PaymentLinks

thin onyx
shell plover
#

Yes, exactly

thin onyx
#

then I don't really understand the question.

if you have a payment form using Checkout, you don't need a PaymentLink. All a PaymentLink is is a re-usable link that redirects to Checkout. If you already have a website that creates a CheckoutSession and redirects to it, you have basically created the same thing

#

and if you have a payment form using Elements, why do you also need a separate way to pay using a PaymentLink?

shell plover
#

Oh, sorry, my bad. I just have been missunderstanding something. Basically if we create let´s say a button in our website with a PaymentLink that would redirect our end user's directly to the checkout page, that checkout session could be embedded in our website without redirecting our users to Stripe's website?

thin onyx
#

hmm. If you are using a PaymentLink, that means you have a button on your site, like aby-site.com. If I click that link, I am redirected to checkout.stripe.com , and I pay there.

shell plover
#

It completely make sense.

#

Really appreciate your guidance

#

Thank you!

thin onyx
#

is your concern mainly that you don't want end-customers to be redirected for their payments?

#

if so then you would normally build your payments integration to use Elements like the PaymentElement, as those are components that you embed into your own existing web pages with no redirect.

shell plover
#

Exactly! that´s what I was looking for. So if we use Stripe Elements, the end customer´s won´t be redirected for their pyaments and the payment form would be embedded in our site right?

thin onyx
#

yes

shell plover
#

Completely understood.
Thanks a million!