1

I am trying to configure CiviEvent, but have a problem and don't know where to look.

  • I have two test sites, as far as I can see both configured the same. CiviCRM 5.29.1, Stripe 6.5.1. Simple test Event set up.
  • On One site I can configure Events that work OK if not paid for or paid for using credit card with Stripe (with a test card only so far). On the other it works if not paid for, but Stripe fails.
  • When failing it flashes up the 'Wait while Pre-authorising' message, but then returns to the registration page asking to have the card number put in again.
  • When failing the Stripe log shows an Authorised but Uncaptured payment.
  • There are no errors in the Drupal log.

Can anyone suggest anywhere to look that might help find this problem? Thanks.

Improve this question
2
  • I’m voting to close this question because it is purely local to the questioner's site, and has no wider usefulness.
    – user6274
    Oct 11, 2020 at 15:37
  • Since it's your own question, I believe you can just delete it.
    – Jon G - Megaphone Tech
    Oct 11, 2020 at 18:17

2 Answers 2

Reset to default
2

It looks like this is a side-effect of a custom Module we have installed for something else (still related to Events). Consider this question closed.

Improve this answer
1

I would look in your Stripe dashboard at "Events" (found under the "Developer" section of the navigation menu). You're likely to find an event associated with the failure with an error message in its details.

Also, errors on your end are much more likely to be in the CiviCRM log than the Drupal log.

Improve this answer
1
  • The Events contain just the following: A new payment ... was created. An uncaptured payment for £5.00 was created ... The amount_capturable for payment [first reference] was updated I mention Drupal log because I have configured all Civi log messages to be written to Drupal log as well.
    – user6274
    Oct 10, 2020 at 10:59

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge that you have read and understand our privacy policy and code of conduct.