# JSONP legacy protocol deprecation

The JSONP communication protocol is a legacy protocol that very old versions of browsers rely on. We are ending support for JSONP in our APIs.
## **What this means for you**
If your integration uses Stripe.js, it may have cached a version of the library from multiple years ago. This would be a common reason as to why your code is using JSONP instead of a more recent protocol. If this is the case, it means that a handful of requests submitted by very old devices might fail when entering card details in your application. If you know your code is caching Stripe.js, we recommend replacing the code with the latest version found at [https://js.stripe.com/v2](https://js.stripe.com/v2) to resolve the issue.
Alternatively, you can use [Stripe Checkout](https://stripe.com/payments/checkout) or [Payment Links](https://stripe.com/payments/payment-links) to collect payment from your customers, which will automatically ensure your integration is using the latest browser technology.
## **More detail about this change**
[JSONP](https://en.wikipedia.org/wiki/JSONP) is a legacy technology that has been deprecated by modern browsers for many years. To date, Stripe has maintained support for this technology to ensure backwards compatibility for very old browsers such as Internet Explorer 6 (today, this accounts for less than 0.01% of users on the Internet). Over the past few years, newer browsers have instead adopted [CORS (Cross-Origin Resource Sharing)](https://en.wikipedia.org/wiki/Cross-origin_resource_sharing), which is a more secure and improved solution.