TOPIC: Payment gateway for Australia

Anyone interested in joining forces to pay a developer to make DT Register work with eWay so us Aussie's can use DT Register!!?

We're ready to get this done ASAP.

Nick
Aussiecom Internet Consulting
Sydney web development, hosting and SEO - http://www.aussiecom.com.au

Yes we would possibly be interested.
We are a not for profit organization operating in New Zealand so I need to confirm that eWay can offer the services we require.
Any indications of costs?

The DT Register developer has quoted it as US$200, so this would be divided amongst whoever is interested.

If it's just us 2 it's US$100 each (which I'm happy with).

Let me know if you're interested.

Once we can pay the total (US$200) we can have eWay integrated within 1 week.

Hopefully there are another 1-2 people who also want eWay integration which will bring the price down to US$67 or US$50 each.

Anyone else in Australia or NZ using DT Register and keen for eWay (ie. credit card payments) integration? Let us know...

Nick
Aussiecom Internet Consulting
Sydney web development, hosting, SEO, Adwords
www.aussiecom.com.au

I am very interested.
I just need to do some more research on eWay costs before we make a final decision.

I have questions though....

If we pay then does this become functionality only the payers can access or does it then get released publicly?


Why do we need to pay such an exorbitant fee seeing though this was meant to be integrated years ago? We've had so many promises that this would be done which I believe justifies there is a problem with this feature which is why it hasn't been done to begin with... I'm just sceptical!

First - the fee is very small. Custom development for an extension is generally much more expensive than that. We made it that cheap though because it would help the overall extension as we would add it to the package for everyone.

You would want it added for everyone anyway, otherwise you'd have to re-implement it with every new update of DT Register.

Second - there is no problem that has prevented eWay integration to this point. We have continually added so many new features on a regular basis... and they mostly come from high user demand or people paying to get a feature added. When someone contributes towards a feature, it gets added now rather than later. So eWay hasn't been added yet just because it hasn't made it to the top of the list yet.