Conditional payment or payment on single record update form

[Sprocket]

Hello, 

I am trying to set up a form that would allow users to register, and give them the option to pay immediately or if they prefer they can skip paying now. 

I tried using a conditional rule to hide the payment unless the user has indicated they do want to pay immediately. But the payment form still appears despite the conditional rule, I am guessing it's because all the payment fields are required and this cannot be changed.

So i tried instead making a single record update form for the payment, but it seems this is not possible either, after creating a single record update datapage, the 'insert' button does not include the 'payment' option. 

So the only solution I have thought of is 

1. have the registration form collect their contact information and choice of whether to pay now or later. 

2. Make the destination of the registration form be a separate payment form if they have chosen to pay now, and pass a unique ID from the first form submission as an external parameter to the payment form.

These users will not be authenticated so I am concerned that if the only thing linking  the first form with the payment form is an external parameter, there may be instances where that parameter value is accidentally deleted or missing, resulting in a payment but no indication of who it was from. 

If anyone has a suggestion for another way to approach this please let me know. thank you!

[TellMeWhy]

11 hours ago, Sprocket said:

Hello, 

I am trying to set up a form that would allow users to register, and give them the option to pay immediately or if they prefer they can skip paying now. 

I tried using a conditional rule to hide the payment unless the user has indicated they do want to pay immediately. But the payment form still appears despite the conditional rule, I am guessing it's because all the payment fields are required and this cannot be changed.

So i tried instead making a single record update form for the payment, but it seems this is not possible either, after creating a single record update datapage, the 'insert' button does not include the 'payment' option. 

So the only solution I have thought of is 

1. have the registration form collect their contact information and choice of whether to pay now or later. 

2. Make the destination of the registration form be a separate payment form if they have chosen to pay now, and pass a unique ID from the first form submission as an external parameter to the payment form.

These users will not be authenticated so I am concerned that if the only thing linking  the first form with the payment form is an external parameter, there may be instances where that parameter value is accidentally deleted or missing, resulting in a payment but no indication of who it was from. 

If anyone has a suggestion for another way to approach this please let me know. thank you!

Yeah, it's pretty risky, but, maybe you can require an email address on the payment form? You can also make the receiving field required and hide it  This will prevent the form from being submitted if nothing is passed.

Also, if you haven't checked this out for your workflow https://howto.caspio.com/tech-tips-and-articles/common-customizations/dynamic-redirects-after-form-submission/