Prosperative Public Forum

Payment - Best Move of 2015

0 Members and 1 Guest are viewing this topic.

Payment - Best Move of 2015
« on: November 30, 2015, 08:50:58 PM »
Adding the Zaxaa payment system was the best move Jon did in 2015! I've been waiting all year to purchase Article Builder and even tried hiring it's Rep as a middle man to purchase the product bypassing PayPal since I was Blackballed from that crappy payment system. Once I saw I was able to purchase AB using my credit card, I jumped on the opportunity. Now I'm a happy new user since yesterday and hopefully my websites will all start benefiting from utilizing AB's use.
Cheers to all of use that have another option other than crappy PayPal to purchasing AB and Jon's other fine products.

PS: Jon, if you happened to catch this thread, it might be beneficial to email everyone and let them know about you adding this new payment service. I'm not sure when it went active, but if I had gotten an email informing me about this, I would have purchased it instantly.

Re: Payment - Best Move of 2015
« Reply #1 on: December 01, 2015, 04:34:51 AM »
Did you get the access instantly or if not, how much time needed for the access details. I paid a few days ago by cc but still have not got the access .

Re: Payment - Best Move of 2015
« Reply #2 on: December 01, 2015, 08:12:55 PM »
It took them 5 days before I got my access via an email they sent. But I believe that might only be because I put in a help ticket here: - so hopefully you did that otherwise it might take a lot longer then what it took me.
Best of luck to you.

Offline Jonathan Leger

  • *****
  • 8863
  • Here's to your success!
    • View Profile
    • Jonathan Leger's Blog
Re: Payment - Best Move of 2015
« Reply #3 on: December 02, 2015, 07:44:45 PM »
I'm glad you're finally in, and yes, I plan on emailing the list to let them know that we have a PayPal alternative for all of the tools and services.

When we first added Stripe (the PayPal alternative) there was a glitch that prevented sales from being logged in the database. That only lasted about half a day before it was fixed, but it's possible it affected you too.