Jump to content

IP.Nexus 1.5 Dev Update: Gateways & Payments

IP.Nexus currently provides support for a number of gateways: Authorize.Net (with ARB and CIM support), PayPal (Website Payments Standard and Pro), 2CheckOut and manual payments (check, bank wire, etc.)

In IP.Nexus 1.5 we're adding more gateways and extending the functionality of some existing gateways.



Stripe is a relatively young payment gateway. They support all major cards and have no monthly or setup fees which makes them great for smaller companies wanting to accept card payments.

One of the more interesting aspects of Stripe is that they have a clever solution where although the customer can enter their card details right in Nexus, these details never actually hit your server - which is great for security.
Those interested in the technicalities of this - the card form elements are displayed without having a 'name' attribute, meaning that their values are not sent in the POST data to your server. Instead, Javascript on Stripe's server extracts these details and provides Nexus with a token which is what is then sent.

In addition, Stripe supports "storing" card details (again, technically, Nexus only actually stores a token) meaning when paying your customers will be able to tick a box to save card details, and these details can automatically be used for renewals, future purchases, etc.

Authorize.Net DPM

Nexus already provides support for Authorize.Net's AIM (that's "Advanced Integration Method") service. This allows customers to enter card details directly into Nexus.

The way this works is that the card details have to be sent to Nexus - this is a concern for some as it means that, even though it's very briefly, your server has the customer's card information, which means that certain security precautions need to be considered.

Authorize.Net now have a new service called DPM ("Direct Post Method") - to the customer, this seems to work exactly the same, however, rather than posting the card data to your server, and then Nexus sending that data to Authorize.Net, the form submits directly to Authorize.Net's server - meaning your server never deals with the sensitive card information.

Unfortunately, due to the way this works, Authorize.Net's ARB and CIM services (both of which are a form of recurring billing) are not compatible with DPM. Those who need recurring payments can keep using the AIM method.


Nexus 1.5 also adds support for Sagepay.


Currently, Nexus allows you to refund transactions right from the Admin CP for Authorize.Net and PayPal transactions.
In IP.Nexus 1.5, PayPal Pro and 2CheckOut can now handle this too. Authorize.Net DPM and Stripe, which are added in 1.5, also support it.

2CheckOut Improvements

2CheckOut payments are now handled with their INS service. Not only is this more secure and reliable, using it has also allowed us to add support for recurring payments.

So where does that leave us?

IP.Nexus now supports 7 different payment gateways (8 if you include manual payments like check and bank wire), each of which have their own features and merits over one another.

We've created a little table to show the key differences between each gateway:

As always, we'll continue to gauge interest and add additional gateways to Nexus over time.

But wait.... there's more!

Split Payments

Sometimes, people might want to pay for an invoice using two different cards (or other payment methods). In IP.Nexus 1.5, this is now possible:

You can set a minimum invoice amount before this feature is available, or disable it completely if you don't want to use it.

Package Methods

In IP.Nexus 1.5, you'll now be able to set which payment methods can be used to purchase a particular package:

  • Create New...