In the Guest Checkout settings, administrators can choose whether to allow public payments and, if enabled, how to collect guest data. When the Allow Public Payments option is disabled, payments from public users will not be processed. This article will cover the three available options when public payments are enabled:
- Creating a new account for each payment
- Adding payments as public
- Associating them with a catch-all account
Create new account for each payment
This section occurs with the Handle as - Create new account option.
Fields | Description |
1. Allow Public Payments | The button should toggle to enable or disable the acceptance of public payments. |
2. Handle as | Create new account for this example. |
3. Default Account Type | Choose a default Account Type the new account should be created under. |
4. Additional fields | Additional information collected on the new account. Information: Additional information collected will be used when creating the account. |
5. First/Last Name* | First and Last name. |
6. Email Address* | Email address. |
7. Mobile Number* | Cellphone number. |
8. Address* | Address. |
9. Note* | Payment note that appears on statement. |
10. Catch-all Account | In case the admin doesn't want to capture the account (donation less than a certain amount) and the Tile doesn't require additional filed it could be associated with the Catch-all Account. |
11. Cancel | Cancel all above selections. |
12. Save | Save all above selections. |
* Can be required
Adding payment as public
This section occurs with the Handle as - Add as public payment option.
Fields | Description |
1. Allow Public Payments | The button should toggle to enable or disable the acceptance of public payments. |
2. Handle as | Add as a public payment for this example. |
3. Additional fields | Additional information. Information: Additional information collected can be used in the web app to associate with or create an account. |
4. First/Last Name* | First and Last name. |
5. Email Address* | Email address. |
6. Mobile Number* | Cellphone number. |
7. Address* | Address. |
8. Cancel | Cancel all above selections. |
9. Save | Save all above selections. |
* Can be required
Associate to catch-all account
This section occurs with the Handle as - Catch-all Account option.
Fields | Description |
1. Allow Public Payments | The button should toggle to enable or disable the acceptance of public payments. |
2. Handle as | Associate to catch-all account for this example. |
3. Catch-all Accounts | All accounts in the ShulCloud database to choose from for the catch-all account. |
4. Additional fields | Additional information. Information: Additional information collected will appear in transaction memos. |
5. First/Last Name* | First and Last name. |
6. Email Address* | Email address. |
7. Mobile Number* | Cellphone number. |
8. Address* | Address. |
9. Cancel | Cancel all above selections. |
10. Save | Save all above selections. |
* Can be required
Related Resources
- ShulCloud Mobile Payments App v1.0 (Feature Overview)
- Mobile Payments App - Create an Event (How To)
- Mobile Payments App - General settings of an event (Reference)
- Mobile Payments App - Checkout settings of an event (Reference)
- Mobile Payments App - Add and Edit Tile (How To)
- Mobile Payments App – Tiles (Reference)