Stripe

Not to throw a wrench into this discussion, but is the Square gateway ( squareup.com/ ) API better suited for CBSubs structure? Square is another up an coming option that had picked up momentum as much as Stripe and recently became a option in OpenCart.

Honestly for me any affordable (modest fees) gateway besides PayPal is preferred.

AlexRag wrote: Not to throw a wrench into this discussion, but is the Square gateway ( squareup.com/ ) API better suited for CBSubs structure? Square is another up an coming option that had picked up momentum as much as Stripe and recently became a option in OpenCart.

Honestly for me any affordable (modest fees) gateway besides PayPal is preferred.

Nope, they follow same API structure as Stripe with Customer objects. Single payments for Stripe should be relatively easy for me to implement. Recurring will not be in the first release and could be awhile before I implement recurring for Stripe. We'll see how single payments go and build from there. We've got a large enough discussion here regarding Stripe so I really don't want to get into discussing yet another gateway when this one hasn't been created yet.

Thanks Kyle. I was just curious if Square was easier, but as you say it's no different than Stripe. Looking forward to seeing how it goes.

krileon wrote: The earliest I can review writing a Stripe gateway is after CB Auto Actions 7.0.0, which hopefully should be done by end of next week. The plan would be to first tackle single payments, testing, stabilizing, and releasing that. Recurring subscriptions would follow in a future release. If that time schedule is acceptable to everyone then I'll put it in place as my next project as their single payment API is simple and straight forward.

Yes - that sounds good to me - thank you!

krileon wrote: That's our biggest issue with developing gateways. They take a significant amount of time causing a lot of lost revenue.. for maybe 1-2 more CBSubs customers. The numbers just don't add up, which is why we often require significant investment to sponsor them, which doesn't really cover cost of maintaining them. We do not charge individually per gateway like other extensions either and are all simply included with your CBSubs subscription.

Basically we're all ears for any suggestions on how to better improve all of this.

Why not split out all the payment gateways from the CB Subs Plans (perhaps for new customers) and charge for them as individual add-ons on an annual basis?

* Customers could then pick and choose which gateways they do or don't want.
* You'd get first hand feedback over which gateways are in demand / being used.
* Ongoing revenue from new customers going forward to off-set initial development and ongoing maintenance costs.
* If the gateways are generating specific income (all new customers would need at least one) this may make them more 'attractive' to develop?

Just my two-penneth for what it worth.

Why not split out all the payment gateways from the CB Subs Plans (perhaps for new customers) and charge for them as individual add-ons on an annual basis?

That's something we've discussed, but we're not quite sure yet if that's the direction we'd like to go. Ideally in that scenario the base cost of CBSubs would go down and gateways beyond the core gateways would cost extra. This seams to be standard practice for other subscription extensions and solutions. It'd be a big change from our current business model so can't really comment on if that's the direction we'll go or not.