Card recognition not working / Card Code phrase

  • Resolved Tom

    (@jeffreeeeey)


    3 years, 7 months ago

    Hi. Recently installed and configured this plugin. Using PayPal/ Sofort and also Credit/ Debit Card Seems to work just fine, but there are three potential issues that I feel I should mention:

    1. When inputting a credit or debit card number, the icon which displays in the card number field (recognising the card type) does not appear to work.
    It stays greyed-out even after card details are entered. (Using background image: wp-content/themes/storefront/assets/images/credit-cards/unknown.svg)
    As you can see this is being sourced from within the Storefront theme files.
    Unsure if a Storefront issue or an issue with this plugin?

    2. On the field title for expiry date, the field title reads in the format: MM/YY, but the placeholder text reads in the format: MM/YYYY. This appears to be confusing customers.

    3. The field labelled CARD CODE, per any other card processing form I have ever used, has always been labelled CVV rather than CARD CODE.
    Again this is confusing customers. Plugin has been installed just 2 days and already we have received 10+ emails from (UK) customers asking where they find their CARD CODE.

    Are any of these things likely to be changed in a future release?
    Currently I am faced with having to revert to the old plugin that we were using for PayPal/ Card processing as this plugin seems to be affecting usability/ conversion rates quite dramatically.

    Thanks

Viewing 14 replies - 1 through 14 (of 14 total)
  • Plugin Support Andreas W.

    (@aweissinpsyde)

    Hello @jeffreeeeey

    can you please open a ticket here https://paypal.inpsyde.com/docs/how-to-request-support-via-widget-on-the-website/ I would like to create an internal issue for it. So I can forward it to our developers.

    Have a nice day
    Regards
    Andreas

    Thread Starter Tom

    (@jeffreeeeey)

    Thanks Andreas, I have submitted a ticket as requested, along with some site info.

    Best regards

    Plugin Support Andreas W.

    (@aweissinpsyde)

    Hello @jeffreeeeey

    I just got an update and the fields from the PayPal Card Processing are “hosted fields”, which means the labeling, etc. comes directly from PayPal.

    That’s why they currently cannot be modified directly in the plugin or via code. But we received many complaints about it and are in contact with PayPal to improve it.

    We will try to get feedback from PayPal asap so that issue can be fixed.

    Best regards
    Andreas

    Thread Starter Tom

    (@jeffreeeeey)

    Hi

    Noticed that there’s also some errors:

    [19-Apr-2021 15:08:47 UTC] PHP Parse error:  syntax error, unexpected '(' in /home/HIDDEN/HIDDEN-URL/v1/wp-content/plugins/woocommerce-paypal-payments/woocommerce-paypal-payments.php on line 64
