PayPal Express and PayPal Standard

The full HTML looks like this:

<div class="wc-proceed-to-checkout">

				<a href="https://www.site.com/checkout/">Proceed to Checkout</a>
		<div class="clear"></div><div style="position: relative;" class="paypal_box_button"><div id="paypal_ec_button"><a href="https://www.site.com/?wc-api=WC_Gateway_PayPal_Express_AngellEYE&pp_action=expresscheckout"><img width="150" border="0" alt="Pay with PayPal" src="https://www.paypal.com/en_US/i/btn/btn_xpressCheckout.gif"><noscript><img src='https://www.paypal.com/en_US/i/btn/btn_xpressCheckout.gif' width='150' border='0' alt='Pay with PayPal'/></noscript></a></div>            <div style="display:none;z-index: 1000; border: none; margin: 0px; padding: 0px; width: 100%; height: 100%; top: 0px; left: 0px; opacity: 0.6; cursor: default; position: absolute; background: url(https://www.site.com/wp-content/plugins/woocommerce/assets/images/[email protected]) 50% 50% / 16px 16px no-repeat rgb(255, 255, 255);" class="blockUI blockOverlay angelleyeOverlay"></div>
            <div class="clear"></div></div>
	</div>

It doesn’t hurt anything to have both enabled, but the Express Checkout settings do give you the option to display that option in the regular list of gateways, so if you had that set and you had PayPal Standard enabled then you’d have 2 separate “PayPal” options in the checkout page and that could confuse people.

I know lots of people have already updated to WooCommerce 2.3 and haven’t had any issues, however, there are a few minor things that we plan on getting updated and released for 2.3 before much longer. Mostly cosmetic, and what you mentioned about the button alignment is a perfect example of that. Woo changed the way the checkout buttons get output on that page, so we need to make a few adjustments to our plugin, too.

I have not specifically tested the sequential order IDs plugin, but off the top of my head I can’t think of any reason that wouldn’t work out for you. If you find there are problems, though, please create an issue in our GitHub repo and we’ll get it resolved in a future update.

I’m going to go ahead and mark this as resolved, but let me know if you have any other questions or concerns. Thanks!

Hi,

Thanks a lot for the quick response.

Reason I asked if it was working with 2.3.5 and sequential is because one of the first payments that someone tried to put through with this plugin returned an email error as follows:

DoExpressCheckoutPayment API call failed.

Error Code: 10431
Error Severity Code: Error
Short Error Message: Transaction refused because of an invalid argument. See additional error messages for details.
Detailed Error Message: Item amount is invalid.

And I have no idea why.

With regard to having express and standard enabled simultaneously can I ask you a quick question? With your plugin and using the express option, what happens if someone clicks the normal “proceed to checkout” button, fills in the entire standard woocommerce form and then selects paypal express? Will it use the shipping details they entered from WooCommerce form, or from PayPal?

Thanks

Well, that’s an issue that we know about and we’re working to get resolved. WC keeps changing things and then we have to try to keep up, but they don’t always document their changes in their change-logs, so sometimes it can prove a little difficult to get things resolved, and that has been proving to be one of those cases.

Are you including sales tax in your item pricing? Are you using any bulk item discount plugins or anything similar?

Yes, we enter our prices in WC inclusive of sales tax. Although that is only applied to any countries located in the EU.

Anywhere outside of the EU has no sales tax (and WC automatically removes it)

Not using any bulk item discount plugin AFAIK.

Thanks

Ok, yeah, that’s getting caused because of a rounding issue with the way prices are handled with inclusive of tax. It’s been something that’s tough to replicate exactly when you want to, but is definitely happening enough that there’s an issue.

We’re focused on it, and we do plan to have it resolved with 1.1.7, which we’re hoping to get done in the next couple of weeks.

Awesome – look forward to the update ??

Alsom any chance you can help with this:

With regard to having express and standard enabled simultaneously can I ask you a quick question? With your plugin and using the express option, what happens if someone clicks the normal “proceed to checkout” button, fills in the entire standard woocommerce form and then selects paypal express? Will it use the shipping details they entered from WooCommerce form, or from PayPal?

Thanks again

If they use the actual WooCommerce checkout forms then it should be sending that address over to PayPal and locking it so it can’t be changed. So that would be the address that gets used.