PayPal and others?

  • Resolved develobaby

    (@bornefysioterapi)


    3 weeks, 2 days ago

    Hej there,

    For a very long time now, PayPal was listed as an inbuilt, explicit QuickPay payment method – same as e.g. Mobile Pay or Apple Pay and I could configure this any I way I wanted in the WC backend (e.g country exceptions). PayPal appears to be gone now entirely, so effectively, customers notify me that they can’t pay with PayPal anymore. No mentioning of this in the release notes, I have seen no warning, no email notification that this will happen, nothing. Quite unfortunate for us :-/

    At the same time, all alternative payment methods (beyond the default “creditcard” have disappeared from the QuickPay window, too. So, now it appears I have to configure payment methods explicitly in the QuickPay settings in the WC backend, for instance like so: “creditcard, paypal”. In DK, I don’t want to accept PayPal (fees!), but the following doesn’t seem to work either: “creditcard, paypal, !paypal-dk”.

    Where do I go about this from here?

    Best, Maria

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Author PerfectSolution

    (@perfectsolution)

    3 weeks, 2 days ago

    Hi Maria,

    Regarding the Paypal gateway, I can confirm that this is not properly loaded in, in the current version. This is not intentional, and I will look into a fix asap.

    As of right now, I cannot confirm problems with neither Mobilepay and Apple pay. Mobilepay is now called Vipps Mobilepay, but the internals are identical. Apple Pay is also still available.

    Regarding configurations etc. these payment methods have never had specific, extensive settings. Country exceptions etc. is not built in functionality, so this must come from other third party plugins.

    Thread Starter develobaby

    (@bornefysioterapi)

    3 weeks, 2 days ago

    Oh, perfect, thanks for your super-quick response. And thanks for confirming an issue specific to PayPal in the plugin.

    I did not intend to report an issue wrt MobilePay or ApplePay, I just used them as examples to describe, what I used to see in the WC backend for PayPal – so no issue there! 👍

    And you are right. Country exceptions are custom code and as long as PayPal returns as first-class-citizen in WC, existing custom code handling available payment methods per country will work again. I referenced “creditcard, paypal, !paypal-dk” as the content for the field “payment methods” in section “Extra Gateway Settings” on page “admin.php?page=wc-settings&tab=checkout&section=quickpay&from=WCADMIN_PAYMENT_SETTINGS”. There is a link to learn.quickpay.net, which describes negations with the example: “creditcard, !jcb, !visa-us”. I don’t think, this is really plugin related, at all. It’s just a config string that the plugin sends to the QuickPay Gateway and the gateway simply doesn’t handle the case “creditcard, paypal, !paypal-dk” the way, I would expect it to be handled, given that the docs example does something very(!) similar for visa. So, but … none-issue in the WP-plugin, I suppose.

    Plugin Author PerfectSolution

    (@perfectsolution)

    3 weeks, 2 days ago

    Noted – and thanks for elaborating.

    If the payment window acts unexpectedly, when using negations, I would recommend to reach out to Quickpay support as they can actually troubleshoot (or explain) this better than us.

    I have just pushed v. 8.0.3 resolving the missing Paypal instantiation.

    Thank you for reaching out, and do no hesitate if you should experience other problems.

    Thread Starter develobaby

    (@bornefysioterapi)

    3 weeks, 2 days ago

    Stellar!

    Solved in under 3 hours. Works. Closed.

    ★★★★★

Viewing 4 replies - 1 through 4 (of 4 total)

You must be logged in to reply to this topic.