This path applies if you:

• Are currently using PayPal’s own hosted SDK directly (outside of Zuora) as their primary checkout experience.
• Push PayPal payment data into Zuora after the fact, for example by creating payments with existing tokens.

What it means

If you choose this path:

• You continue to manage the PayPal integration outside of Zuora.
• You retain full control over the checkout experience, error handling, and upgrade cadence.
• You are responsible for keeping up with PayPal API changes and migration requirements.

Implications

• Ownership and customization

• You have maximum flexibility over the UI and UX.
• You must own any UX, compliance, and accessibility changes required by PayPal.

• Zuora enhancements and roadmap features

• You will have limited ability to leverage Zuora enhancements that are built on top of Zuora‑managed experiences, such as:
  • PayPal App Switch (native redirect to the PayPal app).
  • PayPal Recurring Payments Module and related checkout presentment features.
• New PayPal‑related capabilities in Zuora may require Payment Forms or the JavaScript SDK integration.

• Tokenization and BAIDs
  • You can continue generating and passing Billing Agreement IDs (BAIDs) from PayPal into Zuora for now.
  • Zuora will automatically migrate BAIDs to PayPal Vault tokens when supported by PayPal Complete Payments.
  • Long‑term support for BAIDs is uncertain. To future‑proof your integration, plan to move to Vault IDs (tokens) instead of relying on BAIDs indefinitely.

This path is best suited for customers who are comfortable with owning the PayPal integration end‑to‑end and are willing to accept more long‑term maintenance.