Jump to content
sunshynecraftsbeads

Paypal Sandard - Customer receives message could not verify Paypal trans.

Recommended Posts

include(/xxx/eyeseetv/includes/apps/paypal/modules/PS/api/

 

is definitely not existing.

 

There's a directory

 

/eyeseetv/includes/apps/paypal/api

 

which includes the referred file GetTransactionDetails.php.

 

I can try two ways:

 

1.) change the path in OSCOM_PayPal.php

 

or

 

2.) copy the directory to eyeseetv/includes/apps/paypal/modules/PS/api/

 

Is it a bug?

 

Regards,

stefan

Edited by stefan21

Share this post


Link to post
Share on other sites

I've never seen this before. It's possible that something was supposed to be created when the module was installed and that didn't happen. I would advise against just changing things. You need to contact Harald Ponce de Leon and report a possible bug.

 

Regards

Jim


See my profile for a list of my addons and ways to get support.

Share this post


Link to post
Share on other sites

Jim,

 

thank you very much for your assistance.

 

Meanwhile I found this:

 

http://forums.oscommerce.com/topic/398887-paypal-app-for-oscommerce-online-merchant/page-4#entry1750358

 

Did what Harald suggested.

 

Customer has been redirected to the shop. Shopping cart is empty. Customer received an email of the order with all details. Shop-owner received all information about the deal. In the PP-account the deal was confirmed and all right.

 

Seems to work now. Would be nice to get some confirmation of other users. I don't want anybody get me wrong, but IMVHO this should be fixed soon. It's all about money...

 

Regards,

stefan

Share this post


Link to post
Share on other sites

You should post in that thread stating that you have tested that fix and it works. It looks like nobody else gave him any feedback on it.

 

Regards

Jim


See my profile for a list of my addons and ways to get support.

Share this post


Link to post
Share on other sites

@jordi "could not verify transaction" is not a bug, it is an error message. There are several things that can lead to it, and most of them are failures to configure the module properly. Reverting to an earlier version of the module using less verification is not a solution, it's really avoiding the problem that you hit by doing less checking.

I have seen several kinds of attacks on websites payment modules over the years usually with the aim of hijacking payments but sometimes trying to steal goods. I think it 's best to set up as much automated checking as you can.


For a new install or if your store isn't mobile-friendly, get the community-supported responsive osCommerce (2.3.4.1 CE).

here: https://github.com/gburton/Responsive-osCommerce/releases

Working on generalising bespoke solutions for Quickbooks integration, Easify integration and pay4later (DEKO) integration at 2.3.x

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×