• Resolved smeckdesigns

    (@smeckdesigns)


    Hi,
    We just got a helpdesk ticket from a customer who tried to create an account (using the Restrict Content Pro plugin, paying using the pronamic plugin), had a bank issue when paying and decided to pay later.
    After some testing on our end it turns out that when you fill in the form to create an account, but cancel the payment, several things seem to go wrong.
    First off, the account is created and can be used despite not paying. And during the exact moment the payment has failed the account is set to pending and then directly to expired despite never being activated.
    Futhermore, when the customer wanted to resume payment, the signup discount was removed from the price and they had to pay the renewal fee instead of the signup fee.

    To be clear, the account is not set to active, so they still can’t see the restricted content, but disappearing signup discount and renewal costs instead of signup is quite a big issue since we offer a 50% signup discount.

    The RCP plugin support redirected us to the pronamic plugin for potentially being at fault. Is there any way to fix this issue?

Viewing 7 replies - 1 through 7 (of 7 total)
  • Plugin Author Reüel

    (@pronamic_reuel)

    This needs some testing from our developers. We’ll look into this and I expect to get back to you early next week.

    Plugin Author Remco Tolsma

    (@remcotolsma)

    First off, the account is created and can be used despite not paying.

    Smeckdesigns

    That’s right, the account is created immediately by Restrict Content Pro, but the user should not yet have access to protected content at that time.

    Futhermore, when the customer wanted to resume payment, the signup discount was removed from the price and they had to pay the renewal fee instead of the signup fee.

    Smeckdesigns

    How exactly does the customer proceed to resume payment? The RCP “Retry Payment” functionality is only available if no transaction ID is stored with the RCP payment. For a failed payment, there will be a transaction ID and the customer will not be able to resume the payment.

    Can you remove the transaction ID from a failed RCP payment in the WordPress admin dashboard and try the RCP “Retry Payment” feature on the “Your Membership” page? Does that work as you would expect?

    If so, we can modify our code to only store the transaction ID in the RCP payment once it is successful. This ensures that users/customers can always use the “Retry Payment” functionality for failed payments.

    We have also created a GitHub issue for this topic with more technical explanations and screenshots: https://github.com/pronamic/wp-pronamic-pay-restrict-content-pro/issues/8.

    Thread Starter smeckdesigns

    (@smeckdesigns)

    Thanks for the quick response aswell as the detailed github data

    How exactly does the customer proceed to resume payment? The RCP “Retry Payment” functionality is only available if no transaction ID is stored with the RCP payment. For a failed payment, there will be a transaction ID and the customer will not be able to resume the payment.

    remcotolsma

    well that’s part of the issue, it’s impossible to resume payment. I just did another test where i created a new account, and cancelled the payment. The system sent me back to my account, which is now creacted.
    But I immediately got an email saying the subscription is expired.

    Can you remove the transaction ID from a failed RCP payment in the WordPress admin dashboard and try the RCP “Retry Payment” feature on the “Your Membership” page? Does that work as you would expect?

    remcotolsma

    after manually deleting the payment ID there is an option on the user dashboard where I can try and make the original payment (the one with the signup discount) again.
    Currently however this requires both the manual deleting of the payment ID before the client tries to pay again and the customer having to navigate to the account details tab on the dashboard. For the target audience (aged 50+) this is too complicated.

    Plugin Author Remco Tolsma

    (@remcotolsma)

    We can’t change how Restrict Content Pro works, but we can probably do the following:

    1. No longer expire the RCP membership in the event of a failed payment.
    2. Only save the transaction ID in the RCP payment if it was successful, so the “Retry Payment” feature is available when payment failed.
    3. In the event of a failed payment, forward the customer/visitor to the RCP account page where the “Retry Payment” link is visible.

    We don’t have many other options, could this be an improvement that you can work with? Otherwise we have to ask the Restrict Content Pro developers for advice. Or maybe you have ideas of your own to make this even easier?

    Thread Starter smeckdesigns

    (@smeckdesigns)

    This sounds like a good improvement that we can work with ??
    We’ll just have to add a notification to the account page to point the user to the “retry payment” button.

    Plugin Author Remco Tolsma

    (@remcotolsma)

    Thank you for your patience, the code changes have been made. We will review this internally and expect to launch an update next week. The GitHub PR and code changes can be found here: https://github.com/pronamic/wp-pronamic-pay-restrict-content-pro/pull/9.

    Plugin Author Remco Tolsma

    (@remcotolsma)

    Pronamic Pay version 9.5 has just been launched and includes the previously mentioned changes.

Viewing 7 replies - 1 through 7 (of 7 total)
  • The topic ‘RCP failed payment issues’ is closed to new replies.