First Data GGe4 Configuration

wldworks: If there one thing I've learned, don't PM them on the message board.

They always want you to go to www.hikashop.com/support/contact-us.html and submit a request there.

That goes into their ticket system - PMs don't and really don't get looked at ever from what I understand.
Really I think they might just disable that but not sure you can do that per user. It is a bad trap.

jazzmang wrote: wldworks: Yeah, I hat that problem with the hashes not matching too during my original testing/setup last year.

What jazzmang wrote is correct: "Actually I think I see what you might have done wrong. You used the Firstdata Hash Caculator to generate the "Your MD5 Hash on Authorize.net". That is NOT correct.

That is just a test calculation for debugging. You would manually enter the price, etc. and it would generate a value that you could then compare to what Hikashop generated. You don't need to do that at all.

The value you should enter into HikaShop Authorize.net plugin's "Your MD5 Hash on Authorize.net" is under FirstData's Payment Page's #9 Security -> Response Key. It is just below the Transaction Key."

That was one thing I had in my write notes as the key discovery. I made that same mistake last year when I was doing my original setup. The labeling is what is confusing (neither side matches the others) and I discovered it via trial and error and a hunch.

The support here is generally very good. I know sometimes they get on some bigger issues to work on but generally speaking I found nicolas and Jerome in particular to be helpful. But some days I think they would benefit from more of a full time support person here than pulling the devs away from coding. They are a small team but they know their stuff.

Still I think it might be time for an official "FirstData e4" or "Payeezy" payment plugin, or even an offical "wiki" support entery with all the key steps. It is why I posted my code file as well. Hope it works now!

OH MY FREAKIN GOD! ALL HAIL JAZZMANG.

So now I got it to work. So this is so confusing the response key needs to go where the hash id is in hika...

What you said made it work: "Actually I think I see what you might have done wrong. You used the Firstdata Hash Caculator to generate the "Your MD5 Hash on Authorize.net". That is NOT correct.

The value you should enter into HikaShop Authorize.net plugin's "Your MD5 Hash on Authorize.net" is under FirstData's Payment Page's #9 Security -> Response Key. It is just below the Transaction Key."

This "Your MD5 Hash on Authorize.net" is not the generated MD5 Hash on authorize.net but the response key...

Wow, finally. I hope this helps other people here. Thank you a million jazzmang.

wldworks: I'm curious, did you uses your own authorize.php or mine I posted here?

At this point, I'm not seeing any of the FirstData (Payeezy) orders getting recorded into Google Analytic Ecomm. reports.

Orders that use PayPal (standard) are recorded by Google Analytic just fine on the same site.

I'm curious if you are seeing the same thing.

I don't have any other sites that uses FirstData so noting really else to check against. Other sites that are using authorize.net directly seem to be OK however. So not sure if it is something with FirstData or on the custom authorize.php code.

Really that is my only issue left I think.

jazzmang wrote: wldworks: I'm curious, did you uses your own authorize.php or mine I posted here?

At this point, I'm not seeing any of the FirstData (Payeezy) orders getting recorded into Google Analytic Ecomm. reports.

Orders that use PayPal (standard) are recorded by Google Analytic just fine on the same site.

I'm curious if you are seeing the same thing.

I don't have any other sites that uses FirstData so noting really else to check against. Other sites that are using authorize.net directly seem to be OK however. So not sure if it is something with FirstData or on the custom authorize.php code.

Really that is my only issue left I think.

I used yours!

I haven't done the Google Nalytics Ecomm Reports because I am afraid that it's not going to work anymore. and unfortunately am on a live site. Again, thank you so much for your help

PS everyone, the latest update overwrote the authorize.php, which broke the plugin again. In case people are having issues. Maybe that just means that I shouldn't ever update... *sad*

That is why I mentioned having to do the modifications with each update.

It is also why I put in my suggestion/request as to why it might be time for an official payment plugin.

Obviously more sites are trying to use the First Data service.
Not like it would take a lot to create the plugin.

Alternative would be for some 3rd party developer to do so.

Unless it as simple as copying over the authorize folder to a new one named firstdata.
Never tried that. Not sure plugins are that simple in HikaShop.

Any ways, always backup the site before an upgrade for situations just like that.

So far my 2.3.0 code still works. I haven't hadn't had time to go back and make the 3.4.x code work, not enough time in the day.

nicolas wrote: Hi,

@wldworks: The updates always overwrite all the preinstalled plugins. Just backup the plugins/hikashoppayment/authorize folder before the update and back it up after that and it will work.

@jazzmang: You can't just rename the folder. You would have to rename the files too, edit the xml file and change the name there too, including the name of the files. Then, you need to edit the main file of the plugin and change the class name to use the name of your folder instead of authorize and change everywhere you have "authorize" in the file to the name of your folder.
Then, you can zip the files and install them via the Joomla installer.

Nicolas,

Couldn't you include that in the next release as the "new" payeezy payment plugin? That should be better than me trying to f***k everything up in the code.

It is really the same thing as what the authorize plugin is, with the authorize.php from jazzmang this thread above and renaming one field in the plugin that is called Your MD5 Hash on Authorize.net to Response Key