[19-Apr-2021 15:08:48 UTC] PHP Parse error:  syntax error, unexpected '(' in /home/HIDDEN/HIDDEN-URL//v1/wp-content/plugins/woocommerce-paypal-payments/woocommerce-paypal-payments.php on line 64
[19-Apr-2021 15:08:50 UTC] PHP Parse error:  syntax error, unexpected '(' in /home/HIDDEN/HIDDEN-URL/v1/wp-content/plugins/woocommerce-paypal-payments/woocommerce-paypal-payments.php on line 64
[19-Apr-2021 15:08:51 UTC] PHP Parse error:  syntax error, unexpected '(' in /home/HIDDEN/HIDDEN-URL/v1/wp-content/plugins/woocommerce-paypal-payments/woocommerce-paypal-payments.php on line 64
[19-Apr-2021 15:08:59 UTC] PHP Fatal error:  strict_types declaration must be the very first statement in the script in /home/HIDDEN/HIDDEN-URL/v1/wp-content/plugins/woocommerce-paypal-payments/woocommerce-paypal-payments.php on line 17
[19-Apr-2021 15:09:02 UTC] PHP Fatal error:  strict_types declaration must be the very first statement in the script in /home/HIDDEN/HIDDEN-URL/v1/wp-content/plugins/woocommerce-paypal-payments/woocommerce-paypal-payments.php on line 17
[19-Apr-2021 15:09:30 UTC] PHP Fatal error:  strict_types declaration must be the very first statement in the script in /home/HIDDEN/HIDDEN-URL/v1/wp-content/plugins/woocommerce-paypal-payments/woocommerce-paypal-payments.php on line 17
[19-Apr-2021 15:12:26 UTC] PHP Fatal error:  strict_types declaration must be the very first statement in the script in /home/HIDDEN/HIDDEN-URL/v1/wp-content/plugins/woocommerce-paypal-payments/woocommerce-paypal-payments.php on line 17
[19-Apr-2021 15:12:44 UTC] PHP Fatal error:  strict_types declaration must be the very first statement in the script in /home/HIDDEN/HIDDEN-URL/v1/wp-content/plugins/woocommerce-paypal-payments/woocommerce-paypal-payments.php on line 17
[19-Apr-2021 15:12:51 UTC] PHP Fatal error:  strict_types declaration must be the very first statement in the script in /home/HIDDEN/HIDDEN-URL/v1/wp-content/plugins/woocommerce-paypal-payments/woocommerce-paypal-payments.php on line 17
    Plugin Support Andreas W.

    (@aweissinpsyde)

    Hello @jeffreeeeey

    what PHP version are you using? Can you please try it with 7.4.x

    Thank you
    Regards
    Andreas

    Thread Starter Tom

    (@jeffreeeeey)

    Hi. Server currently running version 7.2 but in 5-10 days time once we have moved server we will be able to try using 7.4. Everything else however seems to be running perfectly on 7.2 at present

    Plugin Support Andreas W.

    (@aweissinpsyde)

    Hello @jeffreeeeey

    please ping me when you are able to use 7.4.

    Thank you
    Regards
    Andreas

    Thread Starter Tom

    (@jeffreeeeey)

    Sorry I’ll need to disable this plugin because checkout abandonment has increased by 52% since it was installed. This equates to a substantial amount of lost revenue.

    By the way – this plugin also seems to trigger two emails to the customer when they pay by Credit/ Debit card (directly on the WC site)…
    The customer receives both an *order on hold* email and also an *order processing* email. Both are sent immediately after payment is made by card.
    This has also confused customers.

    This plugin really isn’t fit to be used in a live environment in my opinion.
    There is no way that I can leave this on a live site with such a severe impact on conversions.

    I suggest that anyone using this plugin monitors their conversion rates very closely.

    Plugin Support Andreas W.

    (@aweissinpsyde)

    Hello,

    yes, please give it a try. About the emails. Please check your WooCommerce setting > Emails. There you can set up when WooCommerce will send an email. Our plugin itself does not send emails.

    Regards
    Andreas

    Thread Starter Tom

    (@jeffreeeeey)

    Hi Andreas,

    I acknowledge that the plugin doesn’t send emails, but are you absolutely certain that this plugin is not triggering emails?

    I ask because…
    Prior to switching to this plugin for Payment processing a customer would only receive the ORDER PROCESSING email immediately after payment.

    Since adding this plugin the customer now receives both an ON HOLD email and also the ORDER PROCESSING email. Both emails are sent immediately after paying by Credit/ Debit Card (but not when paying through PayPal). The emails are send seconds apart – ON HOLD email first and then ORDER PROCESSING email.

    The on hold email says:
    Thanks for your order. It’s on-hold until we confirm that payment has been received. In the meantime, here’s a reminder of what you ordered

    Then the order processing email says:
    Just to let you know — we’ve received your order #BSOC-5426, and it is now being processed:

    So it seems there is a very short delay in the card payment being confirmed, and so it is causing WC to send out that first email.

    I have tried disabling this plugin and running through an order myself. With the plugin disabled, only an ORDER PROCESSING email is being sent. So to me, this says that your plugin is either triggering the ON HOLD email for some reason, or there is a conflict somewhere?

    WooCommerce itself, in settings -> emails allows you to choose who receives each email. The NEW ORDER email for example, has a RECIPIENT field, but on the ON-HOLD email there is no recipient field and so it cannot be changed or disabled. It automatically sends such emails to the customer as default.
    I believe this can be overridden by unhooking via the themes functions.php file:
    https://docs.woocommerce.com/document/unhookremove-woocommerce-emails/

    But if I unhook the ON HOLD emails – it will also stop them being sent in the event we need to manually mark an order as ON HOLD.

    Plugin Support Andreas W.

    (@aweissinpsyde)

    Hello @jeffreeeeey

    how you can see here the status will be managed by WooCommere (on hold) and in your case the store owner (processing) https://www.ads-software.com/support/topic/error-processing-checkout-please-try-again-40/

    To send two is correct but I get what you mean.

    Maybe you can try these hooks: https://docs.woocommerce.com/document/unhookremove-woocommerce-emails/ but deactivate the hook you don’t want.

    Please note with these hooks no emails will be sent out. You have to set comment them when you want to use it.

    Best regards
    Andreas

    Thread Starter Tom

    (@jeffreeeeey)

    Hi Andreas,

    The order ON HOLD emails still need to be sent out, in the event an order is manually placed on hold. So to deactivate those emails via hooks does not really solve the problem.

    I have also now added Stripe for card payments and using Stripe does not send the customers two emails…
    Eg.
    1) order on hold, and
    2) order processing

    It only sends the:
    2) order processing
    …email.

    This is exactly how it should work. Surely?
    Or at least this is how every other payment processor that I’ve used in WooCommerce has worked.

    Conversions also increased overnight since swapping out this plugin for the Stripe plugin/ payment processing. And in the last week, conversions are up by 23%, so I hope you can pass on these comments to the development team because this plugin clearly needs serious work before anyone in their right mind would use it in a production environment. The lost revenue for the short time of which I used this plugin backs this up.

    Not sure if it matters but it may help:
    – I am in the UK
    – ‘PayPal Payments Pro’ was not available to me as I am using a new PayPal business account and so PayPal insisted that I use their new PPCP for Card Processing. Unless I went for Braintree, PPCP is apparently now the only option. Or at least, in the UK.

    I will keep an eye on this plugin and may resort back to it in future but I cannot experiment with this plugin in a live production environment for the simple fact it’s lost me a ton of money.

    Best regards

    Plugin Support Andreas W.

    (@aweissinpsyde)

    Hello @jeffreeeeey

    thank you for your feedback. PayPal and our team will do our best the make the plugin more stable with future updates.

    I’ll discuss this with our dev team so we can have a closer look at it.

    Have a nice day
    Best regards
    Andreas

    Plugin Support Andreas W.

    (@aweissinpsyde)

    Some fixes will comes with the next update asap

Viewing 14 replies - 1 through 14 (of 14 total)
  • The topic ‘Card recognition not working / Card Code phrase’ is closed to new replies.