Cristián Lávaque

Great! Thanks for the update. :)

Thanks! I’m taking a look now.

If you’re changing the role manually from free to paid, then there wouldn’t be a subscription profile with payment info in the payment gateway.

If you want users to paid for their upgrade, have a subscription button shown to logged in users, and then his account will be upgraded after successful checkout.

Randy, have you tried the troubleshooting advice here? Knowledge Base » Common Troubleshooting Tips. I’d start with the plugins section.

I opened the page you linked to and see the message, but that’s not the default WP registration page. Pro-forms would not give that error.

What did you use to create that registration page and redirect to it from the default one?

Glad I could help. :)

Hi Russ, sorry about the delay, I haven’t been around since Saturday and just returned today. I didn’t notice the email with the site info when you sent it, we usually wait for an update in the thread letting us know that it was sent. Sorry for not noticing it sooner.

I found the email with the info but when I tried to login to the dashboard, I got an error. I guess you probably changed the credentials after not hearing back from me. Could you please send an updated one and let me know here that you did? Thanks! s2Member® » Private Contact Form

Yes, I see what you mean. I don’t know how to change that on PayPal’s site. Have you asked PayPal support about it?

When the user is logged in at the time he loads the page with the upgrade button, the button will include his user ID so the payment will go to it. If the user is paying for another level, the account will be changed to it. If he’s purchasing custom capabilities, these will be added to his account.

Okay, Jason and I just spent some time going over your installation and testing some things out.

I created a Test page for the 1 cent pro-form, but protected it with a password so it could be published but not accessible by your visitors if it happened to show up somewhere. I hope that was okay.

Jason explained to me that for the PayFlow API, the recurring solution is PayFlow Recurring Payments, but since the PayPal Pro API uses DPRP, and that’s what was available until they added the PayFlow Edition recently, sometimes the PayFlow one may get called DPRP. What’s actually being referred to is the recurring payment option.

This threw me off, because the log’s error, which is what PayPal said to s2Member, says that DPRP is disabled, it doesn’t say recurring payment. So I apologize for insisting on DPRP earlier. From what you told me, you have recurring payments enabled in your account, so that’s fine.

He tried two different cards and both times he got this error:

Error #36. Transaction failed: Fail to obtain approval for the online transaction.

I asked him why that could be and he said it’s hard to know for sure. It could be because the account does not accept certain types of credit cards, or anything really. That that’s something you would need to consult PayPal about. They are refusing to authenticate his card for some reason.

He also tried paying with the Express Checkout option, and he got another error with that one:

Error #1. User authentication failed: PayPal.

The user authentication failure indicates that the PayPal account or the PayFlow API credentials, or both, are incorrect. From the above test with the cards, it looks like it connects to the PayFlow API, and you confirmed before that you verified them to be correct. The error does say “PayPal” at the end, so maybe it means the PayPal account, so you’d need to verify that the PayPal account credentials are correct.

He said that in this case, the User Authentication error could be occuring because your Payflow account is not tied to the PayPal account for some reason. That’s not common, but it’s possible.

He suggests that you write back to PayPal and explain that he’s getting a User Authentication error when he tries to use Payflow together with Express Checkout. He’s almost sure that that error is caused because your Payflow account is somehow not tied together with your actual PayPal account.

Payflow is managed at: http://manager.paypal.com
Your PayPal account is managed at: http://www.paypal.com

If your Payflow account accepts credit cards, but does not accept PayPal, this will cause problems.

---

Please let me know how it goes with the credentials verification and with PayPal about the failed transaction. After you verify/fix credentials, or link the accounts, etc, please test again purchasing the subscription with Express Checkout and cards, and let me know how it goes.

Sorry for the long reply, but I hope it helps. :)

according to Paypal – the account is PayPal Pro. It is not a PayFlow Pro account.

Thank you for confirming it.

According to PayPal, s2 Member should be using the Payflow’s Recurring Billing instead of http://www.PayPal.com ‘s DPRP.

I’ll ask Jason about this, then. I’m pretty sure other site owners with PayFlow edition used DPRP… I’ll let you know as soon as I hear back from him.

The server scanner script can be used without a problem in a shared host, I have HostGator too and have no difficulty trying it there. This tool would help see if the s2member folders are the way they should (not changed/missing files). Knowledge Base » s2Member® Server Scanner

I also asked for the site info so I could take a look for you to help identify what the issue in your installation is, but I didn’t get it.

s2Member and s2Member Pro are installable and work every time I’ve tried it and most other site owners try it. When they can’t, it’s usually one of the things I suggested you check earlier. This is the refund policy: s2Member® » Terms » Refund Policy

If you send me the site info (dashboard and FTP), I’ll review your installation to find why s2Member Pro may not be recognized as you said. Thanks! Here’s the private contact form: s2Member® » Private Contact Form

Thanks for great question. I’ll forward it to Jason, who’s the one that coded it and is more familiar with PCI. I’ll let you know when I hear back from him. :)

Thanks for the info.

So you’re selling a subscription. I wanted to see the shortcode for that, because EOT for buy-now transactions is handled differently.

I see that it’s a non-recurring subscription, though. These are good if you plan to use the trial/initial term subscriptions allow, but you’re not using it in that shortcode. Maybe you’d prefer to sell them as buy-now transactions: rr=”BN” [hilite path]Dashboard -› s2Member® -› PayPal® Pro Forms -› Shortcode Attributes -> rr[/hilite]

A user who was expired already since June ’12 re-joined yesterday, but the EOT shows at March 2014. I think the EOT should be extended from the date of the renewal but it’s not happening.

Okay, I’m re-reading your original post now, let me see if I understand correctly. You wanted his previous subscription to be extended from last year’s date when he paid his membership now. Is that correct?

Buy-now transaction can extend the time the user already has, you’ll find a setting for it here: [hilite path]Dashboard -› s2Member® -› PayPal® Options -› Automatic EOT Behavior -> Auto Extend[/hilite]

But even if it had been buy-now and you had that setting enabled, it applies to EOTs in the future, not past ones. If the user already expired and had been demoted and he now pays a new year, then the EOT will be set a year in the future.

If you want to make dynamic adjustments to this, it’s possible with some PHP in your shortcode. This article will help: Knowledge Base » Using Variables In A Shortcode