"Pay as you will" ticket level option

[Carl Paulsen]

We'd like to offer a pay-as-you-will event level where users must pay for a ticket/registration, but they choose what they can pay for it. Setting up a level with $0 as the price just lets them purchase tickets at not cost. We'd like to let them choose a non-zero price, and might also want to set a minimum price (e.g. to at least cover processing fees). Is there a way to do this?

[CnP.Support.AM]

In this case, you can create a Level with $0 and enable the Additional Donation option. You can also set the default amount for additional donations and make it mandatory by locking the amount.



However, please note that in case of $0 transaction, we don't offer any payment methods and it will process the transaction as a custom payment type. The Custom Payment type method will be authorized the transaction without sending to BANK. There are no fees associated, as these transactions are not sent to the bank.

[Carl Paulsen]

Thanks for explaining one option. Unfortunately I'm not sure that will work for us for the "pay as you will" option. I posted a related question here (https://forums.clickandpledge.com/fo...vels#post55403) about adding a donation option to this same event. The problem is we want both options for the ticket sales form. We want a ticket level of "pay as you will" (and that should show up as another ticket level so its' not confusing to the user). That option should allow the user to set the price they want to pay for that ticket level but ideally have a minimum price (say $25).

In addition, we want to provide an option for those who can't attend but would still like to make a donation. The donation option ideally would show on the checkout page. The Additional Payments section appears to work for the donation option, but in that case the transaction will only have the additional payment, not a ticket sale. Will that work? And then is there another mechanism to provide a "pay as you will" option?

[CnP.LiveSupport.AB]

Ticket levels require a price - If you want to offer more of a choice, you would just have to have several levels of different prices: $10, $25, $50. A "choose your price" option.

The additional payment feature is primarily what people use for an additional donation option.

I suggest that you have one level at your minimum price, and perhaps change your "Additional Donation" to "Additional Donation Encouraged", and perhaps include language in the event description to promote this aspect. People who are going to go for the minimum they can will, and people who are willing to be generous will.

[Carl Paulsen]

Thanks. Another option I thought of was to set a low ticket price but also tie that to a donation which would have a minimum. So for example have a $10 ticket price but buyers at that price would also have to make an additional donation of $15, making the effective minimum price $25. Is that possible (meaning is it possible t require the additional donation/payment)?

[Carl Paulsen]

I should clarify. I know you said above that we can add a ticket price of $0 and create an additional payment option, set a minimum and lock that. But what I don't yet understand is will that mandatory "donation" be tied to every ticket level or just the $0 one? Is it locked in such a way that the user could increase it (so it becomes a minimum) or is that the only option for all ticket buyers? And can the user opt out of the additional donation for other levels?

[CnP.LiveSupport.AB]

The Additional Payment option works independently of the ticket levels.

Will that mandatory "donation" be tied to every ticket level or just the $0 one?

You can require a certain amount of Attendees to also require the additional payment, but you can't specify which ticket level the Attendees should be from.

Is it locked in such a way that the user could increase it ?

No. "Lock" means the amount is set- there's no way to set a minimum or maximum.

And can the user opt out of the additional donation for other levels?

No, the Additional Payment feature cannot change it's behavior based on different levels. If it's locked, it's locked for everyone. If Attendees are required, that number is based on the total number of Attendees, not the number of attendees in a particular level.

[Carl Paulsen]

OK thanks.