Wednesday, April 3, 2019

New “Require Immediate Payment” Functionality


We’ve added new functionality to the Require Immediate payment feature on Regatta Network.  On the Payment Options tab of Edit Event Information, if you select “Require Immediate Payment,” the entrant will be able to register as before: 
·         During registration, the entrant is be told that their registration is not complete without payment. 
·         They receive an email confirmation with a link to edit their registration, and an link to the payment page.
·         The Entrant is added to the event with an unpaid status to the Edit Event Entries, Email/SMS Console, and Scoring
·         The Entrant is hidden from most publicly available entrant lists and is blocked from completing an additional registration. 
If you select the option to “Hide Registrations That Have Not Paid,” as an additional option on the Payment Options tab of the Edit Event Information console, there are several key differences to the entrants experience and the options to manage the event. 

·         The entrant will register as before, and be told that their registration is not complete until they submit payment. 
·         They will not receive an email confirmation regarding their registration until they have completed their payment. 
·         The entrant will not appear on any public registrant list until payment is submitted.
·         The entrant will not be added to Edit Event Entries, Email/SMS Console, Accounting Reports or Scoring until they have either a) completed the payment process or b) the organizer decides view the unpaid entries from the Edit Event Entries, Email or SMS console.

So as the organizer, you can mark them as paid if paying you directly, and you will have the option to email or text the entrant and “remind” them to submit payment. 

Also, the entrant will be able to complete multiple registrations, and naturally only paid entrants will be included on your accounting reports.  Please feel free to contact us with questions or comments.  

No comments: