1. Login to your dashboard as an Event Organizer and navigate to the left of your screen, select Management > Participants followed by Participant List and then customize the fields you want to see, click View Results
2. Use the search bar above the results to type in the participant's name or email to find their original registration transaction
3. Click edit on the right side of the participant's registration details
4. A modal will appear with the participant's info, on the lefthand side of the menu, click Issue A Refund
5. Now you will be taken to a refund page similar to the image below, here you decide:
- Is this a full refund? if yes, click total refund
- Is this a partial refund? if yes, click partial refund and change the amount in the box that reads amount
- Would you like to remove this person from the active list? this way they won't appear for bibs/shirts
- Would you like to return any line items such as tax? (example below is not returning tax)
- In the light red section, you can then decide whether or not to refund the admin processing fee, in most cases we recommend you do not refund it as this was the cost to process the original transaction
6. After tailoring the refund to the unique circumstance of this participant you can now review the refund total from the righthand side of the page.
7. Ready to go? click refund in the bottom righthand corner of the page and a pop up will appear to verify your decision to refund
8. If you chose to have Race Roster issue the refund directly an email is sent to the participant and a refund will be applied to the credit card they used for registration within 5-7 business days
Pro Tip
We recommend using the Additional Details tool under your Event Settings to clearly outline a refund and cancellation policy for your event participants. Most endurance events do not offer full refunds, especially on admin or processing fees paid during the initial registration.
See our Manage Participants section for more articles on modifying your athlete's registration information.
Comments
0 comments