Migrated from Redmine #912 | Author: edwin ko
Status: Feedback | Priority: Normal | Created: 2022-07-25
Dear,
we meet a problem as below
if we use the ios device and your website will show the cookies. and cuz your 3D secure is using iframe on the website, it will cause the transaction false.
could you please open a new page for the 3D secure payment url? then it will fix the problem.
Dmytro Bondarev wrote:
Hi,
You should contact to tappay with isuue, we implemented it by their documentation.
edwin ko wrote:
Dmitry Bondarev wrote:
Hi,
You should contact to tappay with isuue, we implemented it by their documentation.
I am TapPay sales Edwin. i think our documentation didn’t show the 3D secure use iframe insert to the website. or could you please provide which part so that we can discuss about that.
Dmytro Bondarev wrote:
Can you please provide URL where we can check it?
As i see in our code we do not use any iframes in tappay integration, so i thought that it was created on your end.
edwin ko wrote:
please refer to our website.
Dmitry Bondarev wrote:
Can you please provide URL where we can check it?
As i see in our code we do not use any iframes in tappay integration, so i thought that it was created on your end.
please refer to our website and attached photo. bank will send the payment url for Tappay, TapPay will send this url for simplybook, and simplybook will send the url to customer.
Dmytro Bondarev wrote:
No, i meant url, where user has an error.
edwin ko wrote:
Dmitry Bondarev wrote:
No, i meant url, where user has an error.
please refer to attached photo, the page show the browser has problem. this 3D secure need to open a new page then it can avoid the cookies.
Dmytro Bondarev wrote:
Sorry, seems you are not able to attach screenshot.
Please provide link, where we can check it or ask customer to contact to live chat.
edwin ko wrote:
Dmitry Bondarev wrote:
Sorry, seems you are not able to attach screenshot.
Please provide link, where we can check it or ask customer to contact to live chat.
Dmytro Bondarev wrote:
But as you see there is not our domain. Seems they are using widget or iframe.
We do ask for 3rd party cookies when we show widget before booking process, but this is not our window and not our message.
so please explain workaround with your payment system to avoid this.
edwin ko wrote:
Dmitry Bondarev wrote:
But as you see there is not our domain. Seems they are using widget or iframe.
We do ask for 3rd party cookies when we show widget before booking process, but this is not our window and not our message.
so please explain workaround with your payment system to avoid this.
noted with thanks