Multi-participant registration fails: requires_capture

A pretty simple event registration that allows multiple registrants fails on the final submission and returns this error: Stripe This PaymentIntent's amount could not be updated because it has a status of requires_capture. You may only update the amount of a PaymentIntent with one of the following statuses: requires_payment_method, requires_confirmation, requires_action.

NOTE: In Test/preview mode.

The same form works with PayPal. A very similar registration form for a different event (single registration only) works as expected. Its frustrating that the general form architecture here requires pre-approval of the payment, but so it is.

I have also encountered this error. When a user selects the number of registrants from the dropdown menu at the top of the page, Civi then separates the ticketing section per registrants, e.g. the first page is only for the first registrant, and second for the second registrant, and so on. Stripe then creates a payment intent based on the number selected in the dropdown * the number of tickets entered on the first page.

Example: Someone misses the "Total for **this ** participant" on the first page and wants to buy tickets for 2 people at $50, and puts a 2 in the dropdown and a 2 in the box for $50 on that first page. When they hit "Continue", Stripe pre-authorizes a payment intent for the amount of $100. Then, on the second page, they see the ticket option again, so they enter another 2 tickets at $50 again, rather than 1 ticket for that second participant only. This results in a total of $200, not $100. When Stripe goes to complete this payment, it tries to update the initial payment intent and fails based on the amounts mismatching.

Example 2: Someone selects 2 from the dropdown menu, and correctly enters one ticket per registrant on each of the two pages. However, if they select a ticket for $50 on the first page, and $60 on the second page, the payment intent will again not match. Stripe will have pre-authorized $100 ($50*2), not $110 ($50+$60), and the payment will fail to complete.

Obviously, if a user selects 2 from the dropdown and only enters 1 ticket per page/registrant at the same price level, the amounts match up and it works, but this is not intuitive and has caused confusion for at least half a dozen people who want to register for our event.

mentioned in issue #375 (closed)

Yeh, this isn't working for me either on:

• Drupal
• CiviCRM 5.50.3
• Stripe xt 6.7.6
• Payment shared 1.2.6

Same setup of a simple multi-participant event. The card box appears on the first participant, and pre-authorises. Then after completing a second participant, which also has a fee, and clicking continue, we get the error:

Ping @mattwire

Looking at Stripe's documentation, I don't see how support for multiple participants is possible in the current setup. Unless I'm missing something?

https://stripe.com/docs/payments/intents?intent=payment

After the card is authorized, the PaymentIntent status transitions to requires_capture. To capture the authorized funds, make a PaymentIntent capture request. The total authorized amount is captured by default—you can’t capture more than this.

So we can't pre-authorize for one amount, and then add charges for additional participants.

The card details entry form would have to be moved to the last participant page (which I think would be too complex, thinking about CiviCRM's workflow which allows you to move back and forth and skip participants) or the confirmation page?

However the release notes for the latest version of this extension suggest that it was working?

So we can't pre-authorize for one amount, and then add charges for additional participants.

This is correct.

Agileware Ref: CIVISTRIPE-6

Have confirmed that this bug still exists in Stripe 6.7.7.

Steps to reproduce:

1. Create an Event
2. Set Stripe to be the payment processor
3. Enable the option, Register multiple participants?
4. Open the test-drive URL for the Event
5. Register more than 1 participant for the Event
6. Note that the "Pre-authorization process" notice is shown when registering the 1st participant
7. When registering the 2nd participant there is no such notice
8. Complete the registration process for the multiple participants
9. Confirm the registration
10. CiviCRM redirects back to the initial Event registration page
11. In CiviCRM back-end, 1st participant was recorded as a "Test registration". None of the other participants are recorded at all.

Result, Stripe cannot be used for Events when using the Register multiple participants? option. Payment fails and registration does not complete.

mentioned in issue #381 (closed)

We'd be happy to support this fix with some $$'s ... do you have a rough estimate @mattwire ? Or, perhaps disable the card pre-authorization per #381 (closed) (this would be our preferred route). Thank you!

We'd be interested to know how to support this too, as it's causing some headaches for our events teams.

I do not feel confident enough in the code to make a PR to alter this; but would be happy to offer QA or know if there's anything else we can do to help? @mattwire

Fixed in 6.7.8

closed

changed milestone to %6.7

added bug label

Sorry, I'm not sure this is fixed @mattwire , using 6.7.8 and shared payment 1.2.8

Using the same steps to reproduce, adding additional participants to a paid event, on the final step we are redirected back to the event page and the error message is now:

It works correctly with a single booker.

I'll open a new issue, rather than dredging up this one: #387 (closed)

mentioned in issue #387 (closed)