I'm excited to announce a new module that I have started building tonight!

The Authorize.net Suite module is the first payment gateway module to be developed for Typolight. It will feature both Advanced Integration Method (AIM for short) and Simple Integration Method (SIM) modules, and in the future, the Customer Information Manager (CIM) and the Automatic Recurring Billing (AR module as well.

Authorize.net is one of the largest payment gateway providers on the internet. If you have a merchant account in the U.S., it is likely that Authorize.net is your gateway service provider. I've worked with Authorize.net over the years and have always been happy with their service and support and pricing. All their payment gateway solutions also meet PCI-DSS (Payment Card Industry Data Security Standards specifications).

This thread is the place to offer feedback on this module, as well as receive support for bugs or integration issues, if any.

I look forward to hearing your feedback for this module. for more information on Authorize.net, visit their website at http://www.authorize.net

Cheers,

Fred

Hi fbliss,

Is it possible in the future when you will finish the Authorize .net module, to have a paypal module ?
In France we use more Paypal than Authorize.net...

Awesome,

Wish we could implement a few of the swedish payment options later on ;-)

I've made a payment API bridge a few yrs ago for an e-commerce system, I will look at this later on aswell. This is also one thing that really could boost TL, along with a nice cart aswell.

Hi Cyril,

I realize paypal is probably the more popular choice, so that is on the short list. I will try to get to that next, unless someone wants to do it ahead of me. The Authorize.net module is being built right now over other things because I need it for a project, so I will release that hopefully in the next week or two.

Keep the great feedback coming, guys!

Fred

Feature Set

Current Features

- AIM (advanced integration method) Style Gateway Connection (requires an SSL installed on your server)
- Maintain multiple checkout configurations (this will enable testing of new features/changes while leaving your current configuration alone)
- In-depth Explanations of various settings as provided by the AIM developer's integration manual
- Front-end module to insert a checkout module into any page you choose

Features to come

- eCheck support
- Refund and Void Transaction tool (back end) for administrators
- Full optional feature support (refer to the Authorize.net AIM integration manual at http://www.authorize.net)
- SIM (Simple Integration Method) style connections (for people who do not have an SSL installed on their server)
- CIM (Customer Information Module) integration
- ARM (Automatic Recurring Billing) module integration

Fred

This sounds very interesting Fred! I will follow this development closely and try to get it to work easily with our swedish way of card payment.

Cheers,

Hi AZ,

I love the idea of a single module supporting multiple payment processors. If we can find out what things are consistent between each processor, we may be able to save a lot of work by doing this, but it would be quite a project! You might be able to adapt the swedish payment processor to it, though it is built specifically to the requirements authorize.net has.

Hi everyone,

Just wanted to let you know that the first Authorize.net module (AIM integration of the front end member registration process) is now operational! It is rudimentary, but it works nicely. I will set up a demo of it in the next 3-5 days so you all can play with this prototype version.

Take care,

Fred

Hi Fred

Any news on this or on the upcoming Product Catalog app?

Hi Thyon,

Yes, Andreas Schempp and I have been working on the e-commerce package now for a while, Andreas has done a ton of work to improve and clean things up, and while the last 10 days for me have been of minimal work on the project, I should be back on it much more this week. No idea of a timeline except to say that this summer, for sure, we'll have something put together. Just not sure about the how in releasing it. Open source yes, but we're going to try and put together a focus group to help us get it to release mode before it becomes widely available. We want it to really work well when it comes out.

Hope that answers some questions!