Hot answers tagged

5

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?


4

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


3

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 ...


3

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. ...


3

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 ...


3

This was due to an unused Payment Processor which had no API key. Deleting this Payment Processor fixed the issue.


3

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 ...


3

There's a new requirement listed in the Stripe CiviCRM documentation for version 6.0. You also need the MJWShared extension.


2

If you think the webhook URL is correct and the extension is still printing the error message on the status page and the same is also not getting fixed by Fix Stripe Webhook, make sure - You have correct latest API version set for your webhook. Only a bunch of events are enabled for triggering the webhook instead of "All Events". The events currently ...


2

Hi I can confirm the same behaviour. We are on Drupal 7, CiviCRM 5.19.4 and the problem is that the Billing address profile seems to be ignored for the dedupe rules. You must create a new profile with all fields needed for dedupe rule and include it in page. The billing address name and first name is not used.


2

That looks like a bug in the events component (possibly, specific to Joomla). The error is happening in the constructor of an object that is managing the event registration process (https://github.com/civicrm/civicrm-core/blob/master/CRM/Event/StateMachine/Registration.php), presumably after the payment has occurred. It's failing to get the id of the event, ...


2

After seeing this question Civi 5.9 not serving extension javascript in WP 5 I put an absolute path in the resource URL in Administer > System Settings > Resource URL and the issue was fixed.


2

If the Stripe webhook wizard is creating webhooks with the wrong API version, that's a bug, and should be reported on https://lab.civicrm.org/extensions/stripe/issues. To allay your concerns - it's very unlikely that you're going to experience any ill effects from this. The check in question is mostly concerned with folks running older versions of the ...


2

Go to your System Status page and check for any stripe warnings In particular look for any notices about Stripe webhooks that might need resetting. Also ensure you are on latest versions.


2

April 21: The issue appears to be related to Stripe. The submit button is generating a couple of ajax calls to the stripe url as: https://q.stripe.com/?event=elements.event.focus&event_count=12&timestamp=1587498851543& ... https://q.stripe.com/?event=elements.event.blur&event_count=13&timestamp=1587498851574& .... After that first ...


1

You can use the Stripe element events to trigger something - see https://stripe.com/docs/js/element/events We do that in the Stripe extension here: https://lab.civicrm.org/extensions/stripe/-/blob/master/js/civicrm_stripe.js#L281 There are some useful CiviCRM/Stripe extension events which help with frontend integrations and we are open to adding more: ...


1

Problem turned out to be js conflicts with Themefy popup messing up the js files in civicrm. Disabling the plugin from /wp-admin/plugins.php?plugin_status=all&paged=1&s removes this problem and contributions go through to Stripe as intended


1

Just needed to refresh the cache.


1

The Stripe development team has upgraded the code of the extension to support the new API that is PCI compliant.


Only top voted, non community-wiki answers of a minimum length are eligible