For most of the clients I've worked with (and those I've talked with at our JUG) people are only using cards for online payments (at least here in the US), so just supporting all the CCards would be great for us here.

All the card methods that Stripe supports have all been tested working. I've also implemented both of their payment APIs. You can use Checkout (popup form) or Elements (inline form) methods as desired. Default is Elements as it seamlessly fits within CBSubs.

Stripe is officially done (single payments only). We've some final review and install testing to do, but should be released sometime this week if no issues.

Also - can you give details on sponsoring the recurring part?
I have a client that will need recurring and is willing to sponsor.

You'll need to contact us privately regarding sponsoring recurring payments. However it's a time issue more than anything. I've already paused all development to push single payment Stripe gateway as quickly as possible. Single payments are very easy to implement API wise. It's a simple charge API call with a source. Subscriptions are different. Subscriptions require a Customer, Plan, and Subscription object. Believe CBSubs can get away with just tracking the Subscription ID, but it's a lot more complicated dealing with recurring payments and are often the reason gateways are expensive to develop.

Stripe is officially released. You can download it below.

www.joomlapolis.com/downloads/cb-paid-subscriptions

Please be sure to also update CBSubs as the Stripe gateway required some changes to CBSubs API.

Ok, have went through and fixed several of our gateways. I'm now back to Stripe to reviewing recurring payments. Please note this is not a guarantee, but will be trying to implement recurring payments for Stripe and will see how it goes. Feedback on existing single payments implement greatly welcomed.

Recurring payments officially implemented. Changes are under review to be merged and released in a future CBSubs build. Customer handling, plan handling, and subscription handling all implemented. Webhooks are supported, but not mandatory and if not present will use CBSubs scheduler to check for recurring payment status. Note as with all recurring there is often a delay so a 1 day grace period or at minimum 3 hour grace period is highly recommended.

To avoid tons and tons of duplicate plans at stripe plans will be generated at stripe from price, currency, duration, and plan id. This allows them to be reused for multiple subscription records to prevent bloating your Stripe account with a plan per basket, which was originally being implemented. Customer objects can now also be optionally enabled for single payments if you want to attach single payments to Stripe customers as well.

I've also fixed the extremely slow HTTP requests as it was due to our API using HTTP 1.1 while Stripe is HTTP 1.0. Since CBSubs API has been improved to use either/or payments are not basically instant instead of taking roughly 30 seconds to a minute.