-
Notifications
You must be signed in to change notification settings - Fork 71
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
[Bug] Debit or Credit Card section not loading after click the button #488
Comments
I have the same problem, it seems to be only happening on Sandbox account and is also country-specific. It started to appear consistently (although not on every test) about a month ago. |
We have also encountered the same problem. Do you have a good solution? Or reduce the probability of interface errors? |
We have an internal live issue tracking this bug, there is a team looking into the fix now. I'll update this ticket when the fix has been identified and again when it is deployed |
Thank you for your reply. We look forward to receiving updates from the PayPal team regarding this issue. |
Library used
paypal-js
🐞 Describe the Bug
When clicking the Debit or Credit Card button too quickly after the page loads, the credit card page fails to load. It's very intermittened but I can see that the error stems from a HTTP 400 error coming back from /smart/card-fields endpoint when the SDK tries to render the credit card iframe.
This issue is reproducible on your demo checkout page here: https://developer.paypal.com/demo/checkout/#/pattern/validation
🔬 Minimal Reproduction
Please note that it doesn't happen all the time. I often have to try multiple times before I'm able to reproduce it.
😕 Actual Behavior
Spinner appears and spins endlessly
🤔 Expected Behavior
Spinner should appear briefly while it loads the credit card form but then it should disappear and the form should be visible.
🌍 Environment
➕ Additional Context
I've attached a screenshot of the error happening on your official demo page.
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: