If this is your first visit, check our documentation. To post, register or login.
Forums / Addon Payment Modules / Cardsave Redirect 403-Forbidden: ERROR 13326: Couldn't speak to ServerResultURL

Cardsave Redirect 403-Forbidden: ERROR 13326: Couldn't speak to ServerResultURL

Started by kapil_raja on 26 Oct 2012, 10:14 AM · Views: 1,753

Results 1 to 2 of 2
26 Oct 2012, 10:14 AM
#1
kapil_raja avatar

kapil_raja

New Zenner

Join Date:
Mar 2012
Posts:
4
Plugin Contributions:
0

Cardsave Redirect 403-Forbidden: ERROR 13326: Couldn't speak to ServerResultURL

Can anyone check this issue and answer me.

I have integrated cardsave redirect module in Zen Cart 1.3.9g,

cardsave says: URl need fixing

ERROR 13326: Couldn't speak to ServerResultURL

You are receiving this email as an error occurred whilst processing a payment using
our hosted payment form solution. We were unable to successfully deliver the
transaction result to your system. This could have been caused by a network problem
(e.g. a connection timeout), or an error occurring on your ServerResultURL page.

As this error happened after the transaction was processed, we suppressed it from
the customer, and displayed the transaction result to them on our system.

ERROR 13326: Couldn't speak to ServerResultURL
[http://www.somedomain/includes/modules/payment/cardsave_redirect/serverresult.php].
Full Error Details: The remote server returned an error: (403) Forbidden.

how do i deal with this??? :frusty:

26 Oct 2012, 3:17 PM
#2
drbyte avatar

drbyte

Sensei

Join Date:
Jan 2004
Posts:
63,512
Plugin Contributions:
176

Re: Cardsave Redirect 403-Forbidden: ERROR 13326: Couldn't speak to ServerResultURL

For security reasons, you cannot use URLs which point to PHP files located inside the /includes/ folder.

Rewrite your module to do its callback to a file that doesn't sit below the /includes/ folder.

.
Zen Cart - putting the dream of business ownership within reach of anyone!
Donate to: DrByte directly or to the Zen Cart team as a whole

Remember: Any code suggestions you see here are merely suggestions. You assume full responsibility for your use of any such suggestions, including any impact ANY alterations you make to your site may have on your PCI compliance.
Furthermore, any advice you see here about PCI matters is merely an opinion, and should not be relied upon as "official". Official PCI information should be obtained from the PCI Security Council directly or from one of their authorized Assessors.