#hobbes-paymentelement-migration
1 messages · Page 1 of 1 (latest)
Hi 👋
You should not host the Stripe Elements inside an iframe. This will block Stripe.js from being able to perform many of it's useful functions including fraud detection and privacy screening
Let me confirm with dev--I thought it was iframe.
Stripe automatically creates an iframe that the Stripe Payment Element loads in. But if your site is also hosting it inside an iframe that will cause some problems
Oh! No there is not a double iframe. Sorry for confusion.
Okay so you want an interface that automatically hides the CC number when entered?
Yes correct.
All other fields not as important if we can at least blur the CC number. Would prefer all fields work this way if possible.
Right, I can understand that.
The Card Element doesn't do that by default. Were you using style rules to achieve that effect?
I apologize, I wasn't able to ask original developer how it was done. I thought it was just a feature within the stripe.js that could be toggled.
Unfortunately it looks like not. I will raise this feedback as a feature request though.
Would you say this is a requirement for migrating to the Payment Element?
It is. We are worried about user security if in public spaces, that all information is onscreen at once and could easily be seen over someone's shoulder.
So there is no current way in Stripe to achieve this?
Unfortunately it does not look like it. I can raise this as a high priority feature for your integration.
Is it possible to break elements apart and enter cc number in field and then hide entire field once entry is complete?
Just trying not to have all info on screen at once.
No, the Payment Element does not allow you to separate out the inputs.
Understood. So we will have to implement full custom checkout if we want this feature?
You can continue to use the Card Element
I did raise this internally and stressed it is a make or break requirement for your integration