First Data GGe4 Configuration

ok I found that whatever item id I enter, I still get that same error.

However, if I take Allow payment notifications from %s to No in the Authorize.net hikashop plugin, then i dont get an error BUT there is no confirmation.

I also checked my menu entry id for hikashop and it is 771 but when i click on checkout it shows me

http://websitename.com/component/hikashop/checkout?Itemid=721

Any idea why I don't get a response back? and my email above?

Here is what it looks like when I buy something at my store:

After I click on the link, I get redirected back to the regular thank you page.

When I enable it, I get the following error from FirstData in an email:

x_relay_url : Invalid x_relay_url. Must be the same as configured for the
payment page

The parameters of the request are

'x_address' : street
'x_amount' : 4.95
'x_city' : Bellevue
'x_company' :
'x_country' : United States of America
'x_currency_code' : USD
'x_customer_ip' : 162.211.217.4
'x_email' : This email address is being protected from spambots. You need JavaScript enabled to view it.
'x_first_name' : firstname
'x_fp_hash' : 1d41cbXXXXXXXXXXXXX71ed9b
'x_fp_sequence' : 58
'x_fp_timestamp' : 1426052392
'x_invoice_num' : 58
'x_last_name' : lastname
'x_line_item' : 30DPJ<|>30 Day Daily Practice
Journal<|><|>1<|>4.95<|>N
'x_login' : WSPxxxxxxBCGQ
'x_logo_url' : http:/xxxx.com/images/xxxx-logo.png
'x_phone' : 123 123 1234
'x_po_num' : 58
'x_relay_response' : TRUE
'x_relay_url' :
websitename.com/index.php?option=com_hik...t&lang=en&Itemid=721
'x_ship_to_address' : Address goes here
'x_ship_to_city' : City
'x_ship_to_company' :
'x_ship_to_country' : United States of America
'x_ship_to_first_name' : Firstname
'x_ship_to_last_name' : Lastname
'x_ship_to_state' : Washington
'x_ship_to_zip' : 98004
'x_show_form' : PAYMENT_FORM
'x_state' : Washington
'x_tax_exempt' : TRUE
'x_test_request' : FALSE
'x_type' : AUTH_CAPTURE
'x_version' : 3.1
'x_zip' : 98004

When I disable it I get paid but not response back

So what should the link be? because you said i am using & instead of using &, which doesn't make sense to me. I am confused

http://websitename.com/index.php?option=com_hikashop&ctrl=checkout&task=notify&notif_payment=authorize&tmpl=component&lang=en&Itemid=721

I see, now when you put it in code view that makes sense.

I put in

http://www.xxxxx.com/index.php?option=com_hikashop&ctrl=checkout&task=notify&notif_payment=authorize&tmpl=component&lang=en&Itemid=721

http://xxx.com/index.php?option=com_hikashop&ctrl=checkout&task=notify&notif_payment=authorize&tmpl=component&lang=en&Itemid=771

Hi,

I think that the "www" can cause an issue. Please specify the live_site url in the configuration.php file of Joomla, and for the use of the www or not in the htaccess file based on the value used for the live_site.

What about the item id?

Good and bad.

Ok so I took of the www on all links in first data and i changed the item id to 771, I also turned on allow notification from %s which allowed me to go through to firstdata without an error. Now the problem is coming back to the site i get an error. The payment also went through successfully but I got a page back that says: Invalid notification.

I just received a hikashop error:

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

But the hash it shows in first data is this one: 3cf4e6f4dxxxxxxxxxxxxxxxxx1457db
Which is also the one I have in the payment plugin...

What is going on?! I just want it to work and am growing frustrated...

Do I have to regenerate some kind of token every time i change the reciept url or what?!

Anything? Support?

Today I upgraded to 2.4 from a working version of 2.3.5.

In previous upgrades, I originally just kept my modified version of authoirize.php from Hikashop v2.3.0

This upgrade, I decided to use the new 2.4.0 authorize.php and modified it accordingly.

As soon as I did that, FirstData started providing Invalid messages on their end and the cart showed declined.

NO other changes were made any where else.

Then I pushed my my old 2.3.0 modified version that had been working fine and it works again.

I have attached my modified 2.3.0 version.

I'm not sure what all the differences are between the 2.3 and 2.4 versions are but it is enough to cause breakage.

Also note that for my Relay Response URL I"m using (using " &" in my URL either):

https://www.xyz.com/index.php?option=com_hikashop&ctrl=checkout&task=notify&notif_payment=authorize&tmpl=component&lang=en

https://www.xyz.com/index.php?option=com_hikashop&ctrl=checkout&task=after_end&order_id=###

wldworks,

One setting I have different from you in my HikaShop's Authorize.net plugin settings is I have "Allow payment notifications from %s" set to Yes.

I also don't set the logo URL as I found I could set that in FirstData's end and I don't think it worked any ways.

I've reviewed my FirstData setup and other than the Relay Response URL I've already mentioned above, everything looks the same.

I Know this is very frustrating. I really wish there was a true GGe4 hikashop plugin so I didn't have to do this modification with ever update. It is a real pain when you have to do something like this for just one site.

jazzmang wrote: wldworks,

One setting I have different from you in my HikaShop's Authorize.net plugin settings is I have "Allow payment notifications from %s" set to Yes.

I also don't set the logo URL as I found I could set that in FirstData's end and I don't think it worked any ways.

I've reviewed my FirstData setup and other than the Relay Response URL I've already mentioned above, everything looks the same.

I Know this is very frustrating. I really wish there was a true GGe4 hikashop plugin so I didn't have to do this modification with ever update. It is a real pain when you have to do something like this for just one site.

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

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!