In-Context

This plugin redirect customer to PayPal page, this is normal. After do payment customer is redirecting back to shop to confirm payment.

Thanks for your reply “betagoo”.

On the description tab it says:

PayPal PLUS is a solution where PayPal offers PayPal, Credit Card and ELV (pay upon invoice will be added in a later phase) as individual payment options on the payment selection page. The available payment methods are provided in a PayPal hosted iFrame that gets embedded into the WooCommerce checkout page.
Based on the payment method selected by the buyer, he will at a later stage (on redirect to PayPal / in context checkout) be presented with either the PayPal Login page or an input mask for bank / credit card details.
The redirect can be initiated from within the iFrame or at any later stage during checkout. The final payment execution happens on the merchant side.

I don’t want a redirect to paypal. It needs to work as a pop-up window.

I have Paypal plus enabled, why is it not working?

PayPal Plus, as included in this plugin, is only designed for German merchants. It would be used in place of Express Checkout.

You mentioned you’re setting up Express Checkout, though, so I guess I’m a little confused. Do you have both Express and Plus enabled? That’s not going to work well for you.

If you’re using Express Checkout there is an “in-context” feature for it that we plan on implementing in a future update. We’re hoping to get that included on our very next update, actually, but I can’t guarantee it.

Again, though, I don’t think Plus is what you’re after unless you’re in Germany and you have Plus specifically enabled on your account.

Thank you for your reply.

I am based in Germany, however we do offer the same extra options that Paypal plus offers anyway, no gain there other than more fees. I am solely interested in the in-context feature.

Do you have a timeline on integrating in-context in the plugin?

We’re currently working on the 1.2.4 release, which should be ready within a couple of weeks.

Then we’ll probably do a 1.2.5 to add a few other small feature requests before getting started on 1.3.0, which is going to add quite a bit and take a while.

I’ll do my best to get this included on our 1.2.5, and I’d hope to have that done within a month or two at the most.

Alrighty, thanks! Will wait then for 1.2.5