Stripe Laravel Package

Product Decisions This Supports

• Payments architecture (build vs. buy): Deciding to accept Stripe payments through a maintained, pluggable driver rather than hand-rolling a Stripe integration. This package is Lunar's Stripe payment driver, so the real decision is "adopt Lunar's driver layer" versus writing custom Stripe code (payment intents, refunds, webhooks, SCA/3DS).
• Platform/stack commitment: It is only useful if you've committed to Laravel + Lunar for commerce. Adopting this driver effectively locks in that stack choice, so treat it as a downstream consequence of a larger "which commerce framework" decision (Lunar vs. Shopify/Saleor/Medusa vs. custom).
• Feature scoping: Helps define what payment capabilities are in-scope out of the box (card payments, payment intents, refunds) versus what would need custom development (subscriptions/recurring billing, marketplaces/Stripe Connect, multi-currency, wallets).
• Roadmap and risk mapping: Because the description says "[READ ONLY] Subtree split of the Stripe payments driver (see lunarphp/lunar)," the adoption signal, issue tracker, and release cadence all live in the parent repo, not here. Roadmap and support decisions should be driven by lunarphp/lunar activity — the 20-star count on this split is not a meaningful adoption metric.
• Vendor/support risk: Informs decisions about acceptable dependency risk (community-supported, open source) and whether a fallback path (e.g., stripe/stripe-php directly, or Laravel Cashier for subscriptions) should be planned.

When to Consider This Package

Consider it when:

• You're building (or already run) a Laravel + Lunar storefront and need Stripe as the payment provider.
• You want a standard, maintained driver instead of bespoke Stripe integration code, and your team is comfortable with PHP/Laravel and the Stripe API.
• You're fine with a community-supported open-source dependency and can absorb the support model (issues/PRs go to the parent lunarphp/lunar repo).

Look elsewhere when:

• You are not using Lunar — use stripe/stripe-php directly, or Laravel Cashier if subscriptions/recurring billing is core.
• Your needs are subscriptions, marketplaces/Connect, or complex split payments, which typically require more specialized tooling than a base payment driver.
• You require an enterprise SLA or vendor-backed support.
• You're on a non-Laravel stack — the package is irrelevant.
• You need to evaluate it as a standalone project: this is a read-only subtree split, so don't judge it by its own stars, issues, or releases. Base the go/no-go on the parent repo's health, maintainer activity, and release history.

How to Pitch It (Stakeholders)

To executives: Adopting this driver lets our Laravel-based store accept Stripe payments through a standard, maintained integration instead of custom code — reducing integration cost, time-to-market, and maintenance risk. It's a module of the Lunar commerce framework, so the real investment is our platform choice, not a niche library. Caveat: it's community-supported and a read-only split of a larger repo, so we should validate the parent project's activity and keep a documented fallback (direct Stripe SDK) if support or coverage falls short.

To engineering: This is Lunar's Stripe payment driver — it wraps Stripe APIs (payment intents, refunds, webhooks) behind a driver interface so we avoid bespoke integration. Adopt it where we're already on Lunar, keep a thin abstraction so the driver can be swapped, and route issues/PRs to lunarphp/lunar rather than this read-only package. Confirm coverage against our feature list (subscriptions, Connect, multi-currency) before committing.