feat(payment): PAYPAL-6499 add wallet buttons

[bc-yaroslav-zhmutskyi]

What/Why?

Add wallet button integration for cart page

Testing

Manual

video_paypal.mp4

Migration

No need

[changeset-bot]

🦋 Changeset detected

Latest commit: fb2e096

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
@bigcommerce/catalyst-core	Minor

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
catalyst	Ready	Preview, Comment	Jul 9, 2026 1:10pm

[github-actions]

Bundle Size Report

Comparing against baseline from 2b7f2cc (2026-07-09).

Metric	Baseline	Current	Delta
Total JS	446.1 kB	447.1 kB	+1 kB (+0.2%)

Per-Route First Load JS

Route	Baseline	Current	Delta
/(default)/cart/page	347.2 kB	348.3 kB	+1.1 kB (+0.3%)

Threshold: 5% increase. Routes with ⚠️ exceed the threshold.

[github-actions]

Unlighthouse Performance Comparison — Vercel

Comparing PR preview deployment Unlighthouse scores vs production Unlighthouse scores.

Summary Score

Aggregate score across all categories as reported by Unlighthouse.

	Prod Desktop	Prod Mobile	Preview Desktop	Preview Mobile
Score	89	92	92	94

Category Scores

Category	Prod Desktop	Prod Mobile	Preview Desktop	Preview Mobile
Performance	74	83	74	69
Accessibility	95	92	95	95
Best Practices	100	100	100	100
SEO	88	100	100	100

Core Web Vitals

Metric	Prod Desktop	Prod Mobile	Preview Desktop	Preview Mobile
LCP	3.7 s	4.7 s	3.7 s	5.7 s
CLS	0.049	0	0.001	0.19
FCP	1.1 s	1.1 s	1.2 s	1.2 s
TBT	10 ms	0 ms	10 ms	0 ms
Max Potential FID	60 ms	40 ms	70 ms	50 ms
Time to Interactive	3.7 s	4.7 s	6.1 s	5.7 s

Full Unlighthouse report →

[bc-nick]

Mention that the related files should be places in the core/public/v1 folder to be able use them via next server in dev mode

[bc-nick]

Also can you please provide some information regarding how the release environment works here? How the release flow should be managed in our case? Probably it should be covered by exp or something before merging.