Jump to content

Harald Ponce de Leon

Community Team
  • Content count

    5,378
  • Joined

  • Last visited

  • Days Won

    125

Reputation Activity

  1. Like
    Harald Ponce de Leon got a reaction from valquiria23 in Payment Zone Not Working   
    There is a bug with the Braintree App v2.011 that does not respect the Payment Zone if one has been specified. Until the next App update is pushed out, those affected by this issue can easily apply the following change.
    In the following file:
    catalog/includes/modules/payment/braintree_cc.php on lines 95 and 97, the following constant is being referenced:
    OSCOM_APP_PAYPAL_DP_ZONE simple replace both instances with the following constant:
    OSCOM_APP_PAYPAL_BRAINTREE_CC_ZONE and save the file.
    Payment Zones will then work as normal.
  2. Like
    Harald Ponce de Leon got a reaction from Smoky Barnable in One-Page / Guest Checkout   
    I did not refer to storing the actual card information locally in the database - that I advise against unless you know what you're doing with PCI DSS (you 99% don't, so don't try). What I'm referring to is allowing the payment service provider store the card information on their servers and have them deal with PCI DSS (they are 100% compliant as it's their business). The payment service provider sends you a token which is stored locally in the database and is referenced for future payments. This token must be of course secured locally just the same as your payment service provider credentials must be secured. The last 4 digits of the card number is stored so the customer knows what card is going to get charged. It is here where CVV and 3D Secure can be configured to be asked for again as they have already been verified when the first purchase was made.
    The PayPal and Braintree Apps have this as a configuration option. Other payment modules that support vault storage are also configurable to enable the feature. The card input fields are loaded via iframe from the payment service provider so the card information never touches your server. There is no need to worry about PCI DSS even when stored tokens are enabled.
  3. Like
    Harald Ponce de Leon got a reaction from fohenrolle in Braintree Credentials   
    I don't know why the module would not be installed. It's not possible to install the module in the traditional manner as it will redirect you to the Braintree App Configuration page.
     
    Try deleting the OSCOM_APP_PAYPAL_BRAINTREE_CC_SORT_ORDER parameter from your configuration table:
     
     
    delete from configuration where configuration_key = 'OSCOM_APP_PAYPAL_BRAINTREE_CC_SORT_ORDER';  
    Then visit the Braintree App Configuration page and it should auto-install the module for you.
  4. Like
    Harald Ponce de Leon got a reaction from drferrari in UTF-8 In Payments Standard   
    @@Gergely, can you remove that charset addition and instead try the following in your PayPal account:
     
    PayPal Profile -> Selling Preferences -> Language Encoding -> More Options -> UTF-8
  5. Like
    Harald Ponce de Leon got a reaction from raiwa in QTPro BS   
    @raiwa done!
  6. Like
    Harald Ponce de Leon got a reaction from raiwa in QTPro BS   
    @raiwa done!
  7. Like
    Harald Ponce de Leon reacted to burt in One-Page / Guest Checkout   
    My ethos is;
    Make it very simple for the customer to do things.   As far as a checkout goes, what can be more simple than;
    login > choose shipping > choose payment > review order > complete
    It has been proven many times that a bite-size of cake, followed by a bite-size of cake...is far better than ramming a whole cake down ones throat.

    What I would like to see [in CORE]...which is sort of related...
    On shopping_cart.php a summary (estimated) shipping price, (estimated) taxes and so on.  So they see their grand total prior to starting a checkout.
  8. Like
    Harald Ponce de Leon got a reaction from oscMarket in One-Page / Guest Checkout   
    Sorry, I didn't write anything constructive in my post 
    I think just by judging the way that one page checkout screenshot looks is overwhelming the customer with too much information on the screen at once. The checkout process column on the right is not needed as I presume that information is shown again in the last step for the confirmation. The same edit links are also available with each step listed.
    Having a JavaScript based one-page checkout procedure is nice and can outperform a standard checkout procedure, but only if it has been designed properly. The idea behind a one-page checkout procedure is to keep it as simple as possible for the customer experience, not the technical achievement experience.
  9. Like
    Harald Ponce de Leon got a reaction from douglaswalker in One-Page / Guest Checkout   
    6 steps, and entering credit card information before the checkout confirmation page? That's not an improvement.
  10. Like
    Harald Ponce de Leon got a reaction from oscMarket in One-Page / Guest Checkout   
    Sorry, I didn't write anything constructive in my post 
    I think just by judging the way that one page checkout screenshot looks is overwhelming the customer with too much information on the screen at once. The checkout process column on the right is not needed as I presume that information is shown again in the last step for the confirmation. The same edit links are also available with each step listed.
    Having a JavaScript based one-page checkout procedure is nice and can outperform a standard checkout procedure, but only if it has been designed properly. The idea behind a one-page checkout procedure is to keep it as simple as possible for the customer experience, not the technical achievement experience.
  11. Like
    Harald Ponce de Leon got a reaction from oscMarket in One-Page / Guest Checkout   
    Sorry, I didn't write anything constructive in my post 
    I think just by judging the way that one page checkout screenshot looks is overwhelming the customer with too much information on the screen at once. The checkout process column on the right is not needed as I presume that information is shown again in the last step for the confirmation. The same edit links are also available with each step listed.
    Having a JavaScript based one-page checkout procedure is nice and can outperform a standard checkout procedure, but only if it has been designed properly. The idea behind a one-page checkout procedure is to keep it as simple as possible for the customer experience, not the technical achievement experience.
  12. Like
    Harald Ponce de Leon got a reaction from Gyakutsuki in One-Page / Guest Checkout   
    There isn't a one page checkout procedure in v2.3 due to the legacy codebase having the ideology of working on browsers with cookies enabled or disabled and JavaScript enabled or disabled. The v2.4 release will still have a standard checkout procedure however it doesn't share the same ideology and can have a one page checkout in a future v2.5 or so release.
    Regarding entering card information before the checkout confirmation page, we moved those fields in the payment modules a while ago to the checkout confirmation page. I don't remember if there is a European law on it, but it's more satisfying for the customer to see the real and exact order total when entering their card information in. If something alters the order total during the checkout payment page and the checkout confirmation page (card acceptance fees?), the customer will feel cheated of giving up their card information for an order total they didn't agree to.
    For the cases where card acceptance fees are passed to the customer, the customer chooses Credit Card on the checkout payment page and first enters their card information on the checkout confirmation page where the fee is included in the order total rows. The customer sees the exact order total before entering their card information in.
  13. Like
    Harald Ponce de Leon got a reaction from douglaswalker in One-Page / Guest Checkout   
    6 steps, and entering credit card information before the checkout confirmation page? That's not an improvement.
  14. Like
    Harald Ponce de Leon got a reaction from Klaus H. in PayPal App for osCommerce Online Merchant   
    The problem Henry experienced has been solved.
     
    If the PayPal Seller account has a API Certificate already set up, the API Signature cannot be used as the API Certificate already exists (PayPal only allows either a API Signature or API Certificate to be used). Removing the API Certificate from the PayPal account allows the Retrieve Credentials procedure in the osCommerce PayPal App to work and retrieve the API Credentials.
     
    It's not necessary to create the API Signature at PayPal, the Retrieve Credentials procedure will automatically do this for you.
  15. Like
    Harald Ponce de Leon got a reaction from pete2007 in IPN Verification Postback to HTTPS Microsite *Important Update Needed*   
    All PayPal modules we have included in our releases have always used HTTPS and POST. If you would like to make sure that your module works without disruption after June 30, you can check now by performing a test order and transaction using the PayPal sandbox server.
  16. Like
    Harald Ponce de Leon got a reaction from greasemonkey in PayPal App for osCommerce Online Merchant   
    What paths are shown in the update logs in includes/apps/paypal/work/update_log-*.php? Your custom admin directory or hardcoded "admin"?
  17. Like
    Harald Ponce de Leon got a reaction from frankl in PayPal App for osCommerce Online Merchant   
    @@greasemonkey @@mattjt83 could you please confirm if the following fixes the positioning for you:
     
    in catalog/includes/modules/payment/paypal_express.php, on line 207 change from:
     
     
    <span id="ppECButton"></span>  
    to:
     
     
    <span id="ppECButton" style="display: inline-block;"></span>  
    (A better approach is to add a custom css file to the PayPal App)
  18. Like
    Harald Ponce de Leon got a reaction from birdiebitsnbites in What are different PayPal modules   
    @@birdiebitsnbites TLS v1.2 support was first added in cURL v7.34.0 (in 2013) and in OpenSSL v1.0.1 (in 2012). The cURL package may need to be updated on your web server which may trigger a system wide upgrade depending on the operating system dependencies.
  19. Like
    Harald Ponce de Leon got a reaction from GetSirius in Braintree Credentials   
    Thanks for pointing the error out. I can confirm the problem is using empty() on a constant (this produces an error on PHP < 5.5 Servers).
     
    An update will be pushed out within a few hours.
  20. Like
    Harald Ponce de Leon got a reaction from altoid in PayPal App v5.000   
    Hi Fabrice..
     
     
    The v2.3.5 release is based on v2.3.4 (not BS). The BS is a separate community release series.
     
    v2.3.5 is based on the previous v2.3 release series. The BS release series is incompatible to v2.3.x and will merge to v2.4 when the production ready release is pushed out.
  21. Like
    Harald Ponce de Leon got a reaction from frankl in PayPal App for osCommerce Online Merchant   
    ​Hi Mike..
     
     
    The PayPal App for osCommerce Online Merchant has only been developed and certified for our v2.3 (and earlier) and v2.4(beta) release series.
     
    The PayPal App for v2.3 has been added to the BS/EDGE community release series, which is not compatible with the v2.3 release series. I'd suggest waiting until the App has been updated for BS/EDGE and performing the update manually.
     
    There is currently no update for our v2.4 release series as the update feature has moved to the core level and has not yet been pushed out in a v2.4 beta release (this is coming soon).
     
    If everything is working for you on BS/EDGE, I'd recommend waiting for the production ready release of v2.4 (coming at the end of March) and moving to that. There will be a push to move existing v2.3 and BS/EDGE users to v2.4 once the production ready release is pushed out.
     
    Users currently on v2.3 will experience no problems updating the PayPal App.
  22. Like
    Harald Ponce de Leon got a reaction from Sam-AUST in PayPal App v5.000   
    v5.0.10 has just been pushed out! This includes using the suburb value as the street2 parameter for the payment modules.
     
    Thanks to Jack_mcs and greasemonkey for reviewing the address changes.
  23. Like
    Harald Ponce de Leon got a reaction from vampirehunter in PayPal App v5.000   
    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.
  24. Like
    Harald Ponce de Leon got a reaction from Sam-AUST in PayPal App v5.000   
    This will be added to the next update. v5.001 only fixes the coding error in the Payments Standard module that v5.000 introduced.
  25. Like
    Harald Ponce de Leon got a reaction from mcmannehan in PayPal App v5.000   
    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.
×