Stripe supports idempotent requests.
I don’t see a way to add this on the GUI for example, when making a new payment intent:
For me it looks logical for it to be under advanced options.
Is there a way to add this (preferably on all GET requests)?
Thanks!
Many of us that have Stripe incorporated into our site have struggled with the difference between Stripe’s object models and Wappler’s. The Wappler team initially took a brave step to offer Stripe components in the native Wappler UI. However, keeping their object models updated to reflect the latest Stripe object models wasn’t possible (my opinion and observation due to the lack of updates to Wappler’s Stripe components).
Therefore, we Stripe customers have moved on to using Wappler’s API Action component, along with the excellent Stripe docs and sandbox environments. Being able to quickly copy/paste Stripe’s object model into the API Action, so you have access to it correctly in your server connect API, is what I would consider standard process now when using Stripe with Wappler.
So for your question, you may not ever get Wappler to natively support idempotency in the current Stripe components, but you can easily use it if you switch to the Wappler API Action.
Thank you. I feel your frustration, and thanks for sharing/ input. I really don’t want to refactor most of our calls, but I guess there is no other option. At least going forward we likely won’t depend on the ui.
@George @patrick ever considered open sourcing these things? Or just make them easier to tweak?
Thanks!
Stripe api and components are updating so fast that not only we can’t keep up but their api is also continuously changing.
So you have to pin to specific api version and use the components for it.
So our plan is to separate the Stripe components as custom extension published on npm that can be updated as needed but you can choose and stick to the version you want.
