Cherry

@bdacus01 According to https://stripe.com/docs/security, all you need to really do is use TLS on your origin (https), and only store the card data on Stripe's end. As Blesta only ever stores the last 4 digits when using this module, you should be safe. Our Stripe account is 6+ years old, so we didn't have any additional questionnaires to fill out when we started using this. Could you perhaps send me a copy / screenshot of the questionnaire? 
We actually take a step further in our private implementation, and generate card tokens using stripe.js on our website, and only ever pass these to Blesta, so never transmitting card details to our server. This requires direct edits to Blesta though, which is why it is not a part of this module.

We would LOVE to support Apple Pay with Blesta, but they don't have good support for mixing both Merchant and non-merchant payments. Additionally non-merchant payments are currently required to have a payment notification. Our only option is to require a plugin to be used in addition to the module and that's really not good practice :/

Yes, sorry for the delay. This should now be pulled and 1.0.5 released, which includes the Invoice's ID code in the statement description, rather than the Invoice ID itself.

Yes, sorry for the delay. This should now be pulled and 1.0.5 released, which includes the Invoice's ID code in the statement description, rather than the Invoice ID itself.

Hi there, sorry for the delayed response.
We've tried to replicate your scenario multiple times, but are finding it really difficult to see what you're seeing. We are using test Stripe credentials, and have tested every card at https://stripe.com/docs/testing, which are all returning the expected success, or error codes, with the data being saved as expected. We're honestly not entirely sure what could be causing your issues currently, but suspect that the old data, and mismatch you have now between Blesta and Stripe (after the upgrade process) is the primary cause. 
Until we're able to replicate the issue that you're seeing, you may want to opt to switch back to the official Stripe gateway as provided by the Blesta team, sorry!

Hi there, sorry for the delayed response.
We've tried to replicate your scenario multiple times, but are finding it really difficult to see what you're seeing. We are using test Stripe credentials, and have tested every card at https://stripe.com/docs/testing, which are all returning the expected success, or error codes, with the data being saved as expected. We're honestly not entirely sure what could be causing your issues currently, but suspect that the old data, and mismatch you have now between Blesta and Stripe (after the upgrade process) is the primary cause. 
Until we're able to replicate the issue that you're seeing, you may want to opt to switch back to the official Stripe gateway as provided by the Blesta team, sorry!

@Cherry i have sent a pull request that fix the Invoice ID statement .

This is something we did explore when developing this addon, but came to the conclusion that as Stripe sends this information along to the bank, it's really down to each individual bank if they choose to use it. From our experience, most european banks will display the company name, phone number, URL, and statement description, but this is a lot more rare to see in the US.
It's something we'll definitely consider in a future iteration of the gateway, but have no plans currently. We're always happy to resolve and fix any bugs, but our time is pretty limited when it comes to feature requests, especially those beyond our use case, sorry! Let us know if there's anything else we can assist with, and thanks for using the gateway!

We've pushed 1.0.4 to GitHub, which upgrades the PHP Stripe SDK, and removes invoice IDs from statement descriptors for now. https://github.com/nodecraft/stripe_plus_gateway/releases
We'll look into including the invoice number on statements instead in a future release.

We've pushed 1.0.4 to GitHub, which upgrades the PHP Stripe SDK, and removes invoice IDs from statement descriptors for now. https://github.com/nodecraft/stripe_plus_gateway/releases
We'll look into including the invoice number on statements instead in a future release.

We've pushed 1.0.4 to GitHub, which upgrades the PHP Stripe SDK, and removes invoice IDs from statement descriptors for now. https://github.com/nodecraft/stripe_plus_gateway/releases
We'll look into including the invoice number on statements instead in a future release.

@Paul Thanks for the information. It appears as if `invoiceArrayToAmounts` method within gateway_payments (which is eventually passed down to our gateway) only ever returns the raw `invoice_id` and `amount`, which is all we used. I suppose we could lookup every invoice and get the invoice number instead, but that wouldn't solve the issue from appearing in any other gateways that expose this information to the client, such as via the PayPal form (albeit a little more difficult to find).
We'll push an update shortly to remove the invoice ID from statement descriptors for now until we've investigated a little further. Thanks! 

We have released version 1.0.2 of this gateway today, which patches a small bug that prevented users from making "credit payments", and depositing funds not applicable to any invoice. We also took the opportunity to update the Stripe PHP SDK version, which patches a few issues. Full changelog: https://github.com/nodecraft/stripe_plus_gateway/blob/master/CHANGELOG.md
 
Download the latest version at https://github.com/nodecraft/stripe_plus_gateway/releases

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
 

We have released version 1.0.2 of this gateway today, which patches a small bug that prevented users from making "credit payments", and depositing funds not applicable to any invoice. We also took the opportunity to update the Stripe PHP SDK version, which patches a few issues. Full changelog: https://github.com/nodecraft/stripe_plus_gateway/blob/master/CHANGELOG.md
 
Download the latest version at https://github.com/nodecraft/stripe_plus_gateway/releases

You're not losing your marbles. It's added as a "public note" on the invoice, which can be seen under the collapsible "Notes" section via the "Edit Invoice" UI within Blesta.

We have released version 1.0.2 of this gateway today, which patches a small bug that prevented users from making "credit payments", and depositing funds not applicable to any invoice. We also took the opportunity to update the Stripe PHP SDK version, which patches a few issues. Full changelog: https://github.com/nodecraft/stripe_plus_gateway/blob/master/CHANGELOG.md
 
Download the latest version at https://github.com/nodecraft/stripe_plus_gateway/releases

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
 

Ah, that's right. Thank you for the clarification!

You're not losing your marbles. It's added as a "public note" on the invoice, which can be seen under the collapsible "Notes" section via the "Edit Invoice" UI within Blesta.

We have released version 1.0.2 of this gateway today, which patches a small bug that prevented users from making "credit payments", and depositing funds not applicable to any invoice. We also took the opportunity to update the Stripe PHP SDK version, which patches a few issues. Full changelog: https://github.com/nodecraft/stripe_plus_gateway/blob/master/CHANGELOG.md
 
Download the latest version at https://github.com/nodecraft/stripe_plus_gateway/releases

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.

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.

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