From first invitation to opening night.

Your brand & California business details

Supply the legal operator or business name, business mailing address, support email, and privacy contact. Confirm your business setup, tax treatment, event restrictions, retention schedule, and refund policy with qualified advisers. The included terms and privacy pages are review drafts and must be finalized before real customers use the service.

Hosting does not guarantee physical California data residency. Confirm any location requirements separately. Hosts and guests use independent rsv-we email/password accounts. Email verification and recovery email delivery are not enabled; account recovery uses a private recovery code.

Stripe Connect & payment launch

Create or connect your Stripe platform account, activate Connect, and configure STRIPE_SECRET_KEY and STRIPE_WEBHOOK_SECRET as protected hosting secrets. Register /api/stripe-webhook on the deployed domain for checkout.session.completed, checkout.session.async_payment_succeeded, checkout.session.expired, and charge.refunded. Verify that the site’s public access boundary allows Stripe callbacks before enabling payments.

Run Stripe test-mode end-to-end checks for $5 event setup, $10+ destination charges with 10% application fees, Connect verification, failed and expired checkouts, duplicate webhooks, full refunds, transfer reversals, fee refunds, and disputes. Finalize tax and exceptional-cost handling. Do not switch to live keys until these checks pass.

Amazon wishlist behavior

Wishlist URLs and manually added items work as a linked shared checklist. The claim system prevents two confirmed guests from claiming the same item. It does not import Amazon accounts or synchronize purchases. A direct Amazon integration requires a supported Amazon program/API and its authorization; do not scrape private lists.

AdSense

Ads are intentionally inactive. Apply for AdSense and obtain publisher approval. Before enabling scripts, add your approved publisher and ad-slot IDs, supply ads.txt as required, review content placement and traffic policies, update privacy disclosures, and integrate a suitable consent platform including Google-certified consent management where required.

Avoid ad placements on private guest records, checkout, and account pages. A publisher ID by itself is not approval or a complete consent integration.

Domain & public access

Connect rsv-we.com to this Site using the exact DNS records returned by the hosting tools. The registrar/DNS owner must enter and verify those records before the custom domain is active. Domain purchase alone does not connect hosting.

Visitors can browse the landing page and published invitations without signing in. RSVPs, wishlist claims, and event creation require an rsv-we account. Private drafts and guest records require authorization. Payment, legal, and support launch steps still need to be completed before live commerce.

Invitations & support

Link sharing, QR downloads, invitation PNG downloads, calendar files, native sharing, and prefilled email messages are available. Automated outbound email is not configured. Add a verified sending domain and an email provider if automatic host or guest delivery is wanted.

Set up a monitored support channel, abuse reports, privacy requests, account/data deletion, and payment incident procedures before public operations. Complete accessibility and mobile checks with actual users and test the production callback flows.