• Resolved barnabas1

    (@barnabas1)


    Hello @mrclayton,

    In the past 2 months, I had 3 orders that were paid using Apple Pay or Google Pay and the order was created with incomplete customer’s details. Only City, country and half of the postcode was captured each time, and once the email and phone number was captured as well. . It’s strange as this does not happen with all the customers who use the express payment methods but only scarcely. One person today verified to me that his address details were filled in correctly in his Apple Pay and he uses Apple Pay often when buying online, but when he placed the order his details were captured fragmented. This is the reason I’m filing this support thread.

    What could be the problem? How can I debug such an issue?

    Kind regards,

    Barnabas

Viewing 3 replies - 16 through 18 (of 18 total)
  • @mrclayton thanks for your reply. I’m just trying to better understand what could be the cause when it so clearly happens to a minority of orders with very specific traits. I shall submit a support ticket ASAP. I appreciate your attention and willingness to look into it regardless of the outcome.

    @barnabas1 I have one other query for you if you don’t mind as we looked primarily at similarities with our plugins previously. I’m wondering now if maybe we’re using the same theme? We’re using Shoptimizer, is this the same for you? Or not the case?

    Thread Starter barnabas1

    (@barnabas1)

    @jackpd I’m using Bricksbuilder myself. So it doesn’t seem to be the case with the theme.

    Did you test the SEO Framework? I didn’t myself because I doubt that it interferes with the wc_order object, or does it @cybr ?

    Also, I only get a couple of orders a day on this store and I’ll have to leave SEO Framework disabled for several days in order to debug, which is not ideal.

    The SEO Framework (TSF) does not interact meaningfully with the WC Order post type other than determining that it is not a post type TSF should support.

    I think it’d be best to follow transaction and error logs. Still, you can try deactivating TSF for several days to see if things improve. If they don’t, it sucks, but at least we know TSF isn’t to blame, and I think we must point our fingers at the theme or, more likely, hosting.

    Because I’m based outside of the USA, setting up a testing environment with Apple Pay hasn’t been easy for me in the past, so I’d love to see some empirical evidence first.

Viewing 3 replies - 16 through 18 (of 18 total)
  • You must be logged in to reply to this topic.