Hi there! I’m using a custom checkout extension that uses the useBuyerJourneyIntercept function. It works great during the standard checkout flow: the extension blocks the process when required data is missing - but I’ve noticed that if a customer chooses Apple Pay, the block seems to be bypassed entirely. Is there any way to ensure the same blocking behavior is applied when Apple Pay is used?
1 Like
Hey @sekmo
Are you using client side validations? The reason I ask is this is noted at the top of our docs here:
Blocking checkout progress behavior doesn’t apply to express checkout options, such as Shop Pay, Google Pay, and Apple Pay.
Hey, just checking in to see if the above helped clarify this limitation.
Hi Kyle, thanks for your response!
Yes, I’m doing client-side validation through useBuyerJourneyIntercept.
Looks like that with express checkout the only way would be to implement server-side validation.
1 Like