The state of the plugin

[sebastian-zarzycki-apzumi]

I would like to inquire about the status of Stripe plugin for Cordova, that you’re apparently the author of.

From what I can see it supports only a small portion of Stripe API (no payment methods, no recurring payments, etc.) and it also doesn’t (?) support Strong Customer Authentication.

Do you have any plans in near future to update the plugin to be up to date with current Stripe API?

[ihadeed]

Hi @sebastian-zarzycki-es

The current stable version covers basic use cases such as tokenizing payment methods and validating payment method information.

The beta version in the v2 branch includes an updated mobile SDK (needs another update) and it aims to provide access to all the functionality that the Stripe Android and iOS SDKs offer. The beta version is currently under active development and testing and I will be releasing an update in the next few days.

The only thing I might leave out is the UI helpers. I will test them to see how well they play, and if any needed customization can be easily wrapped. This will most likely happen after releasing a stable v2 release.

---

This plugin provides client-side functionality only

Features like Charges, Payment Methods, Recurring Payments are part of the Server API and will always be out of the scope of this project.

Handling server side operations require the secret key to function; therefore it's insecure to run them on the client side and is definitely not recommended.

---From what I can see it supports only a small portion of Stripe API (no payment methods, no recurring payments, etc.) and it also doesn’t (?) support Strong Customer Authentication.

[sebastian-zarzycki-apzumi]

Thanks for the update, but I have follow up notes:

• you say beta version is in active development, yet the last commit to that branch happened 7 months ago. Are you saying that you work on (and test) a much newer code, that just didn't find its place in repo?
• I'm well aware about the distinction between clientside and serverside Stripe. Payment Methods is actually a client side functionality, as well as managing payment and setup intents.
• what about SCA? This should be handled externally by Stripe, but I'm not entirely sure, if it requires additional changes in your lib or not. Since this is a mandatory change, that will go live in September 2019, it's extremely important to communicate this properly.

[ihadeed]

• Yes, we're just testing it alongside an application that's in development. I'll push them to the repo once I verify the whole e2e flow works well.
• I'll look into Payment Methods to see if there is something that we're missing.
• I didn't look too deep into SCA since in our internal applications we don't process any payments in the EU. It seems that as long as 3DS is implemented it would meet the requirements. Do let me know if there is something else that's required and I'll be happy to look into it.

[phiferd]

@ihadeed Also looking forward to this update. If you have changes that get closer to getting Google pay working or resolve any other issues, it would be great if you would push them to the v2 branch (see #54 (comment) for the bug).

I get that you are still testing, but maybe others (like me) could send a PR to fix any remaining issues. As it is, it doesn't make sense for anyone to jump in knowing that the code in the v2 branch is potentially 7 months behind your local. If you're really worried about it, you can push to a new branch, like v2-pre-alpha-this-is-not-done. :)

[vicmarcal]

Which is the status of the "beta" version and hence the "state" of the plugin?

[sboudouk]

Any news guys ? :)

[lyngbach]

It would be nice with another update. Just to hear if the development is ongoing or completely stopped. At this point it feels its come to a complete halt.