Support

Home Forums Event Espresso Premium Specify which registrant's email is passed to Stripe

Specify which registrant's email is passed to Stripe

Posted: April 25, 2018 at 8:34 am


runforamy

April 25, 2018 at 8:34 am

Hi there,

The issue we have is when the primary registrant – i.e. first on the list is not the person who will be paying – they are further down the list as on a different ticket type.

– Our event is a race with multiple ticket types – 5k adult, 5k child, 10k adult… and so on

– If I register multiple people at one time (my husband and daughter for the 5K, myself for the 10K, then two kids for the 5K child) then the first registrants are my husband and daughter for the 5K, the next one is me for the 10K then the kids… I go to checkout with Stripe and Stripe shows the email of the first registrant who in this case is not the person who is paying for the registration – I am. I am the third registrant, as I am running the 10K. I am doing the family registration and will be paying. Stripe should be getting my email (third registrant) otherwise it will be confusing if the wrong person gets the receipt. The payer could be anywhere in the order depending on which ticket type they are signing themselves up for.

How can I change this?

Can I select which entrant/registrant should be the primary/payer? A checkbox would work “Primary registrant – This email will receive the payment receipt”

Or can I prevent Stripe from getting the email passed and instead have the user re-enter their email in the Stripe payment window? To make sure the right person gets the receipt.

Thanks,

Alice


Josh

  • Support Staff

April 26, 2018 at 10:13 am

Hi Alice,

You can prevent Stripe from getting the email passed and instead have the user re-enter their email in the Stripe payment window by adding this code to a functions file on your website:

https://gist.github.com/joshfeck/549eb2869a28c675405305dd69ce583a

You can add the above to a functions plugin, then activate the plugin.


runforamy

April 26, 2018 at 11:05 am

Thanks Josh. This is just what I needed. Testing it now.


runforamy

April 26, 2018 at 11:34 am

Hi Josh,

What do you think about adding a checkbox so the user can identify the primary registrant?

Looking at our test registrations the primary registrant as identified by EE is not necessarily the person doing the registration and paying. This is because a parent may register mulitple kids for a race distance higher up the list of ticket types than the distance they are entering. EE currently identifies the first registrant in list order as the primary registrant.

The function you shared above gets around the issue with Stripe getting the wrong email. Thank you! However, looking at the test registrants in the EE backend I see kids being marked as the primary and it would be great for our record keeping if we had the right primary registrant marked for each group registration.

Is it possible to add this?

Thanks,

Alice


runforamy

April 26, 2018 at 11:38 am

I’d also like to make use of the option to ask certain questions only of the primary registrant and if I can get the user to identify themselves with a checkbox then those questions could appear for just that person. We would ask:

– buy extra event merchandise?
– make optional extra donation?
– mailing address

Right now we have the first two questions for all registrants but the question really only needs to be asked once – to the person doing the registration and paying.


Josh

  • Support Staff

April 26, 2018 at 11:44 am

I’m afraid there isn’t a way to add something to specify which ticket is for the primary attendee. This is an issue that the dev team is aware of and they’ve put some work into adding a “purchasing agent” section of the form that could be used for capturing information related more to billing info than attendee info.


runforamy

May 1, 2018 at 11:52 am

The way to found to go around this was to create a new ticket that is first on the list in order and required with a max of 1 per session. I called this ticket “primary registrant info” and hid it from the ticket selector using CSS.

Users see the other (“real”) ticket options and make their choice. On the next screen they are first asked the questions I want asked of the primary registrant. I have to ask name, email but then I ask the one-time donation, extra merchandise etc. questions.

Below that they see the actual ticket choices and they can prepopulate the info if it’s just the one attendee – this also works for children who are all on the same parent’s email. The questions I ask of the additional registrants are specific to that individual ticket (race entry) tshirt size, agree to waiver etc.

Stripe gets the primary registrant email which is great as that avoids the problem with the first registrant potentially not being the person making the payment and their email going to stripe instead of the person doing the registration. This was happening when one user was signing up a few people but signing themselves up for a ticket further down the list in order than the first person they added (who previously became the primary registrant).

Another plus is that a parent can sign up the family, pay and get all the email info, but not register for a race event – for example if they are injured.

The only downside is that I have to be aware of what looks like duplicate registrations when looking at the registrations page, where the primary registrant also gets a race ticket but I reckon I can use the search feature to just show 5K entries or, if I need to just primary registrants. I will also have to do some sorting in the final csv export.

With messages I set it so that only the primary registrant gets emails as that person was getting multiple emails if they registered 4 kids on their email address and each registrant got an email confirming sign up.

We plan to use EE again next year so I would like to see what changes are made re. primary registrant handling.

Thanks for your help and let me know if you see any major downsides to this roundabout approach.


Josh

  • Support Staff

May 4, 2018 at 1:59 pm

I think you’ve covered the downsides in your update.

The support post ‘Specify which registrant's email is passed to Stripe’ is closed to new replies.

Have a question about this support post? Create a new support post in our support forums and include a link to this existing support post so we can help you.

Event Espresso