PayPal Lifecycle Definition
Last updated: Jul 30th, 11:26am
PayPal Open is a significant step in modernizing our platform. It brings together merchant-focused solutions like PayPal Checkout, Venmo, Fastlane, Pay Later options, financial services, and risk management tools into one seamless experience. Our commitment to delivering top-tier, high-converting consumer experiences also benefits your business. As we move to our unified platform, we are phasing out support for older integrations, with full completion set for the end of 2026. We are already working with merchants and partners using outdated integrations to ensure minimal disruption to their customers.
Lifecycle Stages
The following stages define how PayPal manages the lifecycle of offerings on our platform. These stages apply to products, features, interfaces, and interface elements (e.g., methods, objects, fields, enum values). As offerings move through these stages, their availability and support levels will change. Once an offering moves from the Current state, it is on the path to retirement and should not be used for new integrations without specific guidance from PayPal. We encourage transitioning to the appropriate replacement offering.
Beta
Beta offerings are available to give customers early access to new functionality. While Beta offerings are stable, they are still in development and may undergo significant changes before finalization. Additionally, a Beta offering might not succeed and could be moved directly to Retired. You should be prepared to update any integration using a Beta offering.
Current
Current offerings are fully developed, production-ready, and available for use by eligible customers. They should be used for all new integrations with the PayPal platform. Current offerings are fully supported and will receive new functionality and fixes. Use these offerings for all new integrations.
Legacy
An offering is classified as Legacy when it has been replaced by a newer offering that does not yet cover all of its use cases. Legacy offerings are still supported, receive bug and security fixes, and may be updated with new functionality. Only integrate with a Legacy offering if the newer offering does not meet your requirements. Contact PayPal before using a Legacy offering for new integrations.
Deprecated
Deprecated offerings are still available and fully functional, but have limited support and should not be used for new integrations. They will only receive security fixes, with no new functionality added. Documentation will include references to replacement offerings. Migrate to the replacement offering as soon as possible for existing integrations.
Deprecated offerings will generally be supported and remain operational for at least 12 months before retirement, though they may be retired sooner due to security or compliance issues. A list of deprecated products, features, and interface versions can be found here.
Deprecated interface elements will be labeled as such in the relevant reference documentation. For versioned interfaces, Deprecated elements will be retired in the next major version. For evergreen interfaces, Deprecated elements may be retired once they are no longer in use, unless a security or compliance issue requires earlier retirement.
Retired
Retired offerings are no longer available for use. Integrations are not possible, and existing integrations will cease to function. Documentation for retired offerings will be removed.