About: JB Glossinger

i guess somehow something might have gotten corrupted somehow. The issue seems to have been resolved. I had our hosting company revert back to a restore point of a few days ago and now it seems to be working again. We were not able to see the auhorize.net menu at all. We do have the deactivation safeguards enabled.

Yes… new registrations are receiving the email with username/password so we are certain that WP does send emails.
We ran a test with a new user which we have the email for.

For some reason, there is nothing that is happening between Aweber/s2member

Any further insight?

woohoo! rock on. gonna give this a go. Thanks… will report our results.

Jason, and Bruce

Please close – this was a ARB subscription issue on our end. We have resolved the issue.

One things we updated S2 to the current version and we still only have to fields in the state space, we need a few more for our international clients.

Thank you very much guys!!! Great support – took us 4 days but we found the issue!!!

Jason,

Thank you a ton –

Here is what is up –

Right now we are going to do data validation in a few minutes via this link: http://developer.authorize.net/tools/datavalidation/

As soon as we find out why it is sending phone or whatever field we will let you know what the issue is.
This is only occurring on update, and Authorize is telling us it may be another field issue. We only need to update the CC.

As soon as we get this information back and do some work in the next few hours I will post what is
going on and if we need some assistance in the code.

Thanks in advance,

JB

This issue is only happening on UPDATE CC, not on the initial payment, so Authorize should have no bearing on it, as the initial sign ups are going fine. Our issue is only when someone goes to update a CC. (Thanks for the help)

Here are some pics:

The error

Our set up in Authorize

Again Thank you for the help :)

• This reply was modified 3 years, 11 months ago by  JB Glossinger.

As soon as you guys can provide any insight would be great, we’ve tried digging through the code but can’t seem to find where this would be. It’s preventing us from allowing users to update their information.

Again just to reiterate, this is specifically for the update billing form using
authnet pro forms and updates for ARB subscriptions.

Thanks again for the great work you do!

OK on it – and thanks so much will report back – :)

Some things we need to find out

1. Does S2 E-mail members letting them know that they have expired CC that needs to be updated, if so when? Does it do it through Aweber?
2. Our current system attempts to charge an expired card 8 days in a row before the account becomes invalid, Can we do the same with S2, if so how do we do that?
3. Does it send a confirmation e-mail that someone is cancelled? How do we know? Do we get an e-mail too?

Look forward to hearing from you soon, thanks.

Luis

Cristian,

Thank you, we are currently running a custom script – it charges the Auth.net ID on the date that it is due, so you called it. OK, got it.

Now, if the user already has a subscription running at Authorize.Net, what you can do is add Authorize.Net as the gateway and his subscr. ID to his profile. You can do that editing the profile manually, or with the Import tool if you use that to migrate the users or update them in bulk. Dashboard -› s2Member® -› Import/Export -› User/Member Importation

We don’t we use a custom script

If the user doesn’t have a subscription running with Authorize.Net and, instead, your custom script makes the charges and manages that, then they’ll need to start a subscription with Authorize.Net through an s2Member pro-form when you’re ready to migrate them from the old system to s2Member.

Maybe we can script that to happen? I REALLY don’t want 2000 members having to refill out a billing form……

Thanks for the help :)

• This reply was modified 4 years, 1 month ago by  JB Glossinger.
• This reply was modified 4 years, 1 month ago by  JB Glossinger.