stripe.js elements

[Robin Williams]

Hi

I am aware there have been many many discussions and issues regarding "elements" in stripe.js.

In v2, you guys delivered a great javascript API which enabled us to create our own GUI and then do all the necessary backend stuff in Javascript - it is easy to work with and works excellently and we have been very happy with it.

I appreciate the hard work you guys have put in to offer GUI widgets [elements] out of the box.  For some people this works, although it appears that some of the GUI tweaking required has been a bit painful for some.

Our GUI includes automatic inbuilt help (delivered through AngularJS) and the Elements widget actually breaks our GUI as it is not possible to tweak Elements to match the GUI used throughout the rest of our site..

So to give flexibility to developers it would be REALLY helpful if you guys could expose the underlying API (along the lines of v2) to give us developers the option to use Elements or our own GUI components (the ones that we wrote and use successfully in v2).

Is there any reason that you absolutely could not do that - or is it something that could be on the cards - I think it would help to keep many developers using Stripe happy to have that option.

Thanks very much.

Kind regards

Robin

[Remi J.]

Hey Robin,

One of Elements' strengths is that it helps put your integration under the lowest level of requirements for PCI compliance: SAQ A. The reason is that the card details are entered directly inside an iframe served off of Stripe's servers and your page can not control it or tamper with it. This makes it easy for anyone to write an integration while meeting that level of PCI compliance.

Stripe still supports Stripe.js v2 integrations and we do plan to offer similar methods in Stripe.js v3 in the future so that you can build your own payment form on your page. This comes with a higher cost for the PCI Compliance level though. For integrations like those, you get the card details directly in your page and you end up falling under SAQ A-EP instead of SAQ A.

You can read more details about PCI compliance here: https://stripe.com/docs/security#validating-pci-compliance

Separately, we'd love to better understand why Elements did not meet your needs. Most of the UI and styles can be customized to suit your own needs both as the single line element or with separate fields such as in this example [1]. You should be able to reproduce your existing form logic via Elements. If that's not the case, you can contact our support team directly here [2] to discuss the situation and see if we can come up with a solution that works for you.

Best,

Remi

[1] https://jsfiddle.net/kc6mh6tb/

[2] https://support.stripe.com/email

--
You received this message because you are subscribed to the Google Groups "Stripe API Discussion" group.
To unsubscribe from this group and stop receiving emails from it, send an email to api-discuss+unsubscribe@lists.stripe.com.
To post to this group, send email to api-d...@lists.stripe.com.
Visit this group at https://groups.google.com/a/lists.stripe.com/group/api-discuss/.

[Robin Williams]

Hi Remi

Thanks for your excellent answer which explains things so clearly.

We will look carefully at the links you sent as we consider our future migration.

Are you able to give any rough idea of timescales for the v2-like methods for v3?

We will also look at what our issues are with elements and get back to you with those if/when appropriate.

We are currently focusing on development of another part of our system and will return to look at stripe.js in more depth once that is done.

Kind regards

Robin

To unsubscribe from this group and stop receiving emails from it, send an email to api-discuss...@lists.stripe.com.

[Remi J.]

Hey Robin,

Are you able to give any rough idea of timescales for the v2-like methods for v3?

We don't have a firm timeline just yet but v2 is still fully supported on v2 and this version is not going anywhere. There are numerous integrations relying on Stripe.js v2 so it will be supported for a long time. It's similar to when we released v2 of Stripe.js a few years ago and kept supporting v1 at the same time. After the release, v2 was improved to fully support what v1 did at the time and both versions now point to the same exact file. Integrations built with Stripe.js v1 still work today and the change was entirely transparent for them.

We will also look at what our issues are with elements and get back to you with those if/when appropriate.

Perfect! We'd love to hear any feedback you have around the integration, the pre-built UI components and any issues you encountered!

Best,

Remi

 

To unsubscribe from this group and stop receiving emails from it, send an email to api-discuss+unsubscribe@lists.stripe.com.