Getting your site back online, in phpmyadmin:
In table civicrm_extension, enable stripe (change 0 to 1)
In table payment_processor, disable any using stripe (change 1 to 0)
This should allow your site to load.
Deleting stripe (warning: stripe may be related to some transactions, check before doing this):
Make sure none of your donation pages are using ...
I think the new version tries to create the webhook automatically. Maybe if it already exists in the Stripe account it can't create it -- have you tried deleting the webhooks in the Stripe account and then using the "Fix Stripe Webhook" (civicrm/stripe/fix-webhook) page in CiviCRM to regenerate it?
As promised, here are our experiences with Stripe Version 1.9.1 | CiviCRM 4.6.8 | Drupal 7:
We are using it on CiviCRM contribution pages for memberships
In order for the pay later option to work we needed to fix an issue
Afaik the fix has not been integrated with the Stripe master branch - our version can been found here.
Apart from the pay later problem ...
We use Stripe with CiviCRM 4.6.4 on Drupal 7's latest rev and are not having issues. We grabbed the latest Civi Stripe library from github.
So far we have only processed event registrations, not membership payments or other contributions. We haven't tried processing payments via WebForms, only regular civicrm event registration pages.
We had one ...
We are using Stripe with 4.4.14 and had problems accepting payments for memberships using a webform. With investigation though, our developer installed a version of Stripe 1.9.1 from the github and the latest dev build of webform and it is now working for us.
Whether anything within 4.5/4.6 has changed to make our experience irrelevant, that I can not ...
I would follow the instructions on screen:
Log in to your Stripe account, go to the Webhooks section
Delete the existing webhook (on live and testing sides)
Come back to CiviCRM and use the "Update/Create Webhook" button
There is a long thread at https://github.com/drastik/com.drastikbydesign.stripe/issues/76 on this issue. It was for earlier versions but might give you some clues. I have a site using Stripe successfully with webforms on Civi 4.6
Many of these "lost session" issues (which stem mainly from redirect_canonical correcting CiviCRM's malformed URLs) are solved in more recent versions of CiviCRM. All I can really do is suggest you upgrade. FWIW, you can pick through the PRs that deal with URLs here:
The answer is that I had pasted one of the Stripe API keys with a trailing blank, so when I looked at Firefox's web developer console there was a message 'Your key is invalid as it contains whitespace' Working consistently now, but how I previous managed to make a couple of contributions successfully I don't understand!
You would need to reach out to Paypal and Stripe directly to ask them about how to initiate the process of transferring your recurring giving. I would suggest inventorying your existing recurring records in Paypal first, to see how complex the data is; in a recent transition to Stripe, we encountered some challenges with constituents who had multiple ...
I believe this is correct behaviour.
The flow with Stripe is slightly opaque due to the complexity of maintaining a level of PCI compliance while using a CiviCRM form for payment.
The credit card part of the form is actually an iframe hosted with Stripe (that's what allows for the PCI compliance trick), which will take the credentials and test them by ...
The most common approach to reconciliation is to update contributions within the CRM with the identifier from the payment processor. For Stripe we have a few approaches, our most recent is the payout reference from Stripe is automatically pulled back into CiviCRM. This allows the finance departments to run a payout report from both systems and reconcile. ...
In general, auto-recurring memberships are generated via an auto-recurring payment, whose mechanism depends on the payment processor, and most especially on whether the recurring payment schedule is managed by CiviCRM or the processor.
When the schedule is managed by CiviCRM, you have more direct control and could for example use some sql to just push ...
This seems to be a long-standing issue with the Stripe processor, and from what I can tell (and from what I have experienced), in some cases this extension doesn't play well with other payment processors (including the "pay later" option).
Try disabling Paypal (and Pay Later, if applicable) and then test Stripe again.
You can not use the checkout option for stripe if you are using it with CiviCRM.
As far as I'm concerned, you can use only direct payment option in stripe while making payment in CiviCRM.
Please refer a function doTransferCheckout() from link: https://github.com/drastik/com.drastikbydesign.stripe/blob/4.6-dev/CRM/Core/Payment/Stripe.php#L665
it says, ...
Have you looked at this extension: Stripe Payment Processor?
I haven't used it myself so perhaps others can comment on how well it works.
There is also this related post: Has anyone tried Stripe payments through OmniPay?
It was a Stripe Payment Extension issue. I thought I was on the latest version but must have been a few commits back. Updating the files to the latest 4.6-dev version and then visiting the Manage Extensions page to run database updates was all I needed.