• Resolved Barry Brunning

    (@datastream)


    On our site, we’re don’t allow guest checkout. We want to allow Apple Pay but only for the customer to have some specific conveniences of Apple Pay (not entering credit card details, having payment on Apple Pay history). Hence essentially what we want is the flow on the checkout page to be identical, whether the customer enters her credit card details or clicks ‘Buy with Apple Pay’. Everything else should be the same, login if you’re a returning customer or complete details for automatic account creation if not logged in.

    After searching forums, Googling, etc, plenty of people seem to have asked essentially this question, but I can’t see it’s been answered precisely. We’ve added the code to have the Apple Pay button only on the checkout page and that’s all good, but that schematically results in a logical OR at too high a level.
    —————————————-
    Returning customer? Click here to login

    “Buy with Apple Pay”

    — OR —

    Billing Details ………
    ________________________________________

    So now (1) if you login as a returning customer, the Apple Pay button disappears. (2) if you’re not logged in and if you click ‘Buy with Apple Pay’, the sale fails (Payment not completed), presumably because the customer details to create the account haven’t been entered. But (3) if one logs in first so all the checkout details are known, then the Apple Pay transaction is successful.

    We are seeking a way in case (1) to refresh with the Apple Pay button again showing, and in case (2) for the flow to continue to the Billing Details.

    In asking this, I see many instances of essentially the same question with the Apple Pay flow. That is, wanting Apple Pay at checkout and insisting on account creation at that stage for non-logged in users. I just don’t see a clear answer anywhere.

    This issue has been raised a sufficient number of times from what I can see, that the answer should not be to consider hiring a developer to achieve what we desire. If necessary we have such resources, but surely this is not a case for recourse to that with such a clear procedural need for a solution for many many sites.

    We haven’t put a link, because at present Apple Pay is turned off, because it’s essentially unusable.

    Thank you

Viewing 3 replies - 1 through 3 (of 3 total)
  • laceyrod

    (@laceyrod)

    Automattic Happiness Engineer

    Hi there,

    Thanks for reaching out.

    I’m not sure I’m fully clear on what’s going on, but it sounds like you are wanting Apple Pay on checkout to require logging in before paying, is that correct?

    If so, I’m assuming you were able to get the Payment Request (Apple Pay) button on checkout, since it’s not included there by default?: https://docs.woocommerce.com/document/stripe/#section-23

    And I see once this is added, the Apple Pay button is at the top of the page, which skips the checkout information and required login. Do I have this correct?

    Would something like moving the Apple Pay button to the bottom of checkout work for you? Here’s a guide that a colleague of mine wrote that outlines the customizations needed for this: https://remicorson.com/woocommerce-apple-pay-move-buttons-below-customer-details/

    I haven’t tested it yet, so I’m not sure how it plays with required logins, but let me know if this is something that would work!

    Thread Starter Barry Brunning

    (@datastream)

    Hi laceyrod,

    Thank you for your reply. Keeping it as simple as possible, yes I’m trying to get the Apple Pay button below the customer details as Remi Corson’s post claims to do. However, his code doesn’t work and I note it’s flagged, below the date “This might be outdated”.

    The big thing that’s being missed here is that often one needs the customer details to work out the final price, because postage, among other things, can depend on it. So, in such a circumstance, having the Apple Pay button before the customer details is useless. This can’t be such an unusual circumstance, (and the issue has been raised by others) and I continue to be puzzled at the lack of a solution, even the fact that it’s not just simply an option.

    It would be terrific if the Stripe Payment Gateway team could give consideration to providing a solution.

    Regards,
    Barry

    laceyrod

    (@laceyrod)

    Automattic Happiness Engineer

    Hi @datastream

    Thanks for your feedback. I would recommend posting this as an enhancement request in the public Stripe repo where our developers scan here: https://github.com/woocommerce/woocommerce-gateway-stripe.

    I can also recommend the following resources for more development-oriented questions:

    – WooCommerce Slack Community: https://woocommerce.com/community-slack/
    – Advanced WooCommerce group on Facebook: https://www.facebook.com/groups/advanced.woocommerce/

    Since this thread has been open for a bit without any further comments, I’m going to mark it as Resolved at this time. Thanks for your understanding.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Stripe Apple Pay but no Guest Checkout’ is closed to new replies.