A4A: Send WordPress.com purchases to the Needs setup page after BD checkout

[jkguidaven]

Related to https://linear.app/a8c/issue/A4A-3165/a4a-wpcom-flow-efficiency-improvements

Proposed Changes

• Bring the Billing Dragon checkout to parity with the legacy purchase flow for WordPress.com purchases.
• After buying a WordPress.com plan, agencies now land on the “Needs setup” page with the purchase confirmation banner, instead of the licenses list.
• The mini-cart now clears on the “Needs setup” page too, so it still empties after a successful purchase.

Why are these changes being made?

• The legacy flow already sent WordPress.com purchases straight to “Needs setup,” where agencies get a confirmation that the purchase went through and can immediately create their site. That behaviour was never carried over when checkout moved to Billing Dragon.
• As a result, agencies buying a WordPress.com plan today are dropped on the licenses list with no confirmation and no obvious next step — they have to work out on their own that the site still needs to be created.
• This restores the original, more guided experience rather than introducing anything new.

Testing Instructions

• Add a WordPress.com plan to the cart in the marketplace and complete checkout.
• Confirm you land on the “Needs setup” page and see the purchase confirmation banner.

• Confirm the mini-cart is empty afterwards.
• Repeat with a cart containing only non-WordPress.com products (e.g. a Jetpack license) and confirm you still land on the licenses list as before.

Pre-merge Checklist

• Has the general commit checklist been followed? (PCYsg-hS-p2)
• Have you written new tests for your changes?
• Have you tested the feature in Simple (P9HQHe-k8-p2), Atomic (P9HQHe-jW-p2), and self-hosted Jetpack sites (PCYsg-g6b-p2)?
• Have you checked for TypeScript, React or other console errors?
• For UI changes, have you tested the affected components in dark mode?
• Have you tested accessibility for your changes? Ensure the feature remains usable with various user agents (e.g., browsers), interfaces (e.g., keyboard navigation), and assistive technologies (e.g., screen readers) (PCYsg-S3g-p2).
• Have you used memoizing on expensive computations? More info in Memoizing with create-selector and Using memoizing selectors and Our Approach to Data
• Have we added the "[Status] String Freeze" label as soon as any new strings were ready for translation (p4TIVU-5Jq-p2)?
  • For UI changes, have we tested the change in various languages (for example, ES, PT, FR, or DE)? The length of text and words vary significantly between languages.
• For changes affecting Jetpack: Have we added the "[Status] Needs Privacy Updates" label if this pull request changes what data or activity we track or use (p4TIVU-aUh-p2)?

[matticbot]

WordPress.com

• Dashboard Live (direct link)

  https://calypso.live?image=registry.a8c.com/calypso/app:build-192074&env=dashboard

• Calypso Live (/home) (direct link)

  https://calypso.live/home?image=registry.a8c.com/calypso/app:build-192074

---

Automattic for Agencies

• Dashboard Live (direct link)

  https://calypso.live?image=registry.a8c.com/calypso/app:build-192074&env=dashboard-a4a

• Automattic for Agencies Live (direct link)

  https://calypso.live?image=registry.a8c.com/calypso/app:build-192074&env=a8c-for-agencies

---

Jetpack Cloud Live (direct link)

https://calypso.live?image=registry.a8c.com/calypso/app:build-192074&env=jetpack