Authorize.net Hack

[DivisionByZero]

Ok, here's the deal...

I'm trying to port a hack I wrote for 3.0.7 that worked seamlessly. It's located in this thread: https://vborg.vbsupport.ru/showthread.php?t=66178 This one also had authorize.net e-check support in it. Worked like a champ!

Since 3.5.0 was wrote with no regard for backwards compatibility, I've found myself pulling my hair out over this one. :devious:

So far, I've done the following, which works ok:

-- made two copies of the API rows in the database, renaming each to reflect CC and ECHECK support.
-- made two copies of the /includes/paymentapi/classes, renaming them respecfully.
-- made templates for the payment form
-- wrote a checkout.php file that handles all the post data, and communicates with the gateway via cURL and retrieves the data that payment_gateway.php?method=authorizenet normally would.
-- copied the contents of payment_gateway.php into my checkout.php file right after the cURL session has closed.

my checkout.php would then require the same files as payment_gateway.php does, and would build the subscription (or delete it) accordingly

The problem I'm having is, when I look in payment_gateway.php, i can't figure out how to serialize, arrange, or assign the POST data to a variable so that it can continue.

So, since the relay response from auth.net uses POST data, how do I convert that data to where payment_gateway.php would parse it?

Any help would be appreciated, so I can get this hack posted


Thanks

[betterman]

Did you ever get this working? I hate the default authorize.net setup, would love to have a fully integrated method. I'd be happy to throw you a few bucks if you've got this working for 3.5 and will share.

Thanks!

[DivisionByZero]

I am about 80% complete with this for 3.5.3. I had it all up and working for 3.0.7 with NO problems, but they changed everything around in 3.5.x so i'm having a hard time implementing it.

I'm doing eCheck support too, so I want to be able to pick and choose WHO gets to use eCheck becuase you know the rate of chargebacks is high because ACH with authnet provides no AVS or Fraud Detection Suite coverage.

I'm trying to set it up to be as configurable as possible... i.e:

• Certain usergroups can use eCheck
• Certain users can use eCheck
• Abillity to set the enable flag for anyone who has made X number of successful payments
• Ability for the module to do its OWN recurring billing (mcrypt supported PHP installs only, because this stores the CC info in the db)

I've also added a nice layout for filling out a "blank check" in the eCheck part of it, and this requires the "Numbers_Words" pear module because this fills in the written dollar amount in the check.

I'll just get it up and running for now with basic features, and i'll add the toys in later, since you're interested in this too.

oh... and for this to work, you'll need to make sure you're HTTPS wwwroot is the same as your HTTP wwwroot. 2 separate vb installs don't work well with this. HTTPS is necessary for a: the protection of your members' personal data (duh) and authnet won't accept non SSL transactions

[betterman]

For now I only need the CC support, but eCheck would be a great addition. Recurring billing would be excellent, as well.

Please let me know what I can do to help.

Thanks,

Rob

[betterman]

Originally Posted by betterman

For now I only need the CC support, but eCheck would be a great addition. Recurring billing would be excellent, as well.

Please let me know what I can do to help.

Thanks,

Rob

Any update?

[grayloon]

I'd love to get my hands on this puppy! How close are you to release date?

[wolfyman]

anyone get this working?

More importantly... working on 4.x?

[Marco van Herwaarden]

This forum is not about vB4.

[wolfyman]

Thanks Marco