Resolved RSForm submits new user even if not paid

Hey Eric,

If payments fail, the new user is registered anyway!

User registration is not done by RO Payments.

At least the not-paid user should be deleted and the correct message should appear, IMHO.

This is not a task of RO Payments as it does not create the user either. This is going to need a custom plugin to react to the plugin triggers and take appropriate action or the plugin you use for creating the user should check the _STATUS field of a submission. This is out-of-scope for RO Payments.

And no matter whether I switch the RSform messages on or off, the RO Payments message "payment failed" is never shown.

The failed message is shown if the response from Mollie is fail or failed. Is that also the status you get back? If you use the RSForm messages itself, there is no distinction based on payment status. This has to go through RO Payments.

Am I doing something wrong?

I assume you have created the messages in RO Payments, if so that should be fine. There must be something with the status what is not triggering the message.

To check what happens when you do not have a successful payment, post the screenshots of your RO Payments settings in RSForm, the transaction log and a screenshot of the messages you have. Are you not seeing any message when the status is cancelled?

Hi Roland,

Hmm, well, it's a bit disappointing that it's not possible to use RSForm for paid user registration.
I thought it was going to be a lot easier than what I did myself in Fabrik with your onPaymentCompete plugin.
In there I put code to delete the customer when payment was not successful, and a cron job that deletes customers after an hour if there was no feedback at all from Mollie. I guess I could do that for RSFom as well, but I'd rather copy my Fabrik solution.

But I wonder: in a regular (not a user-creation) RSForm, would the non-paid entry be marked as such?

Attached you will find an example of a cancelled transaction. Looks good but after the cancellation or fail (in Mollie test mode) the screen just goes back to the form.
No message at all. I also attached screenshots of the RO Paments plugin settings in the form, and the messages

Hello Eric,

Hmm, well, it's a bit disappointing that it's not possible to use RSForm for paid user registration.

RO Payments is a payment extension, not a workflow extension. Of course you can do paid user registrations but this is going to require a custom plugin to handle the trigger.

But I wonder: in a regular (not a user-creation) RSForm, would the non-paid entry be marked as such?

Yes, there is the internal field called _STATUS which has a value of 0, -1 or 1 which represents pending, denied, accepted. You see this field in the submissions list as Payment Status/Betaalstatus. The user creation plugin should be looking at this actually if payments are enabled. That would save everybody from building plugins

Looks good but after the cancellation or fail (in Mollie test mode) the screen just goes back to the form.

Going back to the form is expected because RSForms has no separate page for the result. They check the user session, if there is no data they show the form, if there is a message in the session they show the message. :/

As you said, there is nothing odd in the logs and you are redirected to the correct URL with the task jdideal.return which sets the message in the session and then redirects back to the form. To test, if you set the option Show RSForms Thank You page to Yes in the RO Payment settings, do you see the message from RSForms or are you taken back to the form as well?

Yes, there is the internal field called _STATUS which has a value of 0, -1 or 1 which represents pending, denied, accepted. You see this field in the submissions list as Payment Status/Betaalstatus. The user creation plugin should be looking at this actually if payments are enabled. That would save everybody from building plugins

In which table is this internal field called _STATUS? RSForm can actually create the user based upon a field but I only see my own form fields in their dropdown. Please see attached screenshot. And the line below the dropdwn says:

Indien je de gebruiker wilt aanmaken op basis van een veld selectie, zorg ervoor dat het veld één van de volgende waardes bevat: 1 of registreer. Elk andere waarde en de registratie wordt genegeerd (Er wordt geen gebruiker geregistreerd).

Looks like useful but how?

Hello Eric,

The table is the same for all RSForm field values, it is the rsform_submission_values table. To be completely correct, it is not RSForms creating the user but it is their user registration plugin which was a headache to get working last time I used it.

How I made it work is that I created a hidden field and fill this with the value 0 or 1 depending on whether the user should be created in the PHP Scripts section. This field can then be chosen in that dropdown. This is regardless of the payment status. Another plugin would handle any other tasks based on the payment status, this is being triggered by the RO Payment triggers.

The problem you have here is that the User registration plugin needs this value before the payment is made, so there is no relation between creating the user and the payment status. This plugin has no triggers it listens to for anything payment related.

OK, thanks, up to Fabrik then!

Best,
Eric