Registration Confirmation
Some people have asked, "What should happen if my registration was successful?" Here's the progression of events for a successful registration:
1) Fill in the screens of information
2) After clicking "submit" on the final screen, a new screen should come up with a copy of all the information you just entered. At the bottom of the page is a button that says "Checkout"
3) After clicking "Checkout", if your payment was accepted three things should happen: a) a screen thanking you for registering should appear b) you should get an e-mail from youth2009@wels.net with a copy of the information you entered, and c) you should get a payment confirmation from Wells Fargo via e-mail. NOTE: Sometimes these e-mails are caught by SPAM filters and end up in a junk folder or simply never arrive, depending on your network/e-mails security settings...
If things didn't proceed as outlined above, then your registration did not go through. Some possible problems:
1) If you missed any required fields on the form, an error message would have popped (or the form might recycle to the beginning) up at step 2 above when clicking "submit" and the required fields would have been highlighted in yellow.
2) If your payment was declined, either a white screen or an error message would have come up after clicking "submit" or "checkout" in step 2 above
3) If you misspell any portion of the words in the anti-SPAM Captcha (the goofy looking two-word phrase in the box near the end of the form), the form will cycle back to the beginning.
4) If you're attempting to complete registration from a public computer (school computer lab, library computer, work computer) and/or your computer/Internet browser has strict security setting, your information might be being prevented from transmitting.
5) If you're using a Web browser other than Internet Explorer or Firefox, we can't guarantee that the form will work properly.
These are the most common issues people encounter. Trying a different computer, a different credit card, or adjusting security settings usually solves the problem.