HomeHome Product Discus... Product Discus...Payment Registr...Payment Registr...Recurring Billing issue with Paypal StandardRecurring Billing issue with Paypal Standard
Previous
 
Next
New Post
12/5/2013 10:54 AM
 
SmithReg Pro v4.50
DNN version 6.1.5 (PowerDNN hosting)
SQL version 2008R2

I am having an issue with recurring billing using The SmithReg Pro module and the PayPal Standard payment gateway.  The initial billing happens, the subscription/account is created on the DNN site, the recurring billing profile is configured on PayPal, and re-billing occurs as expected by PayPal.  The issue is that when the re-billing occurs at PayPal nothing about the subscription gets updated on my site.  This results in members who have been billed for a renewal getting locked out of the system because their enrollment in the security group expires.

I have checked the configuration and the documentation.  (Attached Screenshots Smith.regproconfig.JPG and Smith.gatewayconfig.JPG)

Of note, I have verified that the URL return from PayPal is set to my site's home page.  See attached screenshot - Smith.pmtdataxfer.JPG

QUESTION:  Is this setup correct even if the registration module is NOT located on the home page?  In my case the registration module is on the /Membership.aspx page.

This has been an ongoing issue from the start, but now, with growing numbers of subscriptions, it is becoming a real pain.

Thanks in advance!

-Mike




 
 Login to download attachment
New Post
12/6/2013 8:24 PM
 
Hi Mike,

How long after the initial first payment are you expiring the Role?

Typically, if a customer is still being charged for ongoing recurring payments the Role should not be expired unless their card is declined or the transaction fails.

When using PayPal Standard, once the transaction has been processed in the module, no further communication between PayPal and the module is done.

If you would like the gateway to communicate back with the Reg Pro module I suggest using Authorize.net which supports the "Silent Postback" feature. When using the Silent Postback with Auth.net, if a scheduled transaction fails, the postback mechanism will result in the role that was assigned on sign up being removed from the user.

Hope this helps!
 
New Post
12/10/2013 10:47 AM
 
Kevin,
Thanks for the response. This might just be a misunderstanding in the functionality available within the module.

I set the role to expire at the duration of the subscription (i.e. 30 days, 3 months, etc.) as I was under the impression that the registration module would handle extending it with each successful payment. It appears this is backward and I should expire the role in DNN based on 'forever' or what ever max occurrences I want to have. Is this correct?

Also, when I read this about the product features:

"If recurring credit card subscription fails authorization user is automatically removed from DNN role."

I didn't understand that there was a limitation based on the payment gateway used. Is this the case? If so, are there plans to add this functionality to other gateways (i.e. PayPal) in the future? Is Auth.net my only option if I want this feature?

Thanks, as always for great service and support!

-Mike
 
New Post
12/18/2013 2:53 PM
 
Hi Mike,

Yes you should only remove a user from the role only if the transaction is declined.

Auth.net is currently the only payment gateway which communicates back with the module if a transaction is declined.

If you would like the gateway to communicate back with the Reg Pro module I suggest using Authorize.net which supports the "Silent Postback" feature.

Let us know if you are interested in switching to Auth.net as we are authorized resellers and can get you set up quickly. Tp move forward, please purchase the Authorize.Net Payment Gateway Setup from the following link: https://www.smith-consulting.com/pd/P...

Hope this helps!
 
Previous
 
Next
HomeHome Product Discus... Product Discus...Payment Registr...Payment Registr...Recurring Billing issue with Paypal StandardRecurring Billing issue with Paypal Standard