You can, but you don't have to, also rename "Login ID for Authorize.nett" to "Payment Page ID"

Somewhere in the plugin it should also say that your Receipt Link URL and your Relay Response URL should be the same and go as follows:
www.websitename.com/index.php?option=com...pl=component&lang=en (if it's going to called payeezy you probably want to call the notif_payment=payeeze)

I am offering my help to save other future people's the headache... Big thanks to jazzmang. Plus, I rather pay you a subscription to get support and updates, giving you a continued revenue stream, than not ever update the plugin again.

This would be an easy win/win for everyone and drive more customers to you...

The GlobalGateway E4, now called Payeezy Gateway, Plug In.

It's basically done, and no one would need to figure out how to use the Authorize.Net payment plugin for Global Gateway E4 and Payeezy Gatway. We have provided everything for it to be it's own plugin.

Thanks Nicolas, that doesn't seem too difficult. Just a matter of finding some spare time.

Can I post the plugin package here? I don't mind sharing as long as that doesn't violate any HikaShop licenses and not like I will be charging for it. Just don't expect me to keep it up-to-date or fix bugs

Hi Jazzmang, wldworks, etc..

1. I just setup Payeezy Gateway for a client and I get this error from their Error Submission Form:

The following errors were found:

* x_line_item # 1 - Taxable is too long (maximum is 3 characters)
* x_line_item invalid

when I have the 'Send details of the order' turned ON, yet I'd REALLY like to have that functional as the current layout of the
Payeezy Page without it is really not that inviting....

Just a line that says the Total of your Order is $ 1.00

2.Also I just received this:

Hello,
An Authorize.net notification was refused because the response from the Authorize.net server was invalid. The hash received was d05ef2868f0038be9836176ba5f7f053 while the calculated hash was 4D9B338F715D045BF52D0783A6FE4452. Please cehck that you're set the same md5 hash key in Authorize.net and the plugin

even though I have the Your MD5 Hash on Authorize.net in the plugin to be what the site has listed as: Response Key..

Any help would be greatly appreciated!

Thanks,
Cheers,

Emmanuel Lemor.

If you are using my file attached to one of my previous posts, you should be fine.

You get errors when ever you try to modify any of the newer authorize.net files.
Otherwise follow my conversation here with wldworks and you should be fine.

It is very critical you get the settings in Payeezy Gateway exactly right, that is where it is not clear on what the setting should because the language is not the same.

But my client is using the re-branded GGe4 to Payeezy Gateway just fine even after the latest upgrade to Hikashop.

Hi Jazzmang,

I have followed all of your edits/fixes that I know of reading through the 3 posts and 4-5 pages...

EVEN with making sure the:

The value you should enter into HikaShop Authorize.net plugin's "Your MD5 Hash on Authorize.net" is under FirstData's Payment Page's #9 Security -> Response Key. It is just below the Transaction Key."

I still get:

"Hello,
An Authorize.net notification was refused because the response from the Authorize.net server was invalid. The hash received was 9a9991f1f43aec7788b69b2e15422daa while the calculated hash was ABAEF807FB4EA6D1EEB864A06497B20D. Please cehck that you're set the same md5 hash key in Authorize.net and the plugin"

when I turn on Allow payment notifications from %s to YES

I didn't take your authorize.php file [couldn't really find it] but I did make the modifications:

Modified /plugins/hikashoppayment/authorize/authorize.php

1. x_line_item was fixed by changing the "has tax" values from True / False to Y / N around line 242 and 244

2. x_relay_response was fixed by enabling and configuring the authorize.net protocol - relay response settings in the FirstData Gateway control panel.

4. x_test_request this value was set to $debug I changed it to 'FALSE' around line 192 < ---- this was ALREADY changed by Hikashop.

Any help would be great on what else I need to do to get it to work....

ALSO if you see the Checkout page attached I don't get Item names ;( [with Send Details of the Order = Yes which would be really nice for the client]

Thanks,

Emmanuel Lemor

For file see post www.hikashop.com/forum/payment-methods/8...guration.html#196441 .

Like I said, you cannot modify the new authoriz.phpet file and make it work with the changes here.
You need to modify an older version (mine is based off 2.3.0 version).

HI Jazzmang,

You rock, I took YOUR file and it now confirms orders the ONLY thing left it seems/that still isn't working is:

the Item Description is not going across to Payeezy with Send Details of the Order ?

As you can see in the image attached...

Any clues/thoughts?

That is normal.

I'm not aware of any option for it to display cart items on their end. It is strictly quantity and $ totals.

Hi Jazzmang,

Thanks for the input but then why does using the 'normal - non-edited' Authorize.net plugin on a different website with Authorize.net ----> the item descriptions work fine..

See thumbnail attached.

Cheers,

Emmanuel.

Not a question I can answer.

Keep in mind that Payzeey is not an exact clone of Authorize.net.

The calls may be close, but they are not exact (otherwise all these hacks wouldn't be required).

It could also be something that Hikashop implemented only in later versions or something that was just specific to authorize.net.

Either, not something I find to be an major issue or concern.
If one wants Authorize.Net functionality, then use authorize.net