Answers.Body: <p>I see your price set has integer fields for each, presumably so someone can say 'i want 2 of this one and 5 of that one' but that presumably is not collecting you the data about each Participant. If that doesnt matter then yes, set each field to default to 0 (perhaps) and make each required. But if in registering multiple participants you want to know that John's ticket is $500 and Mary's is $2000 then I think you need a price set that is just pure radio buttons (and set as required) then when filling in the form they would enter number of participants, and hence fill in name and price for each one on subsequent windows. hope that is clear. can flesh out if not.</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-04-20T23:51:26.523Z
Answers.Text: derek. thoughts?
Answers.UserDisplayName: petednz - fuzion
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-01-21T18:48:17.913Z
Answers.LastActivityDate: 2016-01-21T18:48:17.913Z
Answers.UserDisplayName: petednz - fuzion
Body: <p>I have a CiviCRM deployment using Pricesets and multiple participants. </p>
  
  <p>Currently, a user is allowed to simply "hit next" without entering any values under the priceset options and register themselves for $0.00. </p>
  
  <p>Would selecting "required" under all the different price-set options address this issue? </p>
  
  <p><a href="https://i.sstatic.net/6HIs4.png" rel="nofollow noreferrer"><img src="https://i.sstatic.net/6HIs4.png" alt="Example of blank event fee form"></a></p>
  
Tags: <registration>
Title: Event Registration - Require Payment
ThreadText: # Event Registration - Require Payment
  
  (Asked by: username_0 on 2016-01-21)
  
  I have a CiviCRM deployment using Pricesets and multiple participants.
  
  Currently, a user is allowed to simply "hit next" without entering any values under the priceset options and register themselves for $0.00.
  
  Would selecting "required" under all the different price-set options address this issue?
  
  [![Example of blank event fee form](https://i.sstatic.net/6HIs4.png)](https://i.sstatic.net/6HIs4.png)
  
  **Tags:** registration
  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2016-01-21. Score: 1
  
  I see your price set has integer fields for each, presumably so someone can say 'i want 2 of this one and 5 of that one' but that presumably is not collecting you the data about each Participant. If that doesnt matter then yes, set each field to default to 0 (perhaps) and make each required. But if in registering multiple participants you want to know that John's ticket is $500 and Mary's is $2000 then I think you need a price set that is just pure radio buttons (and set as required) then when filling in the form they would enter number of participants, and hence fill in name and price for each one on subsequent windows. hope that is clear. can flesh out if not.
  
  > **Comments:**
  > **username_1**: username_0. thoughts?  
  
  ---
  
  