#cnguyen

1 messages · Page 1 of 1 (latest)

misty reefBOT
gleaming salmon
stark cipher
gleaming salmon
#

It's about the payment element to mount

#

Can I customize it like that ?

#

because, for now, I have all in one line with card element

#

and with payent element, I have a big block with tabs (can we remove the tabs?)

stark cipher
#

Payment Element supports multiple payment methods, so tabs will be shown if there are multiple payment methods supported

#

Are you looking into to collect card payment only?

gleaming salmon
#

to make a payment intent

#

with stripe element

stark cipher
#

Payment Intent works for Payment Element and Card Element.

Payment Element allows supporting multiple payment methods. Do you intend to support card payment only, or multiple payment methods?

gleaming salmon
#

yes card pauement only

#

only stripe card

#

as usual

#

not the new one (klarna, etc)

stark cipher
#

If you only want to accept card payment and wish to achieve the above design, you can use separate Card Number Element, Card Expiry Element and Card CVV Element for each individual field and place them according to your design above: https://stripe.com/docs/js/element/other_element

gleaming salmon
#

ok i check

gleaming salmon
#

With that, the behavior is different. I don't have to give the pi_secret to the element form. COrrect ?

#

And it will attach automatically the pm to the customer too?

pine owl
#

👋 taking over for my colleague. Let me catch up.

pine owl
#

to use the pm for future payment your PI should have setup_future_usage param on it either on creation or on confirmation

gleaming salmon
#

ok so event with the separate field (cvc, card number, etc).... I have to give the client_secret to generate it ?

#

Like the Stripe Element form ?

#

and yes, on the pi createion, I set the setup_future_usage to iff_session for later