Forum Replies Created

Viewing 15 replies - 31 through 45 (of 5,090 total)
  • Plugin Contributor angelleye

    (@angelleye)

    @geneise It sounds like the orders where this is happening is because it was set to Authorization instead of Sale.

    If this only happening on some orders, then I would say you must have this set differently at the product level.

    To clarify, under Settings -> PayPal for WooCommerce -> PayFlow, you’ll find the option for “Payment Action” which can be set to Authorization or Sale. This would be treated as a global setting that would be the default for all of your orders.

    Within the product editor, where you see the side tabs for General, Inventory, Shipping, etc. you will find a tab called Payment Action. Within that, you could check to enable it, and then select Authorization or Sale. This would take affect for that product, and would override the global setting.

    So one way or another, it sounds like you have some orders that are getting processed as Authorizations. This looks to the buyer like it completes, and it shows up in WooCommerce as a pending authorization. This also explains why your response log shows RESULT 0 (which means successful) and a PNREF (which is the transaction ID for the Authorization.) This is also what the TRXTYPE=A means.

    So that seems to be what’s happening, but you’ll need to double check your settings to figure out what is triggering it.

    Please take a look at those things and let me know if that helps. Thanks!

    Thread Starter angelleye

    (@angelleye)

    Yes, was just coming back to do that. It’s now available here: https://wordpress.org/plugins/angelleye-gravity-forms-braintree/

    It’s basically taking where this one left off and updating everything so it works as expected.

    Based on feedback from here we’ll begin building a new list of bug/feature tickets and maintain this thing accordingly.

    I have forked this plugin on GitHub and made the necessary adjustments to get it working on the latest versions of WordPress and GravityForms.

    https://github.com/angelleye/gravity-forms-braintree

    We are waiting for WordPress to approve our repo here, and then it will be available as a separate plugin on the plugin directory. Shouldn’t be long.

    We’ll be maintaining it separately from that point on.

    Plugin Contributor angelleye

    (@angelleye)

    Hi Martin,

    With the 1.5.5 update we have added the Smart Buttons to the checkout page. These work best when they are last on the list, so that is why it’s being forced that way.

    We also added options in the 1.5.5 update so that you can adjust the smart button display in specific locations (ie. product pages vs. cart page vs. checkout page.)

    One thing we did not add, though, which I’m going to add in the next update, is the option for whether or not you want to use smart buttons in that regular list of payment methods on the checkout page.

    Right now we have a global option for smart buttons in general. If you disable smart buttons in the Express Checkout settings then you’ll see the regular checkout page option like you’re wanting, but of course you’d lose the smart buttons elsewhere.

    Another option would be to revert back to 1.5.4 temporarily until you see our next update, which will include the extra option I mentioned above.

    Let me know if you have any questions or concerns about any of that. Thanks!

    Plugin Contributor angelleye

    (@angelleye)

    So here’s a little bit of back story for you.

    Originally, we had Express Checkout integrated with static buttons and fewer options than are available now.

    A while back we added the Smart Button functionality, which you’ll see at the bottom of the Express Checkout settings. You can enable this to get nicer looking buttons in general throughout the site, and they have better functionality for Guest Checkout built into them as well.

    When we first added Smart Buttons, we did not have them included in the regular list of gateways on the Woo checkout page. This is what changed in 1.5.5. We now have Smart Buttons fully integrated in all button display locations (if you have Smart Buttons enabled in the settings.)

    You’ll see that you can adjust the size and some other options for those buttons, so you might be able to get it looking the way you like on the checkout page.

    I do see that we lost the icons. We’ll get that fixed in another update coming soon.

    All of that said, one of the primary benefits of Express Checkout in general is that users don’t have to fill out your checkout form. I would highly recommend that you enable PayPal buttons on product pages and the cart page if you have not already done so. By doing this, most people will skip the checkout page entirely.

    If you want to try disabling the Smart Buttons altogether you can do that, too, and you may like it. I think you’ll find the smart buttons are better overall.

    Let me know if you have any questions or concerns about that. Thanks!

    Plugin Contributor angelleye

    (@angelleye)

    @amirvenus Yes, you will find ours has many features that their’s does not. 🙂

    Please make sure to apply the 1.5.7 update we just released. Then go into the Express Checkout settings, and at the bottom you’ll find an entire section for Smart Button options.

    Here, you can adjust the smart button display options separately for display on the product pages, cart page, and checkout page. This should allow you to get things looking nice.

    If not, please provide screenshots to compare and I’ll see what we can do to help more.

    Plugin Contributor angelleye

    (@angelleye)

    That looks like you’re using the Woo provided PayPal plugin instead of ours. This forum is for our “PayPal for WooCommerce by Angell EYE” plugin.

    If you install ours to replace theirs you should not have any problems. 🙂

    Plugin Contributor angelleye

    (@angelleye)

    Thanks for the info. We’re looking into this now to see if we can reproduce the problem, and we’ll get an update released ASAP!

    Plugin Contributor angelleye

    (@angelleye)

    @wrip, we’re about to start our new Sprint here internally, and we’re going to include this ticket on the sprint. Should have this fixed within a couple of weeks at most.

    Plugin Contributor angelleye

    (@angelleye)

    @breezyclouds

    I asked you previously if you were using our IPN plugin and you said no. So have you actually had that installed all along, or did you just recently install to check it out? I’m a little bit confused there.

    Express Checkout is a replacement for PayPal Standard. If you have Standard enabled right now and somebody uses that to checkout, it’s going to send the IPN to the WooCommerce IPN handler.

    If you do have our IPN plugin installed, it actually overrides the WooCommerce PayPal Standard IPN URL with ours, and then forwards the IPN data to the Woo URL so that both get hit. Again, though, that’s only if you’re using Standard.

    With Express Checkout there is no default IPN URL used, so it would fall to whatever you have set in your PayPal account profile.

    As for Express Checkout working, you need to make sure you have it enabled for display where you need it / want it. I would recommend you enable it on the product pages, the cart page, and the checkout page. Make sure to set the display option for checkout page to “Include in the regular list of payment gateways.” That is what will make it show up on the Woo checkout page and should get rid of the error you saw.

    That said, the whole point of “Express” Checkout is that buyers don’t have to fill out checkout forms. So again, I recommend you place the button on the product pages and cart page, too.

    That should get EC working for you, and then with Standard disabled the IPNs should go where you’re expecting.

    Plugin Contributor angelleye

    (@angelleye)

    To follow up, PayPal Standard (which comes with Woo) does set a Notify URL to use their built in IPN solution. Ours does not do this by default. Instead of doing that, we built the separate PayPal IPN for WordPress plugin, which avoids this sort of problem, and gives you a lot more power for how you want to use IPN.

    That again is why I feel like you must be using PayPal Standard instead of Express Checkout that comes with our plugin.

    Can you check your PayPal IPN History to verify exactly which URL the IPNs are getting sent to?

    Plugin Contributor angelleye

    (@angelleye)

    @breezyclouds

    Okay, I’m still confused by what you’re saying here. It sounds like you may be using other PayPal integrations separate from ours.

    Our plugin is specifically called “PayPal for WooCommerce”, and it would add a number of additional PayPal gateways to your WooCommerce Payments Tab. None of these are just “PayPal” or “PayPal Checkout” though.

    Our plugin would add “Express Checkout” as one of the gateways it provides. Is that what you configured?

    I asked because we also don’t have any options about “Enable IPN Email Notification”. We do have an “Enable admin email notification” for errors, but that has nothing to do with IPN.

    The ONLY way our plugin could overriding anything to do with IPN is if you specifically enable the IPN feature, and then you would also have to type in the URL that you want it to be sent to.

    So the first thing we need to do here is verify whether or not you actually are using our plugin with Express Checkout, or if you might be using the Standard PayPal that comes with Woo..??

    Plugin Contributor angelleye

    (@angelleye)

    @breezyclouds, Oliver just explained more to me what you are saying.

    Is it correct that you are trying to send IPNs to a separate URL, but payments through our plugin are sending to our URL instead?

    Do you have our IPN plugin installed as well as our PayPal for WooCommerce plugin?

    Plugin Contributor angelleye

    (@angelleye)

    @breezyclouds, IPN is not used to send invoices, so I am not sure what you are asking here.

    If you are trying to send IPNs for paid invoices to a different URL then you need to make sure the proper URL is filled in to your PayPal and/or the Notify URL parameter of any API request or button you are working with.

    Plugin Contributor angelleye

    (@angelleye)

    1. Yes, there are options to include the PayPal buttons in the mini cart. Just do a Find for “Minicart” on the Express Checkout settings page and you’ll see it. It’s a check box option.

    2. We have not had any other reports of the responsive buttons not working as expected. make sure to check your theme to see if it’s overriding something with the buttons. Also check caching / CDN services which can sometimes conflict when you make changes to style settings like that.

    3. You have to make sure you have the button enabled on the cart page (similar to Minicart).

    Our plugin has a lot more options for how/where to display various buttons. This gives you a bit more freedom and flexibility than other plugins.

    Also, you can see from the star ratings that we offer much better support. This is primarily because we are much smaller than Woo, and we are able to focus specifically on payment processing, which is our specialty. Woo has themselves spread very thin across a vast array of products and services, and they have millions of users to support. We are able to get people taken care of much more quickly.

    Also, we do have a lot of features and functionality that Woo’s integration simply does not have. Sadly, we do not yet have all of this information documented well enough that it’s clear. Some of it is, though.

    For example, our use of Auth and Capture is much more extensive.

    We also have product level options for sandbox (so you don’t have turn the entire site to sandbox mode), as well as things like billing agreements, options to disable shipping, etc.

    We have a number of unique hooks that other plugins do not offer.

    Beyond all of that one, one of the things our users like the most about us is that we are able to turn around feature requests much more quickly than Woo. This goes back to our support.

    When you submit a ticket to us we respond much more quickly than Woo in most cases, and if there is a bug or a feature you are requesting that we don’t have, we can often get it added for you very quickly. These are some of the advantages of working with a smaller company.

    That said, we have been PayPal specialists (certified developers) for nearly 20 years now. The reason this plugin came to be is because the original Woo plugins simply were not quality. We had to build our own just so it would function properly, and when we did that, we decided to release it to others as well.

    Since then, we’ve maintained a lead over other plugin options as we continue to add more features and functionality. Simply compare our settings page (which you seem to have skipped over since you missed some of those other basic options) and you’ll see we offer a lot more than other plugins.

    I hope that helps answer some of your curiosity. Let me know if you have any other questions or concerns. Thanks!

Viewing 15 replies - 31 through 45 (of 5,090 total)