CiviCRM Community Forums (archive)

Hello All,

We have a client that really wants BluePay as a payment processor.

BluePay has an authorize.net emulator.

The BluePay authorize.net emulator requires that the existing CiviCRM Authorize.net module that is currently in place uses the Authorize.net AIM (Advance Integration Method) module.

So the big question is, Does it?

GF

BluePay Gateway Interfaces Documentation: https://secure.assurebuy.com/bluepay/
BluePay Authorize.net AIM Emulator (a.net) Documentation
https://secure.assurebuy.com/bluepay/BluePay_a.net/BluePay_Authorize.net_Emulator.txt

Eileen, thank you for your reply.

As Civi uses AIM, my understanding is that to add BluePay as a payment processor, what needs to happen is that the authorize.net module gets cloned & edited as documented in
https://secure.assurebuy.com/bluepay/BluePay_a.net/BluePay_Authorize.net_Emulator.txt
Doesn't sound too tough.

I suppose we can get a quote to have it done by a third party. But then how do we get it put into core? Having our customizations hacked into core, for only our clients, is a nightmare.

And I think this extension only makes CiviCRM 'more better', deserving to be in core.

Perhaps someone knows who maintains the authorize.net code. Perhaps that maintainer can contact us. Perhaps we can come to some kind of financial agreement. It could avoid the whole customization hacked into core (as the authorize.net maintainer is undoubtedly an 'approved' programmer and can slide bluepay into core)--and when the authorize.net code is updated, the bluepay could be updated by the same maintainer.

I'm thinking this might be small enough that we can do it without the whole 'thermometer' call for funds...

Thanks,

GF