• Resolved mikolajk1

    (@mikolajk1)


    Hi there,

    I have a problem with Apple pay method from Stripe plugin. It works just fine with basic woocommerce checkout page (I’m using Woostify as a theme but I don’t think that it is the source of a problem) but at the point where I want to use checkout page plugin to modify checkout fields it won’t work anymore.

    I need to change phone number field to required and after doing that in checkout page plugin, I’m getting errors from Apple pay saying that users phone number is required which is weird because it should work in fast checkout without filling actual checkout.

    I tested out a lot of checkout plugins and problem is always the same.

    Hope you can help me.

    Have a nice day!

    The page I need help with: [log in to see the link]

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Support shahzeen(woo-hc)

    (@shahzeenfarooq)

    Hi there!

    Thank you for explaining the issue. It seems like the conflict is happening when the checkout page plugin makes the phone number field required, causing Apple Pay to display errors.

    To help resolve this, I recommend checking if the checkout plugin you’re using has an option to exclude Apple Pay from custom field requirements. Alternatively, you can reach out to the plugin developer to ensure compatibility with fast checkout methods like Apple Pay.

    If that does not help, you may need to use a custom code to make your number field as required without any plugin so it will effect Apple pay.

    Please note that we do not provide support for custom code. You may want to hire a developer or seek assistance from the Facebook community.
    Here are some useful links:

    Thank you for your cooperation and understanding.


    Plugin Support Feten L. a11n

    (@fetenlakhal)

    Hello!

    We haven’t received a response from you, so I’ll go ahead and close this for now. Feel free to reach out whenever you’re ready to continue.

Viewing 2 replies - 1 through 2 (of 2 total)
  • You must be logged in to reply to this topic.