[SOLVED] Auto Renew

jingato wrote:

ok, Do you plan on implementing the authorize.net callback at all? If so, how long do you think till you do?

also, when users log in will they have the ability to update there payment information, like changing to a different credit card.

Post edited by: jingato, at: 2009/04/18 18:20

Paypal's API is very complete.

authorize.net ARB's API is not as complete, and does not allow all of this.

There is a new API which came out at authorize.net after we developed the authorize.net gateway, but which has a heafty extra-cost and approval-process, so we guessed that it would be way less appealing for now.

We are currently planing to implement the "silent callback" from authorize.net in next features-release 1.1.0, but it will just tell if card could be charged or not.

AIM and payments with our authorize.net gateway are complete and do check fine for transactions.

Also for subscriptions, we do not use ARB alone, but also AIM for the first payment, so that we are sure that credit-card is valid.

For now in AIM+ARB autorecurring auth.net payments: authorize.net sends an email in the unlikely case a further transaction gets declined, and the backend admin interface allows to adjust the subscription accordingly.

In paypal: everything is fully automated as we implement the full webpayments api.

beat wrote:

jingato wrote:

ok, Do you plan on implementing the authorize.net callback at all? If so, how long do you think till you do?

also, when users log in will they have the ability to update there payment information, like changing to a different credit card.

Post edited by: jingato, at: 2009/04/18 18:20

Paypal's API is very complete.

authorize.net ARB's API is not as complete, and does not allow all of this.

There is a new API which came out at authorize.net after we developed the authorize.net gateway, but which has a heafty extra-cost and approval-process, so we guessed that it would be way less appealing for now.

We are currently planing to implement the "silent callback" from authorize.net in next features-release 1.1.0, but it will just tell if card could be charged or not.

AIM and payments with our authorize.net gateway are complete and do check fine for transactions.

Also for subscriptions, we do not use ARB alone, but also AIM for the first payment, so that we are sure that credit-card is valid.

For now in AIM+ARB autorecurring auth.net payments: authorize.net sends an email in the unlikely case a further transaction gets declined, and the backend admin interface allows to adjust the subscription accordingly.

In paypal: everything is fully automated as we implement the full webpayments api.

But see, the problem is, I'm creating a very high end site for a client and he doesn't want the users to have to #1 be forwarded to another site to pay. He wants it to be all on his site. And #2 require signing up and creating a paypal account, which I assume is necessary since it's subscription based.

I know with paypal you can use paypal pro and do everything on your site like any other processor. But what about subscriptions. Is it possible to charge for a subscription without leaving the site and can that subscription be managed without having a paypal account?

Do you have any idea when 1.1.0 will be released? Are we looking at months?

Thanks again

John

jingato wrote:

beat wrote:

jingato wrote:

ok, Do you plan on implementing the authorize.net callback at all? If so, how long do you think till you do?

also, when users log in will they have the ability to update there payment information, like changing to a different credit card.

Post edited by: jingato, at: 2009/04/18 18:20

Paypal's API is very complete.

authorize.net ARB's API is not as complete, and does not allow all of this.

There is a new API which came out at authorize.net after we developed the authorize.net gateway, but which has a heafty extra-cost and approval-process, so we guessed that it would be way less appealing for now.

We are currently planing to implement the "silent callback" from authorize.net in next features-release 1.1.0, but it will just tell if card could be charged or not.

AIM and payments with our authorize.net gateway are complete and do check fine for transactions.

Also for subscriptions, we do not use ARB alone, but also AIM for the first payment, so that we are sure that credit-card is valid.

For now in AIM+ARB autorecurring auth.net payments: authorize.net sends an email in the unlikely case a further transaction gets declined, and the backend admin interface allows to adjust the subscription accordingly.

In paypal: everything is fully automated as we implement the full webpayments api.

But see, the problem is, I'm creating a very high end site for a client and he doesn't want the users to have to #1 be forwarded to another site to pay. He wants it to be all on his site. And #2 require signing up and creating a paypal account, which I assume is necessary since it's subscription based.

I know with paypal you can use paypal pro and do everything on your site like any other processor. But what about subscriptions. Is it possible to charge for a subscription without leaving the site and can that subscription be managed without having a paypal account?

Do you have any idea when 1.1.0 will be released? Are we looking at months?

Thanks again

John

John, if you really need that urgently and have a real budget to co-sponsor a priority-implementation of that new auth.net feature, please PM me to discuss details. To PM: press icon at bottom left of post, and please add URL to this topic, so we can relate to it.

Well, we actually wont be needing it for about 6 months. Membership is going to be free for a while when the site launches. Hopefully that would be enough time to get the newer version of the authorize.net plugin. The sooner the better, just so we would have it in place and ready to go. If you didn't plan on having it implemented by then let me know. I might be willing to get the client to sponsor the plugin creation.

Thanks

I wanted to follow up and find out if there are any changes in the Authorize.Net API. We are currently using Authorize .Net to handle reoccurring subscriptions. Is there anyway for a user of a reoccurring subscription to change their credit card information?

Janis Kupferer wrote:

I wanted to follow up and find out if there are any changes in the Authorize.Net API. We are currently using Authorize .Net to handle reoccurring subscriptions. Is there anyway for a user of a reoccurring subscription to change their credit card information?

Unfortunately at this time, no. However, it is a planned feature to be implemented.