described herein are techniques to provide event ticket pricing based on one or more conditions . in one particular example , an event may be a spectator event such as , for example , a sporting event ( such as , for example , baseball , football , hockey , basketball , volleyball , soccer and so forth ), a play , a musical , a concert and so forth . referring to fig1 a , a system 100 is an example of a system to provide event ticket pricing based on a condition . the system 100 includes a ticket provider system 102 and a user computer 104 . the ticket provider system 102 receives a request for ticket ( s ) from a user ( e . g ., a ticket buyer ) using the user computer 104 and provides the user computer 104 with ticket option ( s ) that includes at least one condition . after receiving a selection of ticket option from the user using the user computer 104 , the ticket provider system 102 determines if the condition was met and the ticket provider system 102 enables a refund to the user if the condition was met . in one example , the user computer 104 may be a personal computer , a smartphone , a personal digital assistant and so forth . in one example , the ticket provider system 102 provides a website which may be accessed by the user computer 104 using , for example , the internet . referring to fig1 b , a system 100 ′ is another example of a system to provide event ticket pricing based on a condition . the system 100 ′ includes a ticket provider system 102 ′, the user computer 104 and a condition pricing provider system 108 . the condition pricing provider system 108 provides pricing based on a condition . in one example , the ticket provider system 102 ′ provides pricing on the ticket options ( s ) based on the pricing provided by the condition pricing provider system 108 . in one particular example , the condition pricing provider system 108 provides insurance to the ticket provider system 102 ′ for each condition . referring to fig2 , a process 200 is an example of a process to provide event ticket pricing based on a condition . process 200 receives a ticket query ( 204 ). for example , a user , using the user computer 104 , sends a search query for ticket ( s ) to a spectator event on a website provided by the ticket provider system 104 . in one example , a ticket query may include a query for one or more tickets . in one particular example , the ticket query may include all or a portion of season tickets . process 200 generates ticket option including refund ( s ) based on condition ( s ) ( 208 ). for example , a ticket option may include a date of the spectator event , location of the seat and price of ticket . in one example , for a sporting event , the ticket option may include teams playing . in one example , for a music event , the ticket option may include the artist ( s ). in other examples , the ticket option includes a condition and a refund action if the condition occurs . for example , a ticket option for a baseball game may indicate that if the home team loses by five runs or more , the user will receive 50 % of the ticket price back . in another example , a ticket option for a baseball game may indicate that if the home team is shutout , the user will receive 40 % of the ticket price back . in further example , a ticket option for a baseball game may include that if the temperature is below a specified temperature the user will receive 30 % of the ticket price back . in a further example , a ticket option for a baseball game where the home team loses after leading by 3 runs or more in the 7 th inning or later . in a still further example , a ticket option for a baseball game may include that if a specified player does not play , the user will receive 20 % of the ticket price back . in other examples , a ticket option may include conditions that may occur before the spectator event . in one particular example , the condition may be a number of games won by a home team at a specified point in the season or what place a home team is in team standing at a specified point in a season . in further examples , a ticket option may include more than one condition . for example , a ticket option for a baseball game may indicate that if the home team is shutout and the home team loses by five runs or more the user will receive 60 % of the ticket price back . process 200 sends the ticket option ( 210 ). for example , the ticket option is sent electronically using for example , a webpage generated by the ticket provider system 102 . process 200 receives the ticket selection ( 212 ). for example , the user selects a ticket option by entering a ticket option using the user computer 104 on a webpage provided by the ticket provider system 102 and purchases the ticket ( s ). process 200 enables user to receive ticket ( s ) ( 214 ). for example , the ticket provider system 102 delivers tickets electronically or physically to the user . process 200 receives data related to the condition ( s ) ( 216 ). for example , the ticket provider system 102 receives data on the spectator event related to the condition in the ticket option selected by the user . in one particular example , a website at the ticket provider system 102 receives data electronically and automatically on the results of a game and / or other conditions ( e . g ., temperature ). in another particular example , the data from the spectator event is entered manually using a graphical user interface ( gui ) on the ticket provider system 102 . in one example , the data related to the condition ( s ) may be received by the ticket provider system 102 during or after the spectator event . in another example , the data related to the condition ( s ) may be received by the ticket provider system 102 before the spectator event . process 200 determines if condition ( s ) was met ( 222 ). for example , the ticket provider system 102 determines if the condition has been met . if the condition ( s ) was met , process 200 enables refund ( 226 ). for example , the ticket provider system 102 enables payment to the user by check , electronic funds transfer , credit card refund or giving credit based on the refund in the ticket option selected . referring to fig3 , a system 300 is an example of a system to provide event ticket pricing based on a condition to ticket sellers to offer to ticket buyers . for example , a ticket buyer may be able to offer a guarantee in selling a ticket based on a condition . the system 300 includes a guarantee pricing provider system 302 , a ticket seller computer 304 and a ticket buyer computer 306 . the guarantee pricing provider system 302 provides tickets being sold by a ticket seller computer with a refund if a condition ( s ) is met . in one example , the ticket seller computer 304 and the ticket buyer computer 306 may be a personal computer , a smartphone , a personal digital assistant and so forth . in one example , the guarantee pricing provider system 302 provides a website which may be accessed by the ticket buyer computer 304 and the ticker seller computer 106 using , for example , the internet . referring to fig4 , a process 400 is an example of a process to provide event ticket pricing based on a condition to ticket sellers to offer to ticket buyers . process 400 receives notification of tickets to be sold ( 404 ). for example , the ticket seller using the ticket seller computer 304 notifies the guarantee pricing provider system 302 of tickets to sell . in one example , tickets to be sold may include one or more tickets . in one particular example , the ticket to be sold may include all or a portion of season tickets . process 400 generates a price of a guarantee for each ticket based on conditions ( 408 ). in one example , the guarantee pricing provider system 302 performs calculations to determine an appropriate price for a guarantee . for example , a price of a guarantee may include a price to refund a ticket and the amount or percentage to refund the ticket buyer if the condition is met . for example , a price of a guarantee for a baseball game may be a price for a refund of 50 % of the ticket price to the ticket buyer if the home team loses by more than five runs . in another example , a price of guarantee for a baseball game may be a price for a refund of 40 % of the ticket price to the ticket buyer if the home team is shutout . in further example , a price of guarantee for a baseball game may be a price for a refund of 30 % of the ticket price to the ticket buyer if the temperature is below a specified temperature . in a still further example , a price of guarantee for a baseball game may be a price for a refund of 20 % of the ticket price to the ticket buyer if a specified player does not play . in other examples , a ticket option may include conditions that may occur before the spectator event . in one particular example , the condition may be a number of games won by a home team at a specified point in the season or what place a home team is in team standing at a specified point in a season . in further examples , a price of a guarantee may include more than one condition . for example , a price of a guarantee for a baseball game may be a price for a refund of 60 % of the ticket price to the ticket buyer if the home team is shutout and the home team loses by more than five runs . in one particular example , one or more of the following information is inputted into the guarantee pricing provider system 302 to determine a price of a guarantee : type of event , name of event , place of event , date of event , participants in the event ( e . g ., teams , performers , and so forth ), price of the tickets , number of tickets ; potential percentage refund ; and the contingency selected . in one particular example , the guarantee pricing provider system 302 may use one or more of the following information to determine the loss probability , evaluate risk and determine pricing of the guarantee : historical data relating to the contingency selected , the type of event , place of event ; participants in the event ; price of the ticket ; number of tickets ; and the potential percentage refund . in one particular example , the guarantee pricing provider system 302 may combine the historical data above with the number and cost of tickets , to generate the level of risk and potential loss / payout data . once the level of risk and potential loss is established , the guarantee pricing provider system 302 may determine pricing based upon the acceptable risk to the grantor of the guarantee . once the loss probability is calculated , the guarantee pricing provider system 302 may output one or more of the following information : the loss probability and the price for the guarantee . in another particular example , one or more of the following information is inputted into the guarantee pricing provider system 302 to determine the price of the guarantee : the sport ; name of home team ; description of ticket package ; price of the ticket package , number of tickets within the ticket package ; potential percentage refund ; first contingency selected ; second contingency selected ; additional contingencies ; if more than one contingency is selected , whether only one , or more than one , of the contingencies must occur ; contingency measurement point ; and data from multiple sources with respect to the expected performance of the team for that season . in one particular example , the guarantee pricing provider system 302 may use one or more of the following information to determine the loss probability , evaluate risk and determine pricing : the sport ; the home team ; the price of the ticket package ; the number of tickets within the ticket package ; the potential percentage refund ; the contingency or contingencies selected ; whether only one , or more than one , of the contingencies must occur ; and data from multiple sources with respect to the expected performance of the team for that season . the guarantee pricing provider system 302 may combine the data set forth above , to generate the level of risk and potential loss / payout data . in one example , after the level of risk and potential loss is established , the guarantee pricing provider system 302 may determine pricing based upon the acceptable risk to the provider of the financial backing for the guarantee . once the loss probability is determined the guarantee pricing provider system 302 may output one or more of the following information : the loss probability , the maximum payout ; the likely payout ; and the price for the guarantee . process 400 sends the price of the guarantee to ticket seller ( 410 ). for example , the guarantee pricing provider system 302 sends the pricing of the guarantee for the tickets by updating a webpage . process 400 receives notification that ticket seller agrees to the price of the guarantee ( 414 ). for example , a ticket seller using the ticket seller computer 304 acknowledges on the webpage that the price of the guarantee is accepted . process 400 offers tickets to sell ( 418 ). for example , the guarantee pricing provider system 302 offers the ticket to be sold using a webpage . process 400 receives notification that tickets ( s ) sold ( 420 ). for example , the guarantee pricing provider system 302 sells the tickets . process 400 receives data related to the condition ( s ) ( 422 ). for example , the guarantee pricing provider system 302 receives data on the spectator event related to the condition . in one particular example , a website at the guarantee pricing provider system 302 receives data electronically automatically regarding the results of a game and / or other conditions ( e . g ., temperature ). in another particular example , the data from the spectator event is entered manually using a gui . in one example , the data from the spectator event may be received during or after the spectator event . in another example , the data related to the condition ( s ) may be received by the ticket provider system 102 before the spectator event . process 400 determines if condition ( s ) are met ( 424 ). for example , the guarantee pricing provider system 302 determines if the condition was met by analyzing the data received in processing block 422 . if the condition ( s ) was met , process 400 enables a refund ( 426 ). for example , the guarantee pricing provider system 302 enables payment to the ticket buyer by check , electronic funds transfer , credit card refund or giving credit , based upon the specified payout . referring to fig5 , in one example , the ticket provider system 102 ( fig1 a ), the ticket prover 102 ′ ( fig1 b ) and or the guarantee pricing provider system 302 may include a computer 500 . in one example , the computer 300 may include a processor 502 , a volatile memory 504 , a non - volatile memory 506 ( e . g ., flash memory , hard disk and so forth ) and the user interface ( ui ) 508 ( e . g ., a graphical user interface , a mouse , a keyboard , a display , touch screen and so forth ). the non - volatile memory 506 stores computer instructions 512 , an operating system 516 and data 518 . in one example , the computer instructions 512 may be executed by the processor 502 out of volatile memory 504 to perform any portion of the processes described herein ( e . g ., the processes 200 and 400 ). the processes described herein ( e . g ., the processes 200 and 400 ) are not limited to use with the hardware and software of fig5 ; they may find applicability in any computing or processing environment and with any type of machine or set of machines that is capable of running a computer program . the processes described herein may be implemented in hardware , software , or a combination of the two . the processes described herein may be implemented in computer programs executed on programmable computers / machines that each includes a processor , a non - transitory machine - readable medium or other article of manufacture that is readable by the processor ( including volatile and non - volatile memory and / or storage elements ), at least one input device , and one or more output devices . program code may be applied to data entered using an input device to perform any of the processes described herein and to generate output information . the system may be implemented , at least in part , via a computer program product , ( e . g ., in a non - transitory machine - readable storage medium such as , for example , a non - transitory computer - readable medium , for execution by , or to control the operation of , data processing apparatus ( e . g ., a programmable processor , a computer , or multiple computers )). each such program may be implemented in a high level procedural or object - oriented programming language to communicate with a computer system . however , the programs may be implemented in assembly or machine language . the language may be a compiled or an interpreted language and it may be deployed in any form , including as a stand - alone program or as a module , component , subroutine , or other unit suitable for use in a computing environment . a computer program may be deployed to be executed on one computer or on multiple computers at one site or distributed across multiple sites and interconnected by a communication network . a computer program may be stored on a non - transitory machine - readable medium that is readable by a general or special purpose programmable computer for configuring and operating the computer when the non - transitory machine - readable medium is read by the computer to perform the processes described herein . for example , the processes described herein may also be implemented as a non - transitory machine - readable storage medium , configured with a computer program , where upon execution , instructions in the computer program cause the computer to operate in accordance with the processes . a non - transitory machine - readable medium may include but is not limited to a hard drive , compact disc , flash memory , non - volatile memory , volatile memory , magnetic diskette and so forth but does not include a transitory signal per se . the processes described herein are not limited to the specific examples described . for example , the processes 200 and 400 are not limited to the specific processing order of fig2 and 4 . rather , any of the processing blocks of fig2 and 4 may be re - ordered , combined or removed , performed in parallel or in serial , as necessary , to achieve the results set forth herein . the processing blocks ( for example , in the processes 200 and 400 ) associated with implementing the system may be performed by one or more programmable processors executing one or more computer programs to perform the functions of the system . all or part of the system may be implemented as , special purpose logic circuitry ( e . g ., an fpga ( field - programmable gate array ) and / or an asic ( application - specific integrated circuit )). all or part of the system may be implemented using electronic hardware circuitry that include electronic devices such as , for example , at least one of a processor , a memory , a programmable logic device or a logic gate . elements of different embodiments described herein may be combined to form other embodiments not specifically set forth above . various elements , which are described in the context of a single embodiment , may also be provided separately or in any suitable subcombination . other embodiments not specifically described herein are also within the scope of the following claims .