I have to agree with Jim Rising. The "implementation" is giving the user access to the secure URL address to redirect the payment information to a different gateway. In point of fact, we are trying to use NMI and would be able to with the Auth.Net setup if we could change the URL.

Also, I disagree with the statement: "implementing such emulators is actually the same amount of work as working with other payment processor using native API."

I have developed multiple gateway integrations, and the authorize.net emulator implementations are nearly identical to the native gateway apis. That's kind of the point.

If your software has good separation, you should be able to almost copy your authnet code verbatim.

This is another request for support of authorize.net emulation. There are several popular gateways that use this ... NMI, USAePay, InstantMerchant ... are three examples. It is literally a matter of giving developers the ability to populate the gateway URL.

@Walt: Authorize.Net emulator is some other payment processor that uses Authorize.Net API to work with. So we have "genuine" Authorize implemented, but as Evgeny has noted earlier we are not going to support any other payment systems using Auth.Net API soon.

Main reason for this is that implementing such emulators is actually the same amount of work as working with other payment processor using native API.

So if you want some specific payment system implemented - please create a corresponding idea for it.

Oleg aka ONe Apricot @ Payments team

@jean - Go to Settings - Finances - Payment settings - Edit and look at the dropdown list of payment processors.

@Apricots - I see authorize.net in the list, so shouldn't this be marked as implemented? (And thank you.) :)

Do you have a complete list of the other payment processors you have in your queue?

I got a response from our developer (expert in this area). He basically says, that from his point of view this is a low priority request comparing to other payment processors we have in implementation queue.

I have forwarded all the details to our developers and as soon as I have an update, I'll let you know. This may take time.

We use Network Merchants LLC (NMI). I'll send you a message with a bit more info on how they say it works.

What is the specific system you're using?

I understand that changes are frequently more complicated than we users comprehend but I was told by someone on the authorize.net emulator side of the process that all that needed to be changed was the website that was pointed to. If we could use this for our renewals and new member applications it would make life much easier for us. To add a new online payment service for this function would be cost prohibitive. Please reconsider. Thanks.

I discussed this with our development team and it looks like we're not going to support Authorize.Net Emulators.