Deposits and discount codes

On an event with tickets, a ticket can take a deposit: families pay part of the price when they sign up, and the rest by a day you choose. Discount codes take money off on your church site's sign-up sheet. Both are on the event, under Tickets and Discount codes, and save as you go.

Take a deposit

1. In the Tickets card, open a ticket with a price, or add one, and type its Deposit, like 25 on an $85 ticket.
2. Under The rest is due by, pick the day. It comes before the event starts.

A deposit is at least $0.50 and less than the price (and the early price). The rest is due by the end of that day on your church's clock.

On your site, the ticket says "Deposit $25 now, the rest by Feb 20". Above the total, "How do you want to pay?" offers the deposit first ("Pay the deposit · $25 today", with the rest and its day under it) or Pay it all now: the whole price in one payment, one card fee, and nothing more to pay, so no reminders. Covering the card fee covers what's paid today. The payment step says which they chose, with Change, and the same choice shows when they pay from the change-or-cancel link or under Me, until the day the rest is due. When the whole price is more than your church takes by card at once, only the deposit is offered. When what's left after the deposits would be under 50¢ (too little for a card), there's nothing to choose: the total says it's all paid now, in one payment, and a ticket whose deposit leaves less than that doesn't mention it.

After a deposit, "You're in" says what's paid and when the rest is due, with a Pay the rest button, and the emailed receipt says the deposit paid, any card fee they covered, and what's left by when. PraisePad emails a reminder a week before the day and again the day before, each with a button to pay, no account needed (someone you added who hasn't paid anything yet is reminded of what's due, not "the rest"). They can also pay it from the change-or-cancel link in any of their emails, or under Me on your site. Once it's paid, the receipt says "Paid in full".

Change the day, and it changes for everyone who already signed up, with their reminders starting over. Once the day has passed, people signing up pay the whole price. Nothing is cancelled when the day passes: whoever hasn't paid still owes, and you decide.

Deposits in Who's coming

Who's coming says where each family stands: "Paid $25 deposit · $95 by Feb 20", then, once the day passes, "Owes $95 · was due Feb 20". The Owes pill counts open deposits too, and "Money so far" says how many deposits are open and what's to come. Cash or a check from the office counts toward the deposit: a family holding a place is in once its deposit is paid, in one payment or two. A family offered a place from the waitlist pays the deposit to confirm it. Reports › Events shows each event's open deposits, and its "Still owed" counts only what's due.

Make a discount code

1. On the event, under Discount codes, press Code.
2. Type the code, like FIRSTTIMER, or press Make one. It's 6 to 30 letters, numbers or dashes, and capitals don't matter.
3. Choose what it takes off: A percent (100% makes the tickets free) or An amount, which comes off a sign-up's tickets, never below free.
4. Under Uses, say how many sign-ups can use it, or leave it empty for no limit. Press Add it.

Each code's row says what it takes off and how it's been used, like "7 of 25 used", with "Used up" when none are left. A code that's been used keeps its code and what it takes off: only its uses can change, never below what's been used. Take it off, in its ⋯, stops anyone using it from now on; the orders that used it keep their discount.

Codes on your site

When an event has codes, Have a code? shows under the total. People type it and press Continue with the code: it comes off on the next step, before they pay, on a line of its own ("FIRSTTIMER −$20.00"). A wrong one is said plainly: "That code doesn't work for this event." or "That code has been used up." With a 100% code the family goes straight in ("Free with your code."), and their email says so.

A family that ends up on the waitlist keeps its code: when a place opens, its price has the code off, and while it waits it holds one of the code's uses. Someone only joining the waitlist isn't asked for a code.

Wrong tries are limited, so nobody can guess a code: after 10 wrong codes in 10 minutes, the sheet asks that person to wait a few minutes. A right code never uses a try, and one family's typos never hold up anyone else, so everyone on the church's wifi can use a code you announce. The Discount codes card counts the wrong ones ("12 wrong codes tried, the last Fri 3:12 PM").

Who sees the codes

A code is a key to a price, so only those who write events (Events editors and managers) and those who see who's coming (Events managers and the event's organizer) see them. In Who's coming, a sign-up shows its code and what it took off ("FIRSTTIMER −$20"), or "Free with STAFF". Duplicate copies the deposits and the day the rest is due, never the codes.