Authorize.net Accept.js Buggy

[brianemwd]

Is anyone using the Authorize.net Accept.js with no problem? We moved to this gateway several months ago from the standard WHMCS Authorize.net payment module and we continue to have problems with this module. The documentation stated the migration process to Authorize.net Accept.js was supposed to be seamless and we found it was not. We have seen the following behavior:

1. While most credit card information data is migrated to Authorize.net Accept.js at the time of payment processing, about 10% of them are not.

2. The migration process is supposed to remove the old card information from the WHMCS database. For about 10% of those successfully moved to Authorize.net's CIM, the old credit card information still remained behind and we have to remove it from the admin side as the client side does not display it.

3. We are still having problems with trying to apply manual payments to invoices with the following error: Error Message => Customer Profile ID or Customer Payment Profile ID not found.

This typically happens to accounts that have 2 or more payment methods setup. When trying to use the other payment methods, we receive the same error and end up having to remove ALL of them. This then has the client having to log into their client area in order for them to recreate their payment methods. This is causing headaches with our clients where before we had NO PROBLEMS at all using the older Authorize.net gateway.