Cherry

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
 

Well done ...
When i finish testing and tweaking my plugin and release it , maybe we can merge the two plugins .

Blesta: Janitor
Small Blesta plugin to automate cleaning of abandoned orders, invoices, and services.
 
Installation
Download the latest release version from our releases and then simply upload the janitor folder to ~/plugins directory on your Blesta installation.
 
How it Works:
Janitor creates two cron entries which can be configured both by the cron settings and by the direct plugin settings. All of the plugin’s settings are based on the time the order was created. It may be important that you not cleanup and cancel at the same interval if you expect the orders to be marked as cancelled for any amount of time.
 
Both cron tasks will never cleanup any orders or services which meeting the following criteria:
 
The order’s invoice has any amount paid towards it.
The order’s service is active or already cancelled.
The order’s invoice is completely paid and is already closed (database: invoices.invoice_date_closed)
Cron Task: Cancel Abandoned Orders
This task is designed to strictly check for open orders which have never had any payments attached to them. First, the task will cancel the order and then next, it will void the invoice with a message as described in the language file. This cron task will also cancel any services attached to the order. This part of the cron intentionally leaves orders, invoices, and services in the database, in the possible event of this data being used by sales automation, etc.
 
Cleanup Order Database
This task is designed to completely delete all related database entries related to the order. It will remove the orders database entry, the order_services entry, and provides you the option to either leave the services as marked cancelled, or completely delete the service from the database via the plugins options. Only canceled services will be deleted if this option is set. If the service on this task is any other status than canceled, as set in the ‘Cancel Abandoned Orders’ cron task, it will ignore the service entirely.
 
Download: https://github.com/nodecraft/janitor/releases
Issues/feature requests: https://github.com/nodecraft/janitor/issues

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
 

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.

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
 

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
 

Merci awesome gateway edit mate.

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
 

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.

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.