cpaschen wrote: Thanks for that link.
I read the description of the extension and they say it uses the 'redirect' function of Stripe.
I've never seen any stripe payment gateway that uses a re-direct. One of the advantages of Stripe is that you don't have to have that re-direct (like paypal). I think these developers missed a key feature of Stripe.

So we'll probably continue to pursue a more 'proper' use of stripe gateway as an option for our needs and possibly others here.

You can ask that developer to make the changes - I believe you can actually sponsor the development.

AlexRag wrote: Hi Nick,

You had mentioned in an earlier reply to this thread that you may have developers that you could recommend. Could you send me the info so I can also explore options?

Thanks!

I gave the developers site in previous response.

Considering that Stripe is now as prevalent as PayPal I'm disappointed that Stripe is not included with CB Subs out-of-the-box.

Because it's just not that simple. PayPal it's 1 API request and you're done. Stripe you need 5-6. You need to create the Customer, the Plan, the Subscription, then charge it. What's worse is all of this needs to be kept track of. The Customer ID needs to be stored and matched to the user for reuse otherwise you'd be generating duplicate customers on every purchase in Stripe, which isn't clear if that's ok or not. Their convoluted API is what stops this from being a possibility. I don't have months of time to give up trying to figure out their API and how we're going to handle it in CBSubs, which was designed for PayPal (the database structure of payments is modeled after PayPal). If their API was simpler then we'd have Stripe already, but as is I do not have the time for it. With all of that said we still do have a feature ticket to implement a Stripe gateway; I just have no idea as to when.

For anyone trying to implement this my best suggestion is to create a database table to link customer id with user_id. Next when create plans generate them with an id that's predictable (e.g. cbsubsPLAN_ID_HERE) so they can easily be recalled. The plans may need to be unique per user though. From there you should finally be able to make the HTTP request to create the subscription and store its ID to the basket.