-
Notifications
You must be signed in to change notification settings - Fork 125
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
STL : Component / drop-in integration - Card Number, Security Code, Expiry date fields are disabled #2124
Comments
Hi @spbpraveen I wonder, do you experience the same issue if you run your environment at And, can you try setting
|
Hi @sponglord, Thank you for your reply! We are on https://localhost which is our local workspace where our application is running, and with our current setup it is not possible to hit the localhost with http://. We tried setting forceCompat: true in the paymentMethodsConfiguration - even in this scenario, the behavior is same. Thanks. |
Hi @spbpraveen, are there any errors in the console that you could include in a screenshot? |
Hi @ossiggy Thanks. |
Hi @spbpraveen - can you see from the Network tab whether the securedFields files are actually getting successfully loaded (including, what the response looks like). |
Hi @sponglord , What do you mean by CookieBot or the cookie consent library here ? As requested, we will share the Network tab to confirm the secureFields loading and response - as a video. Thanks. |
In short, it assesses your website for cookies and whether the user has given consent for them. However, since you're asking what it is, I guess that means you're not using it! ;-) |
Hi @sponglord , It seems like an issue with an endpoint. Could you please advise further on this. URL:https://checkoutshopper-test.adyen.com/checkoutshopper/securedfields/test_FAIM6BH3QJBALDEBKWGHQZMBAEDJ5EZH/4.4.1/securedFields.html?type=cardCompat&d=aHR0cHM6Ly9sb2NhbGhvc3QuY2hjYXJvbGluYWhlcnJlcmEuY29t |
Hi @spbpraveen - following the error you get
Have you done this? Are you sure that you've set Because it really looks like your clientKey ( |
Hi @sponglord, We have verified the ClientKey in our TEST CA and origins allowed. PFB information. Client-key: test_FAIM6BH3QJBALDEBKWGHQZMBAEDJ5EZH PFA for your reference of the configured allowed origins. Under accounts- Please review and let us know if this configuration is ok, and also let us know what further information is required. Thanks. |
Hi @spbpraveen - are you sure it's not working now? Or at least something has changed? Before, when I ran the URL from your previous post: https://checkoutshopper-test.adyen.com/checkoutshopper/securedfields/test_FAIM6BH3QJBALDEBKWGHQZMBAEDJ5EZH/4.4.1/securedFields.html?type=cardCompat&d=aHR0cHM6Ly9sb2NhbGhvc3QuY2hjYXJvbGluYWhlcnJlcmEuY29t |
Hi @sponglord , Thanks. |
Hi @spbpraveen - I'm running your url again: https://checkoutshopper-test.adyen.com/checkoutshopper/securedfields/test_FAIM6BH3QJBALDEBKWGHQZMBAEDJ5EZH/4.4.1/securedFields.html?type=cardCompat&d=aHR0cHM6Ly9sb2NhbGhvc3QuY2hjYXJvbGluYWhlcnJlcmEuY29t and once again I'm getting an "invalid origin" response: Can you please paste the above url into Chrome and send me a screenshot of what the "Preview" and "Response" tabs show (from the Developers console). And then do the same for your test website (for the It would also be interesting to see, for the thanks |
Alternatively, or in addition, can you expose any kind of url that we can test/debug with? |
This is not possible for us to expose our localhost URL. |
We are also getting the same response.
I believe I have already copied the request and response in a txt file and attached with this ticket. Thanks, |
Hi Bala, What I need is a copy of the Request and Response Headers when the securedField.html file is loaded. Please generate a
thanks |
Hi @sponglord |
@spbpraveen any updates on this? |
Hi @ribeiroguilherme - we will provide an update by coming Monday EOD with the necessary information. Thank you! |
Hi @ribeiroguilherme , This is Raja from STL team I have performed the task asked by u earlier to Bala . Here are the files you have asked for. Response.txt |
@spbpraveen Sorry to chip in here. We have this exact issue. If user only accepts the required cookies, Adyen iFrames failed to load. I was trying to add Adyen cookie to Necessary cookies categories, but I couldn't find the information about the cookie used for rendering the iframes. Am I on the right direction? Could you share the proper solution for this? |
Check your CA configuration if you get
|
@rmahoa - everything in you request/response seems to be ok. If I run the url: https://checkoutshopper-test.adyen.com/checkoutshopper/securedfields/test_FAIM6BH3QJBALDEBKWGHQZMBAEDJ5EZH/4.4.1/securedFields.html?type=cardCompat&d=aHR0cHM6Ly9sb2NhbGhvc3QuY2hjYXJvbGluYWhlcnJlcmEuY29t in its own window/tab - I no longer get an So everything seems to be working correctly from our end. Without the possibility of exposing a url on which we can directly debug, I think perhaps it is now the time to contact out support team (https://www.adyen.help/hc/en-us/requests/new) and they can run through the entire process with you |
Hi all, is there any update regarding this one. We had reports of this behavior on our site for some time. Here is is the example video from one customer , hope it helps https://www.youtube.com/watch?v=B70BcackH50 |
@nenadepam - the video you share shows a different issue: the securedFields render but then disappear. Will you please create a new, separate issue - detailing how we can recreate it; and we will look into it. |
Hi @sponglord tnx for response, here is the new separate issue #2529 |
Component / drop-in integration - Card Number, Security Code, Expiry date fields are disabled
We are using the version v5.39.0 and SDK version v68 /sessions API to retrieve the session ID and session Data for our merchant reference through simple Java API call (we are not using react ).
• We have generated the client-key as per the instructions provided in documentation - https://docs.adyen.com/development-resources/client-side-authentication#get-your-client-key - also the necessary origins are added.
In both, component integration and drop-in integration – we are successfully able to load the UI by passing the session ID, Data and client-key.
i.e,
What we are observing in both is – we are unable to access the Card number fields, CVV field, Expiry fields and it is not enabled. Like, we are unable to enter any number in the fields.
Could you please us on this issue ?
To Reproduce
Steps to reproduce the behavior:
Expected behavior
User should be able to enter the card number, expiry date, security code in both Drop-in / Component integration.
Screenshots
Desktop (please complete the following information):
console-browser.webm
The text was updated successfully, but these errors were encountered: