Configuring Payment Workflow
Overview
The Payment Workflow allows you to manage the steps a participant follows when completing payment during registration. From the workflow editor, you can configure workflow details, assign forms and thank-you pages, connect to follow-up workflows, and manage visibility of supporting pages.
Step-by-Step Approach
1. Drag and drop the Payment Workflow onto the Main Editor
- Navigate to the Workflow Builder.
- From the workflow list or sidebar, drag Payment Workflow onto the Main Editor canvas.
- Position it where it best fits in your registration process.
2. Click on Edit details, Lock, or Delete
- Hover over or select the Payment Workflow block.
- Use the available icons or menu options to:
- Edit details – open and configure workflow settings.
- Lock – prevent further edits (useful when the workflow is finalized).
- Delete – remove the workflow from the editor if no longer required.
3. Enter or edit the workflow name and description
- Update the Workflow Name to reflect its purpose (e.g., Standard Event Payment).
- Add a Description to help other admins understand the workflow’s function.
4. Enter or edit the In-Progress Stage Name
- Define the In-Progress Stage Name that will display when participants are in the payment process.
- This helps track participant progress through the workflow.
5. Select Forms from the Forms select field
- Choose the Form(s) that will be used during the payment stage.
- Ensure the selected form captures all required billing or registration data.
6. Select the Thank You Page from the Thank You Page select field
- From the dropdown, select the Thank You Page the participant will see after successful payment.
- This page typically confirms registration and provides next-step information.
7. Select the Thank You Email from the Thank You Email field
- Choose the Thank You Email template that will be sent automatically after payment is completed.
- Make sure the email includes confirmation details and contact information.
8. Select additional pages visible in this workflow
- Configure any supporting or optional pages that should be visible within the payment workflow.
- These may include policy pages, receipt pages, or supplementary information screens.
9. Connect this workflow to other workflows
- From the editor, connect the Payment Workflow to follow-up workflows such as:
- Decline
- Pre-Arrival
- Confirmation
- Or any other relevant workflow paths
- This ensures the participant moves seamlessly to the correct next step based on their payment status.
10. Build a Custom Process Sequence for Engagement Sequence
As a user you can add custom process that run before the Arrival action is processed. Examples include:
- Send a follow-up notification or reminder.
- Tag or update participant profile fields.
- Trigger conditional steps based on response.
- Add participants to a segment or group.
- Start another automated workflow.
To do this:
- Click the + Engagement Sequence button on the Arrival block.
- Select the action type you want to include.
- Configure the action details (rules, message content, timing, etc.).
- Repeat this step to chain multiple actions and create a process sequence.
Apply Conditions (Optional):
- If required, add conditions so actions trigger only when criteria are met (e.g., Event-based, Participant-based, Workflow-based etc.).
11. Build a Custom Process Sequence for After Payment Sequence
As a user you can add custom process that run after the payment action is processed. Examples include:
- Send a follow-up notification or reminder.
- Tag or update participant profile fields.
- Trigger conditional steps based on response.
- Add participants to a segment or group.
- Start another automated workflow.
To do this:
- Click the + Engagement Sequence button on the Arrival block.
- Select the action type you want to include.
- Configure the action details (rules, message content, timing, etc.).
- Repeat this step to chain multiple actions and create a process sequence.
Apply Conditions (Optional):
- If required, add conditions so actions trigger only when criteria are met (e.g., Event-based, Participant-based, Workflow-based etc.).