Leaderboard

Blesta: Stripe (plus) Gateway Forked version of the original Stripe gateway which includes updated offsite storage and ACH payments. Some of the feature/bug requests this updated gateway resolves are listed below: http://www.blesta.com/forums/index.php?/topic/6224-latest-stripe-api-with-blesta-361/ http://www.blesta.com/forums/index.php?/topic/6089-stripe-invoice-number-in-description/ http://www.blesta.com/forums/index.php?/topic/5812-stripe-ach/ http://www.blesta.com/forums/index.php?/topic/5760-stripe-error-401-when-customer-attempts-charge/ Installation Download the latest release version from https://github.com/nodecraft/stripe_plus_gateway/releases and then simply upload the stripe_plus_gateway folder to ~/components/gateways/merchant directory on your Blesta installation. Feature changes from Original Gateway This gateway has been rewritten from the original version which was distributed with Blesta. The major changes are as follows: Only creates one Stripe Customer per Client Contact, rather than one Stripe Customer per Credit Card Only supports offsite card storage, onsite storage is removed Supports ACH payments* Updated Stripe API PHP SDK to version 3.14.2 Utilizes Stripe API Version 2016-06-15 Adds API key environment selection (test vs live) Updated Currency list to Stripe Documentation Does not utilize Blesta's $client_reference_id lookup to Stripe customer ID. This can cause multiple customer accounts if the user deletes all payment methods. Uses added MySQL table stripe_plus_meta Pros: Prevents your Stripe account from having "dead" data by attaching one customer per payment source. This enhances your ability to fight fraud. Added security by preventing payment source information from being stored locally Cons: *ACH Payments by Stripe require "verification" before payments are accepted. Blesta does not provide any methods for this process to take place. You will need to manually verify the bank account with your customer until this is improved or a plugin created. Roadmap: Add ACH verification if Blesta implements methods on Gateway Download: https://github.com/nodecraft/stripe_plus_gateway Issues/feature requests: https://github.com/nodecraft/stripe_plus_gateway/issues

That's known, and fixed in the CORE version in CORE-1877

We've been working on a fork of the original Stripe module shipped with Blesta, as can be seen here: https://github.com/nodecraft/stripe_plus_gateway. Our primary goals are to support new Stripe features, and better complement Stripe's recommendations to its customers. One of the primary new features that Stripe now supports is ACH payments. We've already implemented ACH payments into our forked module, however unfortunately, Stripe's ACH verification process requires additional steps not currently supported by Blesta natively. When adding an ACH account to a Stripe account, Stripe makes two micro-deposits by default, which the customer is then required to enter after they've cleared. This is in order to verify their bank account details. Stripe provides the functionality via their API to then verify and match those amounts automatically for customers and without a plugin, Blesta would be unable to provide this verification process for it's users. https://stripe.com/docs/ach#manually-collecting-and-verifying-bank-accounts This can be worked around of course by contacting the customer, and then having an agent manually verify the micro-deposits via Stripe's UI, but having this available via Blesta would be much more ideal, and allow customers to add ACH accounts via Stripe, without any need of talking to a representative of the company. You can read more about ACH via their docs: https://stripe.com/docs/ach If any further information is required, don't hesitate to let us know and we'll be happy to assist in any way that we can.

Merci awesome gateway edit mate.

Thanks. We've made a separate post about the gateway (found here). This post was primarily for the ACH verification feature request, so we can improve this gateway further in the future.

Ah missed that one Thanks

The way he said it is totally inappropriate and lacks respect, but shunning him for an opinion isn't right I have a fairly large commitment towards Blesta (addon companies), but I can't actually use Blesta for what I need it to do. Do I want to use Blesta? YES. But right now, I'm stuck using WHMCS because of core components that Blesta will not get to until 4.1 at least. The reason I can't use Blesta? Because it would take a lot more money to customize it and bring it up to speed, than it would be to simply use a competing product. And even then, it wouldn't be 100% Let's be honest here guys, the development of Blesta is pretty slow. I'm not sure if the hope was that 3rd party developers would take up the slack, but there's been a really big mis-read on what your customers are using Blesta for, and what you think they should be using Blesta for. I think WHMCS got their act together security-wise, finally. But I don't like their company, I don't like how cPanel runs things either (but use them for server software... because cPanel). I really like Blesta, I met the Blesta guys at multiple Hostingcons, great guys, but Blesta needs to kick it up a notch if it wants to grow and put a dent in competitors' market-share. I'm still rooting for Blesta, i haven't sold my license, and still pay for updates even if I don't use it. But I wish Blesta would really start focusing on what customers want to use Blesta for, how they use it, how many clicks it takes to get to something, intuitiveness, along with a whole bunch of other things, and start moving development resources towards those pain points first, and worrying a lot less about ancillary stuff. Maybe even provide smaller, quicker updates. When a new feature is built and tested, ship it out. Stop waiting 3+ months to make bigger splashes with releases. You're a smaller company, who should be much nimbler than your bigger competitors. Use that to your advantage. You have the ability to pivot quickly and release things nearly as fast. I don't know why you don't do it. Like someone once told me, it's fine to give out ideas and roadmaps about where you're going. It's the execution that counts, and few people can do that part well.