Hi all,
Just wanted to get your input on how everyone is integrating payments.
Coming very soon: Thursday, the most unproductive day
Well that couldnāt be more timelyā¦ now only if I was more familiar with their release schedule 
Sorry to burst your bubble, but not really.
There is an update every Thursday. But its not indicated if WHS is coming on this Thursday.
The post says its in the works and it should be released soon. It could be this Thursday or any next one.
Hey @izzyā¦
Iām interested to know what you want to gain by there being any kind of official Stripe offering in Wappler.
I sense from your contribution to the āGarageā post you are very experienced, so are just looking for a simple setup for each project?
You donāt sound like the kind of user who canāt work out how to interface with Stripe yourself!
I see some core modules have already been added in the latest release do probably not much longer to wait, maybe a couple of Thursdays?
I see the basics have been included for charges/payment intents. Would be good eventually to get some of the other APIās included such as invoices and billing.
@Antony I think the benefit of having Stripe included is that not only will it be simpler for beginners to start building but it will also save us more experienced users more time by not having to integrate a card billing api. I know Iālol be grateful for having it built in knowing the amount of time it will save me, especially for multiple projects.
Yes @max_gb, I can see the benefits in what you are saying.
I guess my experience of putting together a Stripe interface is that I ended up refining an awful lot of the detail and calling multiple stripe APIs at different times to achieve the results I want.
It gets to be quite a thing when creating the Payment Intents flow, integrating it into the flow of your user experience around your store, storing and managing the payment intent and client secret keysā¦ as I am sure you know, it is nothing like ācall an api and all is doneāā¦
ā¦ and then my app supports sales in multiple currencies tooā¦
ā¦ maybe Iāve just got a particularly complex (or sophisticated? 
) application!
I think having an integrated approach to Stripe will allow many more users to experience the full power of Stripe.
I was able to get a simple, one product, site set up with help from @max_gb . But Iād love to expand that and include some of our theatre souvenir products. Where I would run into big issues is setting sales taxes. Luckily I didnāt have to do that for our tickets.
I really look forward to what else I can provide with these upcoming tools.
@antony the answer to your question will depend exclusively on the implementation Wappler does. Your app may or may not be as complex as you think and the implementation may or may not fulfil your actual needs. It might fall short or it might have all the calls you needed at the time that would have saved you time.
This is actually fairly simple. Iām not sure how your local sales tax works but you can set these up in the Stripe dashboard. Once theyāre setup and youāve been given a unique id, you can pass this in the api call. Itās just one extra line in the tutorial I created. Simply add:
āline_items[][tax_rates][]"="{{TAX_RATE_ID}}ā
Stripe checkout will then automatically add the required sales tax.
Our goal is to make the Stripe implementation as easy as possible but also powerful for the advanced users.
For the easy usage, we will use the client side only stripe checkout, where you can just post your products for checkout at the stripe hosted page and then return to your site. No server side is required here.
For the advanced usage, we will cover most of the Stripe API actions that you can insert as Server Connect actions. We will be following the stripe API calls so you will be able to use the exact same flows as described on their docs.
Next we will have a new general webhooks possibility on Server Connect, where you can attach your own actions fully responding on a provider events -Stripe in that case.
Furthermore on the client side, we will have full support for all Stripe Elements as App Connect components, so you can build your own powerful payment forms.
So as you see - lots of work, but we give you previews to try out as soon as we round up the core.
And yes it will be NodeJS and also PHP
No ASP support
This sounds exciting. Thank you @George! 
Hi @Antony good question. I personally canāt be bothered with Stripe or anything that is āaroundā the core of what I am actually building. Iāve implemented these things in the past, with the popular SaaS du jour. But just because I can do it doesnāt mean I should. Reading docs of every SaaS (and of every major version) for every project these things can quickly start taking most of your time. These services I think are perfect territory for Wappler to focus on. Standardizing procedures (auth, payment, the usual software tasks) for us to build end products fast.
Personally, I want to spend most of my time actually solving the problem at hand for my end users, which is where the actual value of my software is anyways. Payments, auth, etc are just a distraction that waste my time and take time away from my end users that could be spent building a valuable business feature. You might argue that this is a one time setup, but there are hidden costs to hand coding these things. Major version bumps, software changes or goes under and youāre onto your next payment SaaS, etc. As your SaaS grows you also start depending on a dozen services and it wonāt be just Stripe.
I think this is particularly true for one man shows, where you want to be extra selective in where you pour your energy. Itās very easy to get carried away and think that you are being productive by building this nice login flow or that Stripe flow or this cool admin dashboard. I only recommend it if you want to do it for the learning experience, but at the end of the day the only thing that matters to your end users and the reason they pay you money is that your software actually solves their problem.
For Wappler, it makes sense to focus on these things as any new user they onboard will be delighted that they donāt have to implement this stuff anymore. But not for me: I have 0 incentive to write one line of code for a login or a Stripe integration. After all, this is supposed to be the Wappler forum, where weāre supposed to be focused on getting our products out the door fast, right?
i found a stripe.js (in lib/modules/) file in one of our Wappler projects! itās already there and we donāt know it!?
Probably some partial functionality is available without the UI. Happens constantly with the weekly releases. If you check carefully with each update through your GIT repo you can catch what they are working on 
See mine and Gerogeās posts above, Stripe will be developed in to a full server connect module later on in addition to the front end components to start with.