Authorize.net AIM method

[Eric Caldwell]

Hi, I'm evaluating the new 2.x for a client. After installing the Authorize.net payment gateway and when clicking the payment link in the invoice, your routed to an nBill page to click submit. After clicking submit, your taken to an AN SIM page.  Per the nBill website, I see that you mention the AIM integration but, I can't get it to work that way.  The client is setup on my server with a dedicated IP and valid SSL certificate as well.

Thanks.

[Eric Caldwell]

Figured it out. Turning on the Joomla SEF caused the problem.

[netshine]

SEF should not cause a problem - lots of sites use both SEF URLs and the auth.net gateway with AIM. If you would like me to look into it, please submit a support ticket.

[Eric Caldwell]

Does the nBill lite not support the Authorize.net AIM feature?

[Eric Caldwell]

Just figured that one out too..  You have to create logins in order to use the AIM method. If you don't use logins to pay invoices, payments are handled via SIM from there?  If using the SIM method, how do you get the AN extension or AN for that matter to mark the invoice paid?

[netshine]

Being a logged-in user should make no difference either. Whether to use SIM or AIM is based purely on whether the port used is the same as the SSL port defined in the gateway settings. If your server uses a non-standard port for SSL, you need to enter that port number in the gateway settings. The default port number is 443, but some servers use port 80, and some might use a different port number altogether (if it doesn't work with either of those, ask your hosting company which port they use for SSL).

It looks like the SIM protocol might have changed since the auth.net gateway was first written, so the callback does not happen or does not get recognised by nBill and the invoice therefore is not marked as paid automatically. This is something I will look into when I have time, but in the meantime, using SSL and AIM is recommended.

[Eric Caldwell]

That is what's happening on this site, if you login you can pay via AIM. If your not logged in, nBill lite defaults to SIM.  If SIM is used, then the transaction will not mark as paid.  We do use the standard SSL port 443 on our server    We have a few dozen ecomm sites with SSL certs.  We used nBill to run our company until we out grew it and had to move to WHMCS but, that experience is what drives me to recommend nBill for clients who need a web based billing solution and we only build Joomla sites

If you would like to login and check this out, I can PM you with the information?

Thanks!

[netshine]

Please do, or e-mail support@nbill.co.uk.

[Eric Caldwell]

Emailed

[netshine]

Thank you. I found nothing wrong here. I think the problem is that you are using URLs starting with http to access nBill Lite, so it is defaulting to SIM. You have the 'switch to SSL on login' option turned on, so when the user logs in, they are redirected to the https address, and AIM is used. But even if the user is not logged in, as long as nBill is accessed using https, AIM is used. In the standard edition, version 2.1.1, there is a new option to automatically switch to SSL for ALL nBill pages, which is ideal for use with the auth.net gateway. The Lite edition does not have this option though, so you just have to make sure all links pointing to nBill pages start with https.