I looked around for this topic but did not find quite what i was looking for.
I would like to have a end user be able to submit a form (registration) and then an option to pay later on, but tie it to the first form. Almost like user registration, but I dont need “website” registration - more like “end user will pay later” registration.
Something like user enters data in a form (registers), gets an email with a link to go back later and make payment.
This will avoid duplicating all the user information etc…
With Gravity Flow you can control if/when/in what order steps of functionality can be triggered to occur. For your goal of delayed payments, with the Stripe extension as example you would have two options.
Payment to be taken within 7 days from initial form submission?
In this case you can get the form submitter to provide payment details in the initial form submission and use the Capture Payment step to process the payment when needed. If it’s after 7 days, Stripe won’t allow this pattern to work. In which case.
+7 days Payment Form with Field Mapping
The Payment Form (Checkout) step allows you to use a separate form for payment, but everything behind the scenes gets associated where it is needed to the original request. If, for example, your initial form had a date field that the activity was for, you could schedule the payment step to occur -5 days ahead to ensure it’s top of mind for the person.