This is an importance and we don't want any to feel it is not as such. It's going to take a lot of implementation due to CBSubs to begin with not having billing address support. Continuing to slam the issue is not helping, just costing us time to reply with the same responses over again.

However, it's not top priority because a feature is already in mid development, if you've ever developed a project then half way through implementing something you decide to implement something else you would understand the severity in damages this can and generally will cause. It certainly won't happen overnight, but we're working as diligently as possible and gratefully respect your patience.

An alternative is to switch to Paypal for the time being, in all due respect the payment gateway should handle billing address (as Paypal does), but Authorize.net allows on-site purchases and there is where the problem is. As far as my knowledge extends it was developed initially for Paypal and Authorize.net was added afterward.

EDIT: changed subject back to thread subject

Post edited by: krileon, at: 2009/10/08 14:16

Again, I understand your frustration, but you appear to not have read the entirety of my reply.

...if you've ever developed a project then half way through implementing something you decide to implement something else you would understand the severity in damages this can and generally will cause...

We are avoiding further bugs and complications by finishing what we've started instead of starting multiple developments at the same time.

It sounds so simply to just pass invoice address information, but nothing is as simple as it seams. We prefer to implement a method intended for this purpose instead of a hack job fix. Again, we're working as diligently as possible and again hammering at this thread is not going to make it be completed any quicker.

We truly do understand your frustration, but please also understand ours when we're constantly bombarded on an issue we're already working to address.

We don't set time lines as that's generally setting up a highway to disappointment and angry users; development changes constantly and there's no telling what could delay the development. Maybe someone had a family crisis, maybe a few bugs got in the way during implementation, it's impossible to predict such a thing. The best I can give you is "when it's ready".

Setting up a Paypal account and confirming it to premier status takes 1 day and is free, of course there is transaction charges with any gateway. Authorize.net IS supported, but just not supported enough to your satisfaction. I understand this may not be an acceptable solution, but I am trying to give you an alternative until this issue can be resolved.

EDIT: changed subject back to thread subject

Post edited by: krileon, at: 2009/10/08 14:17