Pro Forms Auth.net Upgrade broken?

I’m busy implementing a membership upgrade using Authorize.net pro forms and it’s canceling the ARB and creating a new one but not upgrading the user’s membership level. Is this a known issue? I’ve tried upgrades between multiple levels. Thanks.

An update on this issue:

Once again, the issue is that a simple upgrade from s2member level 1 to level 2 or level 2 to level 3 using Authorize.net Billing Modification form is not working.

I’ve confirmed on the Authorize.net side that the existing ARB is canceled and a new ARB is created with the new higher monthly price.

The user does not have access to higher level items once they complete the upgrade. In WordPress user management the user is still level 1 (or whatever their original level was).

Here’s the shortcode for the billing modification form:

[s2Member-Pro-AuthNet-Form modify="1" level="2" ccaps="" desc="$19.95 USD / Monthly ( recurring charge, for ongoing access )" cc="USD" custom="mydomain.com" ta="0" tp="0" tt="D" ra="19.95" rp="1" rt="M" rr="1" accept="visa,mastercard,amex,discover" coupon="" accept_coupons="0" default_country_code="US" captcha="0" /]

• This reply was modified 4 years, 10 months ago by  Jason (Lead Developer). Reason: Wrapped Shortcode in code tags

Quick question: I haven’t configured the authorize.net silent post option because my dev box is on a private subnet. Does member upgrade rely on receiving an authorize.net silent post to complete the upgrade? If so that would explain it.

I had a brief look at the code and it looks like the auth code routes the SP to the paypal code in the free plugin and there is some upgrade/modify code in there. I didn’t trace it fully, but it looks like this may be the issue. Can you confirm?

Thanks.

Seems I’m having a conversation with myself here but in case you run across this:

If you have not yet configured silent post for authorize.net, the membership upgrade feature won’t work in S2. Users will be told their upgrade has gone through and they will be billed, but they won’t have their access level increased. At least if you’re using Authorize.net ARB’s. I don’t know about other gateways and features.

Perhaps the devs can add this to the docs.

Mark,

Thank you very much for sharing these details with us.

I will forward this thread along to the lead developer so he can make this clearer in a future update.

Great thanks Raam. Awesome product.

Thanks for the heads up on this thread Raam.
I’m sorry for any confusion. However, actually, that is NOT the case.

s2Member Pro Billing Modification Forms do not depend on the Silent Post integration with Authorize.Net in this regard. You will want to have Silent Post enabled with your integration, so that s2Member can receive payment notifications from Authorize.Net, but upgrading from one Membership Level to another via Pro Forms is not dependent upon this aspect of your integration.

Perhaps you were testing the site in a way that restricted access to only certain IPs? Or anything like that? Perhaps you require a special cookie to access your site during development?

Ultimately, all transactions are processed together using s2Member’s core PayPal processors, which are an internal core functionality for s2Member. If this happens again, please take a look inside your logs directory, for anything that looks odd inside: /s2member-logs/ authnet-api.log or paypal-ipn.log. The Authorize.Net Pro Form processor will make a proxy connection to s2Member’s core IPN handler. If that fails due to some unknown reason, you might have issues.

If you run a transaction like this, and nothing comes into the core IPN handler (i.e. you have no paypal-ipn.log file), something is very wrong.

Thanks Jason. It appears to be working now so if I run into this again I’ll revisit your post and share what I find. Thanks again.

Awesome. Thanks Mark! Keep us posted :-)