Harald Ponce de Leon

The PayPal App only uses POST requests for the classic NVP APIs.

You should see the Instant Update requests in the PayPal App -> Log page logged as CallbackResponse actions. If you don't see these records then the request is probably not hitting your server. HTTPS is required for Instant Update to work. v5.000 enables the In-Context checkout flow - this is now the preferred checkout flow to use but does not support all of the features of the Classic checkout flow (such as Instant Update). After the customer signs into PayPal and confirms their shipping address, they are redirected to the checkout confirmation page where the cheapest or first shipping module is automatically chosen.

That's not going to happen for the v2.3 release series. It has been performed though for the v2.4 series (currently in beta).

Log In with PayPal @@mcmannehan It's briefly described in the documentation in the Requirements section: https://library.oscommerce.com/Package&en&paypal&oscom23&log_in Did you end up setting that up correctly?

This will be added to the next update. v5.001 only fixes the coding error in the Payments Standard module that v5.000 introduced.

Thanks for pointing this out! This has been fixed in v5.0.1 - to apply it, visit the Info/Help page and the update notice should appear.

Perfect! I'll send you a PM when the changes have been pushed out to review. Thanks!

It's a one click procedure. The App checks once every 24 hours if an update is available and displays a notice. A check is always performed on the Help/Info page. The update procedure makes sure the file and directory permissions are sufficient for all files being updated before the files are overwritten. Feel free to try on a backup beforehand.

It will overwrite files that have been modified. Here is a list of changes that will be performed: https://github.com/haraldpdl/oscom2_app_paypal/compare/23-4.039...23-5.000 Click on the Files Changed tab and then the "40 changed files" link to view the file listing. I'll look at adding the suburb into SHIPTOSTREET2 in the upcoming update - this won't break existing installations. Could you get Jack to email me so we can go over the changes?

:thumbsup: Another update to the PayPal App will be pushed out soon that adds an option to force TLS v1.2 connections.

For those upgrading, if v4.039 worked, then v5.000 will also work fine. For new installations that are getting deprecated notices, use the following error reporting level in includes/application_top.php and admin/includes/application_top.php: // set the level of error reporting error_reporting(E_ALL & ~E_NOTICE); if (defined('E_DEPRECATED')) { error_reporting(E_ALL & ~E_NOTICE & ~E_DEPRECATED); } The error reporting is set at the top of those files. The code block above will be present in v2.3.5 onwards.

Hi All.. New certified PayPal payment modules are now available at the Add-Ons site to download, install, and use for existing store owners. The new modules will also be included in the core osCommerce Online Merchant release packages from v2.3.4 onwards for new store owners to use. The new modules include: PayPal Payments Standard v3.0 PayPal Express Checkout v3.0 PayPal Payments Pro (Direct Payment) v3.0 PayPal Express Checkout (Payflow Edition) v3.0 PayPal Payments Pro (Payflow Edition) v3.0 and introducing: PayPal Payments Pro (Hosted Solution) v1.0 The PayPal Payments Pro (Hosted Solution Payflow Edition) module will become available in the coming weeks. The new modules are optimized for osCommerce Online Merchant v2.3.4 and are compatible with earlier v2.3 and v2.2 releases. Documentation for the new modules can be found at: http://library.oscommerce.com/Package&en&paypal&oscom23 Support for all PayPal payment modules for osCommerce Online Merchant v2.x is available at: http://forums.oscommerce.com/forum/54-paypal/

@@headline-dbs I'm looking into this and will get back to you / reply here with a solution. In the meantime, please try Express Checkout as an alternative until the problem has been fixed. I will try and find a solution to this today.

@@headline-dbs It seems to be a bug! Can you please make a change in the following file: catalog/includes/modules/payment/paypal_standard.php line 599, change the PS in: .... $this->_app->getApiResult('PS', 'GetTran.... to APP, so it becomes: .... $this->_app->getApiResult('APP', 'GetTran.... Could you confirm if that works for you? It will be fixed in the next version.

@@headline-dbs Can you confirm via FTP if the following file exists: /homepages/1/xxxxxxx/htdocs/catalog/includes/apps/paypal/modules/PS/api/GetTransactionDetails.php

It looks like you're using the latest development source code from out Github repository which is for v2.4.0beta. This release series will not work with existing modules for v2.3.x - a compatibility module is planned though and will be release in a short while. If you'd like to stick to the v2.4.0beta development code, try the latest source code from the PayPal App for v2.4 at https://github.com/haraldpdl/oscom2_app_paypal

Anything really, as the right url is passed as a parameter to PayPal which overrides what is set in the PayPal profile. If the seller account is only used on the osCommerce store, then setting it to something like the following would not hurt: https://www.your-url.com/path/to/checkout_process.php

Hi Derek.. Can you confirm that the PDT Identity Token has been setup on the PayPal Seller Profile and that the value is entered in the PayPal App -> Configure -> Payments Standard -> PDT Identity Token field? It needs to match the same value as on the live or sandbox account. PDT can be found on the following page at PayPal:

If you have not yet tried, could you also make a test order using a PayPal Sandbox account? A separate sandbox account can be configured in the PayPal App and a customer sandbox account is also needed to test the transaction out.

Hi Derek.. The response should not be empty. Could you check your web server / php error log to see if errors around those times have been logged?