RSVPay

RSVPay lets someone organize a group event with a price per person and collect payment from attendees at the moment they RSVP. WHAT CHANGED IN THIS BUILD No user-facing change since build 28, which is already live; this keeps the binary in step with the JavaScript delivered to it. The binary now contains the waiver feature that reached users after build 28 was approved. An organizer attaches their own waiver text to an event or group; attendees read it, tick a box, and sign by typing their name. RSVPay stores the record and is NOT a party to it: it does not draft or review the wording and makes no claim about its enforceability, as our Terms of Service state. Nothing is gated behind signing it, and the demo account has none to sign. NOTHING ABOUT THE PAYMENT MODEL HAS CHANGED. Apple Pay is still offered only where payment is charged at authorization (guideline 4.9, build 26), and browsing without an account (guideline 5.1.1(v), build 27) is unchanged. BROWSING WITHOUT AN ACCOUNT Tap "Browse without an account" on the first screen — no account, no email, no prompt. You can browse and search public events and groups, open their full detail pages, and scan a QR code for either. Signing up is requested only where an account is genuinely needed: RSVPing, buying a ticket, joining a group, creating anything, or messaging. Attendee lists, group member lists and the organizer's name are deliberately not shown to a signed-out visitor — they identify private individuals who did not consent to being public, so the database refuses them rather than the interface hiding them. Private events and groups are not visible at all. SIGNING IN To review the full experience — RSVPing, chat, check-in and the organizer's view — please use the demo credentials above. That account belongs to a group and has upcoming events. PLEASE DON'T START WALLET SETUP This demo account is an attendee and group member, which is how most people use RSVPay. Attending events, paid or free, needs no setup of any kind. Collecting money as an organizer does. Two places invite you to set that up: the dimmed "Paid Event" option on the create-event form, and an "Organizing paid events?" card under Settings > Payment Methods. Both begin Stripe Connect identity verification — legal name, date of birth, government ID and a bank account. Please don't start it: it is real identity verification on a live Stripe platform, it cannot be completed with test data, and beginning it creates a real financial account. Nothing in the listing depends on it. As this account you can browse and RSVP to events, create your own free event, and use chat, bring lists, waitlists and QR check-in. Only creating a PAID event requires verification, which is why that option is dimmed. The Wallet tab appears only after verification, so this account shows four tabs rather than five — by design, not a missing feature. ABOUT THE PAYMENTS Payments are for real-world services consumed outside the app: attending a specific in-person event on a specific date, such as a pickup game or a group dinner. These are goods and services outside the app under guideline 3.1.5(a), so they go through Stripe rather than in-app purchase. No digital content or functionality is unlocked by any payment — the app is free and nothing in it is gated behind a purchase. RSVPay charges a service fee and pays the organizer after the event. This build uses LIVE Stripe keys, so test or sandbox cards will be declined. To review the full RSVP flow with no charge, please use the free event "Sunday Shootaround" on the Events tab: the same RSVP, attendee list, chat, bring list and check-in flow, with no payment step. For a paid RSVP, email [email protected] and we will set up a zero-cost test event or refund any charge. PERMISSIONS Camera: organizer QR check-in at the door, and scanning invite codes. Photos: optional event covers and photos in an event's album. Notifications: event reminders, RSVP activity, payment confirmations.