In a group system, group pay allows for the head unit to have a single checkout experience, instead of making a payment after the creation of each individual sub unit.
To set this up, follow the steps below:
How can I enable Group Pay?
You don’t have to do anything to enable group pay. By default, the checkout form will show all payments due for the group, and the user can decide which users they’d like to pay for.
However, for an optimal setup to streamline the sub-unit registration, we recommend placing checkout form on the head-unit level and not on the sub-unit level. This must be done in a specific order:
Remove the trigger on the checkout form on the child level.
Create a new category that comes AFTER the Child/Sub-Level forms.
Create a new head-level form to place the checkout widget on, that will live in the new category.
Trigger your new checkout form to “User Account Created” (the same as your other head-level forms)
Now, when the user is completing the child level forms, they will NOT see a checkout form until they are done with adding children/sub-units.
When the checkout form is on the head level, all payments due from all children will appear on the checkout form and allow the user to pay one time for everyone.
Here’s a good example of the form setup:
Notice that the parent level forms appear first, then the child level forms, and finally the group checkout form – which is on the head level.
This means the registration flow will go from parent forms, to child forms (as many times as there are children), followed lastly by the checkout form where the head unit can review and pay for all the sub-units in the account.
Note: you can include more forms on the 2nd head level category (“Family Checkout”) if you’d like. For this example, it’s only important that the checkout is at the end, is a head-level form, and is triggered appropriately.