Jump to content


  • Content Count

  • Joined

  • Last visited

Everything posted by jka

  1. jka

    PayPal Pro Plugin

    We use PayPal as our payment processor only. We don't accept PayPal. Hence we have to use the Pro checkout explicitly. We have a master agreement with PayPal when we switched over merchant processing from Authorize.net to them. So, we cannot use Express Checkout.
  2. I just upgraded to latest 1.2.5 plugin. We use the Pro checkout. This means the secure checkout form is presented from form.tpl. Question : 1. How do we make the billing info for credit card displayed below as "read-only" or non editable. This will prevent fraud from the system billing address and credir card billing address. 2. Any input on how we can make the text fields small for the credit card number, exp, etc. Thanks.
  3. We sent an email on Dec 10 to your admin email as well as your support email, which bounces. Did you read your last 3 lines properly??? So, you are not able to cancel based on anonymous posts at this forum ... agreed. But you were able to create an account and open a support ticket yourself and link it to a purchase based on an anonymous post here??? We did not create an account, you folks did it. Buying an extension here shouldn’t be creating accounts on multiple systems. Please treat or respond to our email and cancel our support etc. FYI, we did like your extension but decided not to use it. We have bought other extensions here to try them out but don’t use them either. It’s ok to try products. It’s not ok to then be asked to login to other websites and then cancel accounts which we didn’t create.
  4. Hello folks at Havenswift Hosting.... We have tried to send multiple emails to you folks. We bought this enhanced admin order entry extension to try it out and dont use it as it doesnt completely cover our needs. However we keep getting renewal emails from your system with invoices (Inv# ES-999) as well as asking us to login to your client area in your website. We have not created any account on your website and do not want to create one. Can someone please remove us from your systems so that it does not keep sending us invoices, reminders etc. Sorry, we have to ask through this forums as our previous direct emails have not yielded any results. Thanks.
  5. The existing PayFlow Link extension does not work. We will be willing to pay for the development or enhancement of the existing extension or a new one. The Payflow link extension should support "Transparent ReDirect". 1. Info: https://www.paypalobjects.com/webstatic/en_US/developer/docs/pdf/paypal_transparent_redirect.pdf 2. Examples flow of hosted flow logic https://developer.paypal.com/docs/classic/payflow/integration-guide/#configuring-hosted-checkout-pages
  6. jka

    PayPal Pro

    Folks, Can someone see if they have received or encountered this before. We got this email from PayPal this morning and we use the PayPal Pro extension which works fine. email received this morning from PayPal.... This email is a follow up regarding the American Express setup on your Payflow Gateway account. At this time, we see that a separate Amex processing account was added to your gateway account as requested. Your transactions are currently being submitted against your backend PayPal account, though, not through the frontend Payflow Gateway account as intended. In order to receive your Amex rate, you will need to make sure you are sending your Amex transactions through the Payflow Gateway account. We recommend reaching out to your tech support team to have your integration updated/corrected to post the transactions to your Payflow Gateway account so that your Amex rate will begin to take effect on those transactions. Thank you!
  7. Any idea on how to make this credit card form at checkout look a bit more small and concise. The form is under the gateway module. This specific attached form is from the PayPal Pro hook module. For example, make the form small and compact and centered on the page.
  8. BSmither et-all Wanted to share here the resolution to the cURL error 35. We thought that it may be something to do with cURL 7.62 but it was not even though it may have caused it with the latest libraries. We saw this issue only when accessing the sandbox environment but from the same server the Live system worked fine. After some poking around and a few calls with the Paypal integration team we found the line of code that made the sandbox environment cough back at us. We commented the following lines in website_payments_pro.class.php /* ## Sandbox requires TLS 1.2 if($this->_module['gateway']=='0') { $request->customOption(CURLOPT_SSLVERSION, 6); } */ So, with the new cURL libraries 7.62 which is the latest, this above causes the cURL error 35. Once we commented it, everything on the sandbox site works fine now as well as the Live site.
  9. The SSL Version under cURL is NSS/3.36. I did some poking around with error 35. It seems few others also have the same issue after upgrading to the latest cURL version 7.62. I downgraded it to 7.29 and it worked fine. We have to wait for them to fix 7.62 or otherwise need to downgrade to 7.61.
  10. Has anyone got this PayPal 1.1.14 extension working. We got all the API info into the extension. The test endpoint works fine and successfully. However when we try a transaction through the cart it fails. The error under request log is as follows ... cURL Error (35): SSL version range is not valid. The server has the latest cURL as well as OpenSSL.
  11. BSmither, we have the shipping estimator working as of now. I think its Noodleman's plugin. In any case, we spent some time on this link which helped explain some of the PayPal behavior. https://developer.paypal.com/docs/checkout/best-practices/ I think we are good at this time by moving some of the buttons around and the credit card images. As always, thanks for your help which always is timely.
  12. We dont have the sandbox test environment accessible over the internet. Will clear the CC cache this evening and try it out again.
  13. The php that controls checkout is content.checkout.php. It pretty much takes care of all the actions. Any chance we will be able to get the User Billing/Shipping address before proceeding to Checkout. The pertinent use case is when the user is not logged in or has to enter the address details. Current flow is that it presents the address form for entry and the page refreshes and reloads shipping/tax etc after address entry. One alternative will be to "not" display the "Secure Checkout" button under address details etc are input or ISUSER.
  14. Will do. However, we tried to added another button to the CSS file, but its not showing up when we refresh the page. Do we need to purge cache etc and retry for it to pickup the newly added button?
  15. Hello bsmither, Thanks again for helping. I am poking around the button styling now. The svg part is a bit too much for now. Question ... In the file content.checkout.php, is there a way to get the address before presenting the full checkout page? Not sure what {if $INCLUDE_CHECKOUT} does, after also displaying the address form. The goal is to get the address form first before the rest of the gateway stuff happens. This will make the Paypal process a bit more cohesive for our avg user base who happen to be 50+.
  16. Is there any chance to know the complete list of buttons, colors etc used in CC such as "Button Success" etc. Also is it possible to add more to sprite svg? After playing with our sandbox environment we have a fairly good idea to make the PayPal Pro integration seamless, however we need to add a couple of different button labels. Looking for pointers on where its controlled or additional options.
  17. jka

    PayPal Pro

    Got it. Did a little bit of poking around and was able to accomplish the screenshot attached. Maybe bsmither or someone can point in the right direction ... 1) Need to make the Credit Card images larger. Not sure where the PayPal image for credit card is stored. 2) Also need to insert and separate the "PayPal Credit" image with a bit of gap or add "--- or ---" between them
  18. jka

    PayPal Pro

    Is it possible to remove the "Choose Payment Method" and replace the "Secure Checkout" button with the Visa/MasterCard/Discover/Amex Logo? It would be a bit more seamless in that case. Would also have to look into inserting a line between "PayPal" and "PayPal Credit" buttons too. Forgot to add ... As a vendor our primary choice is for the customer to choose the credit card option as its cheaper fees for the transactions.
  19. jka

    PayPal Pro

    We are planning on moving from Authorized.net to PayPal Pro for our credit card processing. The Paypal Pro extension looks pretty good. However in the checkout page it looks a bit confusing. There is a radio button for "Choose Payment Method", on the left it has the Visa, Mastercard etc logo, on the right side of the page it has "Secure Checkout" and then it has the "checkout with PayPal" and "PayPal Credit" logo below the Secure Checkout Button. This entirely seems very counter-intuitive at best. How can we change some of these logos around and may them as 3 distinctive choices, (a)credit card (b)PayPal (c)PayPal Credit
  20. jka


    Thanks BSmither, Yes, we want it to be the same behavior as a successful transaction . Will add this line of code and check what shakes out. The "To Review" is really a Credit Card status for the merchant. To the user/purchaser the order has been received. If the merchant goes to the Fraud Detection Suite and sees that its a questionable transaction, then the merchant can always cancel the order. The problem is more to do with the user still sitting on the credit card input page.
  21. jka


    I had posted to an existing thread last week. Today I submitted an order in the system on behalf of my customer. the result received from Authorize.net is 4|1|253 bSmither had given us a fix for 1.3 version and then Al had updated to 1.4 with fixes. Since then, the behavior is not as expected. Please see screenshot attached. It shows order received but still still on the credit card form page. How can we mimic the same behavior as 1|1|1 for 4|1|253
  22. We have updated to 1.1.4 for the last couple of months. The status from AIM with "4 1 253" works fine now with the custom message from Authorize.net. However here is the issue, unlike when the status is "1" where its gets redirected to a Order Complete page, in this case of "4", it displays the message properly etc adds to pending order. However it still sits on the credit card form page. Customers that get a "4" (Fraud Detection Suite) from Authorize, get the order received in pending status on the screen with the CC form below. They end up entering the card info again and sometimes we get 2-3 authorizations. How can change the behavior of "4" similar to "1" and take them away from the CC input screen.
  23. The AIM method stopped working since this past weekend. When we contacted Authorize.net they say its probably related to disabling TLS 1.0 and 1.1. We had this issues with UPS module and have the latest cURL ... curl --version curl 7.57.0 (x86_64-redhat-linux-gnu) libcurl/7.57.0 NSS/3.28.4 zlib/1.2.7 libpsl/0.7.0 (+libicu/50.1.2) libssh2/1.8.0 nghttp2/1.21.1 Release-Date: 2017-11-29 In the transaction logs its a cURL timeout cURL Error (28): Connection timed out after 15000 milliseconds The UPS module started working fine once we updated cURL and we have also disable TLS1.0 and 1.1 Any hardcoding on the Authorize.net module??
  24. jka

    Coupon Code issue

    Hello Bsmither, I tried a few other random numbers but somehow 23 seemed invoke that coupon. We disabled that coupon for now. Not sure if there are others. Any nibbles on what you found or to fix?
  • Create New...