📘 Table of Contents
🧠 Keep It Simple
📝 Waivers & the Member Checkbox
💳 Payment Forms: Required Fields & Best Practices
🔁 Payment Feeds & Conditional Logic
✉️ Confirmations vs Notifications
🧾 Troubleshooting Checklist
🆘 When to Contact Support
🧠 1. Keep It Simple
The most common issue we see is overcomplicating forms with too much logic: variable pricing, date-based rules, multi-person flows. Instead:
Design each form for a single purpose (waiver, guest pass, etc.)
Use dropdowns, checkboxes, and radio buttons to control input
Avoid excessive free-text fields to keep reporting clean
💡 Think old-school: members used to tally totals on a PDF. The simpler your form, the smoother the experience.
📝 2. Waivers & the Member Checkbox
Member Splash supports household-level waivers with the Member Checkbox field:
One submission per household
No need to fill out multiple forms
Tracks the member submitting, their ID, the form name, and the submission date
🗓 Expiration & Submission Rules
Waivers expire automatically on December 31
Marking a waiver as required blocks payment/reservation access until all members have a valid waiver
🔒 Do not rename live waiver forms — it breaks historical submission data.
📝 Recommended language:
“Use the Member Checkbox field to submit one waiver that includes all members on your account for whom a waiver is required.”
💳 3. Payment Forms: Required Fields & Best Practices
To successfully process payments:
✅ Required Fields
1 Product field — defines the item or service
1 Total field — calculates the charge
1 Credit Card field — for Ecrypt payments
Email address field — for receipts and confirmations
Payment Method field — if offering both CC & ACH
🏦 ACH Payments
Must be enabled through Ecrypt
Include a Payment Method field
Display ACH fields only when ACH is selected (conditional logic)
💸 Optional: Service Fees
Want to pass through your processing fees? 👉 How to Add a Service Fee
📍 Recommended Fields
Billing address (with autocomplete)
Email address (required for online payments)
🔁 4. Payment Feeds & Conditional Logic
Every payment method needs a correctly set up feed:
🔁 Feed Requirements
1 Credit Card feed (always required)
1 ACH feed (if offering ACH)
🛠 Set Conditional Logic on Feeds
Go to Settings > Ecrypt in your form
Create or edit a feed (e.g., "Credit Card Payment")
Map required fields (Total, Email, etc.)
Scroll to Conditional Logic and enable it
Set the rule: "Process if Payment Method is Credit Card"
Repeat for ACH feed if needed
✉️ 5. Confirmations vs Notifications
📤 Confirmations
Message shown after form submission
Good for simple thank-you messages or next steps
📬 Notifications
Emails sent to admins, members, or both
Use merge tags like
{Email:1}and{Name:2}
⚠️ Most common issue: “From Email” must match the site’s Admin Email (in Settings > General), or emails will fail.
🧾 6. Troubleshooting Checklist
Use this checklist if your form isn’t working as expected:
✅ Required Fields: Product + Total fields present
Guide💳 Payment Method Logic: CC field only shows when selected
Guide🔁 Payment Feeds: Each feed is configured and uses correct logic
Guide📧 Notifications: From Email = Admin Email
Guide💵 Subtotal/Tax Fields: If broken, hide them
Guide🔗 Form Embed: Use Gravity Forms block, not shortcode
Guide📬 Confirmations/Notifications Work: Always test a submission
Guide🐞 Honeypot Disabled: For silent submission issues
Guide
🆘 7. When to Contact Support
Before submitting a ticket:
🚫 Disable the form temporarily
📢 Add a message: “This form is temporarily unavailable while we resolve an issue. Please check back soon.”
Submit a ticket and include:
Form name
Form ID (found in the URL)
Example account showing the issue