AbleCommerce Shopping Cart Software

Hello,
My company is using Payeezy for the transaction gateway. We are receiving a "Transaction Normal" error when trying to process a credit card order. I have attached a screen shot. Previously, we were getting a "Remote host disconnected during SSL negotiation" error when using "Test Mode" and that was because TLS 1.2 wasn't configured on our server. We verified with Payeezy that the "Live Mode" should not use the TLS 1.2 protocol. Any help on this would be greatly appreciated.

Hi there,

Please go to the configuration page for Payeezy in AbleCommerce. There is a Debug option which needs to be enabled. Save the setting change. Then try to process a transaction. On the server, the log file has been updated. It is in the \app_data\logs\ folder and should be named something like payeezy.log. Open it up and look at the transaction details. You can post the SEND and RECEIVE response here, but remove any 'sensitive' info please.

BTW. This message is coming direct from the gateway, so you are connecting with them successfully.

Katie

Payezzy told us our issue was the TLS1.2 security setting. We had to update our server and turn the tls1.2 setting on. After we turned the setting on, we are still receiving the same error. I turned debugging on and this is what is in the payeezy.log file. There was no receive information in the file.

Send:
Version: 1.0
Request Type: Authorize
Icharge.MerchantLogin: *****************
Icharge.MerchantPassword: **********************************************
Icharge.Gateway: gwPayeezy
Icharge.TestMode: False
Icharge.GatewayURL: https://api.demo.globalgatewaye4.firstd ... action/v12
Icharge.InvoiceNumber: 100057
Icharge.TransactionAmount: 139.50
Icharge.TransactionDesc: authorize request for order#100057
Icharge.Card.Number: xxxxxxxxxxxx1111
Icharge.Card.ExpMonth: 5
Icharge.Card.ExpYear: 18
Icharge.Customer.FirstName: Alfred
Icharge.Customer.LastName: *****************
Icharge.Customer.Id: 1
Icharge.Customer.Address: *****************
Icharge.Customer.Address2:
Icharge.Customer.City: *****************
Icharge.Customer.State: PA
Icharge.Customer.Zip: 17109
Icharge.Customer.Country: US
Icharge.Customer.Phone: 7175551212
Icharge.Customer.Email:*****************

Here is the error message in the app log.
2017-04-29 12:36:51,800 ERROR AbleCommerce Provider threw exception in DoAuthorize.
nsoftware.InPay.InPayIchargeException: HTTP protocol error. 401 Unauthorized.
at nsoftware.InPay.Icharge.AuthOnly()
at CommerceBuilder.Payments.Providers.EPaymentIntegrator.Payeezy.DoAuthorize(AuthorizeTransactionRequest authorizeRequest)
at CommerceBuilder.Services.PaymentService.Authorize(AuthorizeTransactionRequest request, IPaymentProvider paymentProvider)

Please take a look at this page and see if anything here applies to your installation:

http://help.ablecommerce.com/index.htm# ... ls_1.2.htm

Please keep us updated. I'm sure this issue will be coming up several more times, so I'd like to know for sure that one of the solutions in the document works.

Thanks
Katie

Katie,
We are in the situation where we are on .net version 4.0 and using Ablecomm version 8 and greater, but we have .net 4.5 installed on our server. In the help, it states that ".NET 4.0. TLS 1.2 is not supported, but if you have .NET 4.5 (or above) installed on the server, then you can force TLS 1.2 even if the application doesn't support it. However, it requires a different code change in the application's start event." What is the different code change that is required?
Thanks,
Alfred

The code changes are shown toward the bottom of the document.

Hi Alfred,

I was just checking in to see if you had any luck with the TLS issue?

Thanks
Katie

Hi,
We still can't get it to work. We upgraded our server to 2008R2 which supports TLS 1.2. We updated the registry to include the schannel keys in this article(https://success.outsystems.com/Support/ ... nd_TLS_1.2). We did the update that you guys suggested to the global.asax file. We upgraded our .net version to 4.5 than 4.6. We still can't get it to work. Has anyone else had this problem? Do you have any other suggestions?

Hi,

Did you make the two changes to web.config?

- Search on targetFramework="4.5" and change to targetFramework="4.6"

- There will be 2 search and replace instances.

Are you getting the same error message after making all these changes?

Thanks
Katie

Hi Katie,
I had changed both to 4.6 and still received the same error as before. No matter what change I had done, the same error pops up. Also, I've checked the payezzy log file and I'm still only getting "send" information. There's no receive info that comes back.
Thanks,
Alfred

Hi Katie,
Would a asp.net trace be helpful to you? If so, could I email it to you directly? I don't want to put that information on to the message board.
Thanks,
Alfred

Hello Alfred,

You can open up a support ticket for assistance.

https://www.ablecommerce.com/helpdesk.aspx

Thanks
Katie

Trying to setup Payeezy and I am having the exact same issues.. nobody ever posted back with a update on what the fix was.

Based on the ticket that was opened, we tested it with TLS 1.2 and found...

Anyway, come to find out that the test account was no longer active. After we setup a new test account, I was able to successfully connect to Payeezy's test endpoint URL which is using TLS 1.2.

So it was working in our tests, which suggested an invalid configuration. We asked for a screen capture of the settings page and we're guessing they sorted it out as they never got back to us on therequest.

Just went back through the setup and changed all of the keys and now it works.. who knows.

Thanks for the update Tim, glad you got it working.

I got quite a few payments that went through yesterday and today but I did notice this in the log from last night.. there was two pretty much back to back.
Any idea what that could be a result of?

I got one of these today.. six yesterday.. the error time does not match a transaction charge/denial on payeezy so it doesn't seem to be getting that far.. Just looking for a idea of where these are coming from.

Turned on debugging.. When I get these errors there is a send but no receive..

According to Payeezy
400 Bad Request Input Request is invalid or incorrect.

Looking at the send the only thing I can think of is the customer has weird characters in his address.. (Icharge.Customer.Address: ********, 5, 6º 4ª)

**** where put to remove non important part of address.

I asked him to remove those characters to see if it would go further in the process.. waiting on his response.

EDIT.. That fixed the issue and his payment went through fine.. So is this a issue with the gateway programming or a issue with Payeezy?

Called Payeezy and they say they have never supported "special characters" and that is why these customers get the 404 error.

Looks like the Payeezy interface needs to be programmed to strip out any "special characters".