We have developed a subscription app. Whenever a billing attempt on a subscription contract fails, we trigger the customerPaymentMethodSendUpdateEmail, which will send an email to the user.
The email contains a URL that takes the user to a page similar to the checkout page. It has the same layout. See the image below:
Then the user adds the new payment details and presses "Update Card".
Then it will follow the payment steps based on his card provider and hopefully should see a success message at the end.
However, they see this: "Please enable coolies to continue"
I have also attached a video.
I can ensure that cookies are enabled.
This issue happens with Safari -the latest version- on desktop and iOS -the latest version- Safari and Chrome. We haven't tested further.
Has anyone experienced this issue? Any help will be appreciated.
In the video, I see that after payment the browser is redirected to checkout.domain.com.
Was the user on another domain before or the same one ?
Is this happening only with Safari ?
The user accesses the page by clicking on the link sent in the email. On the video, I am skipping the previous page because contains the details of a real card. Happy to share the full video privately.
The domain to which is redirected it is the same as it lands after clicking on the email.
In the video you sent, it seems like the redirect from the payment processor happens on the http, not the https URL.
Can you change it to redirect to the https url ?
Also, what was the payment method used ?
And lastly, is it only happening with Safari ? Other browsers are not affected ?
@Poulping the link is obtained from an email that Shopify sends.
the link has this format:
As far as I know we are not controlling the behavior on this side of Shopify, hence we aren't able to change the redirect to https.
The payment method used is a Visa Credit card through Shopify Payments.
We have only observed this on Desktop Safari and on iOS safari. Not tested on iOS Chrome. It works fine on Desktop Chrome. All for the latest versions.
Any help would be greatly appreciated.
We are being reported that some users also see this issue on Chrome. However, we haven't been able to replicate it.
Hey @polguixe ,
Thanks for all the details, I am forwarding all the information to the right team, and we will get back in touch once resolved, or if we need more information.
@Poulping have you been able to replicate it?
Let me know if you have any questions.