Support

December 14, 2022 at 5:40 am

Hi there,

Is it possible to add Billing Fields to the checkout/payment portion of the process. I’d rather not ask it with the Attendee information section if that’s possible.

Are you wanting to start that information?

That section is controlled by the selected payment method and the details entered there are not saved within the registration itself (those need to be done within the attendee information step).

Is it also possible to rename certain sections in the process. IE: on the Expresso_My_Events shortcode, where it says “My Registrations.”

Do you mean ‘Your Registrations’?

Pretty much all of the strings within Event Espresso can be translated, so essentially all strings can be changed if needed.

If yo let me know the changes you’d like to make I’ll check and confirm the best way to do it with what is available.

December 15, 2022 at 3:26 am

I’d rather end with the billing information, if possible.

My apologies, auto-correct ‘fixed’ my question there:

Are you wanting to start that information?

Should have been

Are you wanting to store that information?

Just be careful with what info you are storing here, billing information covers a lot could change at least your PCI compliance requirements.

And yes, Your Registrations.

So you just want to change ‘Your Registrations’, what to? I’ll creat a snippet to do this for you.

Is it possible to condense the whole checkout, as well? Possibly into one page? If not, that’s fine. Trying to reduce the amount of clicks the user needs to do.

Not currently, no, your would basically need your own custom checkout process for this, which leads to your next question:

Do you guys offer custom development or have a preferred provider?

At this time we don’t have the capacity to undertake any customizations services but we do have some developers who are familiar with working on Event Espresso listed here:

https://eventespresso.com/developers/event-espresso-pros/

A little heads up on this though, altering the checkout process to do the above is not a small task.

I’m seeing now that as I’m choosing the Stripe option, it again asks for my Billing Information even though I’ve filled it out on the Registration page. Is it possible to ask for this information with the Invoice option and then I wouldn’t have to ask for this information on the Registration page?

The registration questions are separate, they are designed to be the questions asked specifically for the registration itself.

The billing info questions are asked by the payment methods themselves (in your case Stripe) and are used for the specific payment request required to process the payment side of things. In short, the billing info questions asked on the payment options are completely separate from the registration questions and aren’t stored with the registration, some payment methods store some info within the transaction but it depends on the payment method itself.

The Invoice payment option does not request any info so to request billing information on that step you would need to create your own custom Invoice payment method which could be used to request those details and then you could save them to wherever you prefer during processing.

I’m also receiving a registration timeout. Is that something that’s set on the backend?

There are a few different possible timeouts, how long for the timeout and what is the error message shown, please?

December 15, 2022 at 7:44 am

So, there’s no way of collecting that billing information, for invoicing, on that payment options page?

No, because Event Espresso considers the Primary Registrant to be the registrant handling payments. Meaning that info would be collected on the registration form in the way it’s currently designed to work.

When I say that to other users, the next question is why the payment options step then ask for the same questions…. the short answer is it doesn’t. Some payment methods require specific questions to be asked for the payment request to process, others require additional questions, and others require none and just the card details. So the payment options step allows the payment method to load and request its own required details. Those don’t ‘need’ to match the primary registrant, so the payment works if they differ, but EE still considers the Primary Registrant to be the one handling everything to do with the payment across the group, regardless of the actual details used for the payment itself.

I don’t want Stripe users to have to input that information twice, so if there was conditional logic I could use, that would be wonderful. I’m trying to think of how to work around this.

Are you not collecting that info using the system Address question group?

The payment form automatically fills in the address question using the system question if info is provided in those.

The timeout occurred on the payment options page; I can’t recall off of the top of my head what it said. I’ll keep you posted the next time I see it.

The most common timeout is session expiry, by default it’s 1 hour from when you start your ticket submission. Whilst the session lifespan ‘can’ be extended I highly recommend you don’t, it affects multiple different functions such as the reservation system which then means tickets are ‘reserved’ for longer than expected.