Surfaces
Gifts
Gifted rego payment review, receiver redemption state, and capacity handling.
First created Last updated
Overview
Gifts is the event-management surface for regos bought by one attendee for another attendee. A gift is not an attendee rego until the receiver redeems it through the normal registration process.
Gift creation uses only the receiver’s username. The public gift purchase page now follows the same rego-style wizard pattern as attendee registration: receiver lookup, card-based tier selection, card-based add-ons, shared payment method cards, shared payment instructions, shared proof upload, and final review. Gift quotes include the same platform fee, provider fee, VAT, and surcharge behavior as regular paid rego. Coupons and affiliate codes apply to gifted rego purchases only when the specific coupon or affiliate record is enabled for gifts. The gifter can add a short markdown-ext message for the receiver and can choose whether the receiver sees the gift as from @username or from an anonymous gifter. Internal gift records still keep the real gifter account for support, audit, and abuse tracing. The receiver must still open their gift redemption link or the regular rego flow, fill their own attendee details, complete required event forms and custom inputs, and submit the redeemed rego without paying again.
Gift redemption is gated by the event’s rego confirmation behavior. If the event uses manual payment review, staff must confirm the gift payment on this page before the receiver can redeem. If the event uses good-faith confirmation, the gift can become redeemable immediately after the gifter submits required payment details. Hybrid follows the currently supported payment method behavior and should be treated as manual review for manual payment methods.
Dashboard route
/ems/manage/gifts?id=:eventId
Operating rules
| Rule | What it means |
|---|---|
| Gifting is disabled by default. | Enable it on Rego Config before advertising the attendee gift flow. |
| Username-only receiver lookup. | Staff should not ask gifters to provide receiver email, legal name, or private details. |
| Receiver notification is automatic. | The receiver gets an inbox notification and email when a gift is created, including the gifter’s optional markdown-ext message and public gifter identity only when the gifter did not choose anonymity. |
| Payment confirmation gates redemption. | Receivers cannot redeem until the gift is Ready to redeem, either by staff confirmation or by the event’s good-faith confirmation behavior. |
| One active gift per receiver per event. | A gift cannot be created for an attendee who already has a rego or an unredeemed gift for the same event. |
| Gift details do not become rego details. | The redeemed rego must use the receiver’s profile, display name, fursona, sizes, and event-required answers. |
| Unredeemed gifts are locked. | Gifts are non-refundable and non-transferable until redeemed. |
| Redeemed regos follow event policy. | Once redeemed, refunds, transfers, and upgrades follow the event-wide rules set by the partner. |
Capacity behavior
By default, a paid unredeemed gift reserves one event capacity slot and one tier capacity slot. This prevents selling the same slot twice while the receiver has not redeemed yet.
Partners can change this on Rego Config with Gift capacity handling. Use redeem-only capacity only when staff accept that gifts may be paid before a real slot is available at redemption time.
Table controls
| Control | What it does | Check before using |
|---|---|---|
| Search | Filters by gift ID, receiver, gifter, message, tier, or payment reference. | Clear search before reporting gift totals. |
| Status filter | Filters payment pending, submitted, confirmed, rejected, redeemed, and cancelled gifts. | Confirm the filter before reviewing payment queues. |
| Receiver visibility | Shows whether the receiver sees the gifter identity and whether a receiver message was included. | Staff can still see internal gifter records even when the receiver-facing gift is anonymous. |
| Confirm | Marks the gift payment confirmed and makes the gift redeemable by the receiver. | Verify payment method, reference, amount, and proof first. |
| Reject | Marks the gift payment rejected. | Include a clear note when staff need to explain the rejection. |
| Notify receiver | Opens the shared Notify modal for the gift receiver. | Use Email + inbox for durable rego-site notices, or SMS blast only when a verified SMS sending line is available and no inbox copy is needed. |
| Notify gifter | Opens the shared Notify modal for the gift giver. | Respect anonymous gift settings in receiver-facing copy; staff may contact the real gifter for support and payment issues. |
Payment and redemption states
| State | Meaning | Next action |
|---|---|---|
| Payment pending | Gift exists but no usable payment proof has been submitted. | Wait for the gifter to complete payment or contact them. |
| Payment submitted | Gifter submitted payment details or proof. | Staff review and confirm or reject. |
| Ready to redeem | Payment is confirmed and the receiver can redeem. | Receiver completes normal rego details and forms. |
| Redeemed | The gift has produced a real rego for the receiver. | Manage the rego from Regos. |
| Payment rejected | Payment was rejected. | Resolve with the gifter according to event policy. |
Common mistakes
- Do not treat a gift as a checked-in or registered attendee before redemption.
- Do not copy the gifter’s attendee details into the receiver’s rego.
- Do not manually bypass receiver forms or custom event inputs during redemption.
- Do not change gift capacity mode after sales begin without checking tier and event oversubscription risk.