Stripe Elements Support

[Emiel]

Sure @Teodor,

Apart from the issues I am having currently, there’s the low maintenance and the way much easier implementation:

@Emiel

• Automatically adjusts input fields to collect information based on the payment method and country.
• Dynamically sorts payment methods based on a customer’s locale and location to optimize for conversion.
• Reduces friction for card payments with input validation, masking, styling and error handling.
• Adds new payment methods without any front-end changes , and gives you access to new payment methods as soon as Stripe supports them.

The issues I had lately and partially still have currently are described here and here and besides that I can’t get the submit handling right when combining Stripe’s scripts with Wappler’s components.

Following Stripe’s guide I would say integration of the Stripe Payment Element would be quite easy:

1. Add Stripe key to Wappler Server Connect Settings
2. Add the Stripe component to the checkout page
   (With step 1 and 2 done, the first 6 steps of the Stripe tutorial are covered, up to the “Fetch a PaymentIntent” step.)
3. So going further I create a payment intent through a server connect action and output the value to the checkout page.
4. With some custom scripts (thanks to @karh) on the checkout page I am able to create the Payment Element with the correct clientsecret from the paymentintent set and style it on the checkout page.
   (So we’re up to step 3 of the Stripe tutorial: Complete the payment on the client)
5. This is were trouble comes in: On clicking the submit button I can’t get the payment done (for cards i.e.) and users are not redirected to 3rd party pay site (like sofort, ideal, etc). I can’t get this right and it’s almost as hard to find help with that.
6. If Payment Elements was integrated in Wappler, besides the great advantages mentioned above, all variables and attributes would be easy to set, which is another thing I am really struggling with. And moreover custom scripting on the checkout page wouldn’t be necessary either.

Curious about your thoughts on this and would be happy to hear them.

BTW: If you could manage to setup a working example of Payment Elements in the current Wappler version I would be very very interested to see that!!