#JohnnyB - Link

1 messages ยท Page 1 of 1 (latest)

white swallow
#

HI ๐Ÿ‘‹
Unfortunately that level of customization is not possible currently with the Payment Element

split umbra
#

and Card Element doesn't allow wallets nor use of Link, correct?

white swallow
#

Correct. The Card Element is only for collecting Credit Card information

split umbra
#

any logic/alternatives to minimize the card number, date, and cvc in a single field in payment element?

white swallow
split umbra
#

it's such an elegant solution but limited/gridlocked to multiple input fields that capture the same

#

can we float as a feature suggestion? seems natural

#

i mean, look at that!

white swallow
#

Oh wait, have you tried adjusting the fields displayed when rendering the payment element?

split umbra
#

no

#

please explain

white swallow
#

Okay so you don't want the two rows?

split umbra
#

only the two rows

#

normally look like this:

white swallow
#

I think the create options I linked can help get rid of the last row.

split umbra
#

will review

#

so it would bundle exp, cvc, and zip, just like card element does?

white swallow
#

That it won't do

#

If your device is wide enough it'll display card number, expiration, and cvc on the same line but as separate fields

split umbra
#

hmmm

#

thank you for your helop

#

help

#

last question then, for the sake of high-traffic transactions where every secondo friction counts

#

of*

#

people will be on the phone as they pay, so bounce needs to be addressed

#

is there a way to use the payment element cc fields, and display the wallets (perhaps only as images) as well as the Link option, and if either the Link or wallets was selected, then to transfer the process to a Payment Element display or page?

white swallow
#

You mean instead of the top row of payment method options?

split umbra
#

I mean, use images/links of the wallets on top, then the Card Element single field, and below an image/question/link for remembering for future use.

If someone selected to use a wallet, it would transfer you away from Card element and to the Payment Element page, same if someone clicked on enabling Link

open meteor
#

๐Ÿ‘‹ stepping in here as Snufkin has to step away

split umbra
#

no problem at all

#

thanks Snufkin

open meteor
#

So to understand... you want to handle a redirect to a page where you would render payment element based on a user action like clicking an image in your UI?

split umbra
#

exactly

#

and those images would be mimics of the functionality that Card Element lacks

#

we have 4M phone calls per month, we're adding a new feature with self-pay. Single fields are easier to present (time, bounce, etc). But Payment Element has 4 fields vs Card Element's single

#

Just trying to find a workaround to display single field (for cc, date, cvc, and zip) while also offering local wallets, and the ability to use link

open meteor
#

Gotcha

#

Then yes, you could do what you are talking about

split umbra
#

I understand PE is required for wallets and link, but not sure the single field feature from CE doesn't survive

#

Thank you

#

would you mind walking us through it?

open meteor
#

You could also disabled wallets from PaymentElement and render PaymentRequestButton alongside card element

#

Then have a button for Link at which point you redirect to a different page with Payment Element

split umbra
#

hmmm

#

but is Payment Request button only for Apple and GPay?

open meteor
#

Yes

#

Are you looking for other wallets?

split umbra
#

yes

#

globally

#

so we like that Payment Element allows for a carousel of wallets

#

and if we use images, then the carousel's intelligence gets wiped out

#

I guess we could use Apple Pay, GPay, and use a link for "Other"

#

we have callers from 100+ countries

open meteor
#

Gotcha so you want things like WeChat Pay as well

split umbra
#

Grab Pay, Ali, Wepay, etc

#

In a perfect world, the field looks like this:

#
  • the Link option/check box below
open meteor
#

Yeah we do want to provide further layout customization for Payment Element in the future

#

But the above isn't possible right now

split umbra
#

that would make sense

#

gotcha

#

Is there a way to be notified?

#

would this work for now:

  1. Use Card Element
  2. Enable Payment request button for apple pay and Gpay
  3. Add a link/image for "Other" wallets
  4. Add a link/image for Stripe Link"

Option 3 and 4 would redirect to a Payment Element page (with wallets enabled, because why not).

Any comments on feasibility and if any risks?

open meteor
#

Yep that would work totally fine.

#

You can use the same client secret so you don't need a new PaymentIntent or anything.

#

No real risks that I can think of

split umbra
#

ok great