There are some changes in the Authorize.net API on which we are working right now. We will update you here once done.
Thanks for the update. I need to switch back to non-recurring packages now until its resolved.
Just checking in. Any idea on eta?This reply has been marked as private.This reply has been marked as private.This reply has been marked as private.This reply has been marked as private.
I recently updated to v1.0.8 because the changelog showed that the recurring subscription was fixed.
I’ve tested and finding that my card was charged twice. Currently one transaction has posted and the other is pending, according to the bank.
And authorize.net shows 2 transactions for me. Both of them are currently showing as settled.
I do confirm that only 1 recurring subscription was created in Authorize.net.
In addition, we have customers who try to renew via the invoice email, and they are getting this message:
Error: The invalid invoice user id
Client is losing patience and considering alternatives.
I have changed the settings for Authorize.net transaction type for recurring to Authorize only and let authorize.net handle it. Can you please check if it fixes your issue or not?
which issue would that fix? being charged twice or invalid user id?
It should fix being charged twice. For invalid user ID issue, it is required to login by the user to pay the invoice as invoice compulsory needs user ID.
how can we set a login redirect?
also, if it’s set to authorize only, will the client have to process the transaction manually in authorize?
So it’s a bug? Any ETA?
To force user login before paying an invoice you can enable setting “Require Login To Checkout” in Invoicing->Settings->Misc. This will not redirect but will show a message to login.
Can you try one transaction with that setting? I think it should automatically process via authorize.net.
You must be logged in to reply to this topic.