#Kasuni

1 messages · Page 1 of 1 (latest)

limpid prismBOT
odd crystal
#

hi! you can't just get the details themselves. The PaymentElement is designed for confirming a PaymentIntent or a SetupIntent. What's your overall objective?

echo lake
#

For example , if user is reach the payment page and not paid like situation .
But we creating payment intent in stripe to just load the payment element. i was just thinking way to stop it

#

Not sure is it possible

odd crystal
echo lake
#

Oh Great! Thanks for the information:)

#

Hey, If i used this test card 4000 0025 0000 3155 , Is it ask authentication for every payments?

odd crystal
#

it would ask for every on-session payment(a payment when the customer is physically there entering their details, yes), but can support payments without 3DS for recurring payments

echo lake
#

What about using this as stored card?

odd crystal
#

what does that mean?

#

that card is very well documented at https://stripe.com/docs/testing#authentication-and-setup , what can I clarify?

This card requires authentication for off-session payments unless you set it up for future payments. After you set it up, off-session payments no longer require authentication

echo lake
#

i saved this card for future payments and used to make a payment

#

but its still ask authentication

odd crystal
#

did you pass off_session:true when making the payment?

echo lake
#

i confirm payment in front end using stripe.confirmcardpayment

#

how to pass the off_session there?

odd crystal
#

you don't since that is not an off_session payment then.

echo lake
odd crystal
#

yeah paying with a stored card like that (customer is on the website and picks their saved card) still requires 3DS when using that card, that is normal.