A Member Splash guide to fixing common Gravity Forms problems on membership, waiver, and payment forms. Your forms are under Content > Gravity Forms.
1. Keep It Simple
The most common problem is too much logic in one form: variable pricing, date-based rules, multi-person flows. Instead:
Design each form for a single purpose (waiver, guest pass, and so on).
Use drop-downs, checkboxes, and radio buttons to control input.
Avoid too many free-text fields so reporting stays clean.
Tip: Think old-school — members used to add up totals on a PDF. The simpler the form, the smoother the experience.
2. Waivers and the Member Checkbox
Member Splash supports household waivers with the Member Checkbox field:
One submission covers the whole household — no need for multiple forms.
It records the member submitting, their ID, the form name, and the submission date.
Set the form's Member Splash Form Type to Waiver Form in the form settings so it shows on the Manage Account and check-in screens.
Waiver Expiration and Rules
Waiver forms reset every year on January 1 (valid through December 31). Members must re-sign each year.
If you need a form submitted once and kept permanently, use the Permanent Acknowledgment form type instead.
Marking a waiver as required blocks payment/reservation access until every member has a valid waiver.
Note: Do not rename a live waiver form. Waivers are matched by form name, so renaming breaks past submission data.
Recommended wording: "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
1 Product field — the item or service.
1 Total field — calculates the charge.
1 Credit Card field — for ECRYPT payments.
Email field — for receipts and confirmations (required for online payments).
Payment Method field — if you offer both credit card and ACH.
ACH Payments
ACH must be enabled through ECRYPT.
Include a Payment Method field.
Use conditional logic to show ACH fields only when ACH is selected.
Optional: Service Fees
To pass processing fees on to members, see Adding a Service Fee to Forms and Adding a Processing Fee for ACH Payments on Forms.
Recommended Fields
Billing address (with autocomplete).
Email address (required for online payments).
4. Payment Feeds and Conditional Logic
Every payment method needs its own feed:
1 Credit Card feed (always required).
1 ACH feed (if you offer ACH).
To set conditional logic on a feed:
Open the form and go to Settings > Ecrypt.
Create or edit a feed (for example, "Credit Card Payment").
Map the required fields (Total, Email, and so on).
Scroll to Conditional Logic and turn it on.
Set the rule: process if Payment Method is Credit Card.
Repeat for the ACH feed if needed.
5. Confirmations vs. Notifications
Confirmations: the message shown after the form is submitted. Good for a thank-you or next steps.
Notifications: emails sent to admins, members, or both. Use merge tags like
{Email:1}and{Name:2}.
Note: The most common issue is the notification's From Email. It must match your site's Admin Email Address (Settings > Site > General Settings), or emails will fail. See About the Administrative Email Address and Confirmations and Notifications on Gravity Forms.
6. Troubleshooting Checklist
Required fields: Product and Total fields are on the form. Guide
Payment method logic: the credit card field only shows when selected. Guide
Payment feeds: each feed is set up and uses the right logic. Guide
Notifications: From Email = Admin Email. Guide
Subtotal/Tax fields: if they are not working, hide them.
Form embed: use the Gravity Forms block, not a shortcode. Guide
Confirmations/notifications work: always test a submission. Guide
Honeypot disabled: for silent submission problems. Guide
7. When to Contact Support
Disable the form temporarily.
Add a message: "This form is temporarily unavailable while we resolve an issue. Please check back soon."
Submit a ticket with:
Form name
Form ID (found in the URL)
An example account showing the issue