This path applies to customers who:

• Want to maintain control over their checkout page and overall UX.
• Prefer Zuora to handle tokenization, orchestration, and the direct gateway integration to PayPal Complete Payments.
• Want a direct replacement for a PayPal‑hosted SDK button embedded in their own site.

With this path:

• You embed a Zuora‑provided JavaScript SDK that renders PayPal wallet payment buttons within your checkout flow.
• You still own the page layout, flows, and non‑PayPal UI components.
• Zuora manages the PayPal Complete Payments integration, tokenization, and payment orchestration.

Key behaviors

• Zuora automatically creates Vault tokens (not BAIDs) for PayPal wallet payment methods.
• Transactions originate in Zuora and are logged as Electronic payments, simplifying reporting and audit.
• You do not need to manage low‑level PayPal API calls or PayPal SDK versions yourself.

Benefits

• A more direct replacement for a PayPal‑hosted SDK with:
  • Fewer API calls and fewer moving parts between your site, PayPal, and Zuora.
  • Streamlined reconciliation because payments are created as Electronic in Zuora, not as “External” records that must be imported.
• Built‑in access to Zuora’s PayPal‑related roadmap, including:
  • PayPal App Switch.
  • PayPal Recurring Payments Module (subscription presentment in the PayPal context).
• Centralized orchestration and reporting in Zuora across payment methods and gateways.

This path is recommended if you want to keep your own checkout page but want Zuora to own the PayPal integration and tokenization lifecycle.