- What does the Filament Stripe Payment Link plugin do?
- It is a Filament plugin for Laravel that adds an action for generating Stripe payment links from your admin panel. Operators can create and share a payable URL for a product or invoice without leaving Filament or building a custom Stripe workflow. It is a thin presentation-layer convenience: it does not own checkout, model payments in your domain, or replace the Stripe SDK.
- How do I install andreia/filament-stripe-payment-link?
- Install it with Composer, publish the package config, and supply your Stripe secret key through your environment or a secrets manager. Then drop the field into an existing Filament resource form. The evaluation notes this is low effort, with no migrations, queue workers, or webhooks implied by the release notes. Pin to ^1.1.0 explicitly rather than using a floating constraint.
- Which Laravel and Filament versions does this plugin support?
- The package requires Laravel with Filament installed, and it is described as a natural drop-in if your admin panel already runs Filament v3. The published material does not state a full compatibility matrix, so whether Filament v4 is supported is an open question to confirm with the maintainer. Verify the major version in a throwaway branch before merging.
- Do I need a Stripe account with Payment Links enabled?
- Yes. You need a Stripe account with Payment Links enabled, plus a secret key made available to the Laravel app. Run it against Stripe test mode keys in staging first, generate a link end to end, and complete a test payment. Compare the generated link's price and amount against your source-of-truth product data.
- Does this package store payment links or act as a system of record?
- It should not be treated as the system of record for pricing, entitlements, or reconciliation. Keep those in your own tables keyed by Stripe price and product IDs. The overview describes a thin integration layer that surfaces link creation inside a Filament form, not a payments subsystem. Whether the plugin caches or persists generated links is not documented and is worth asking the maintainer.
- What changed in v1.1.0 of this plugin?
- The release's only functional change is described as updating the Stripe API to the latest version. That matters because Stripe versions its API by dated snapshot, and a bump can silently change response shapes, expandable-field defaults, and error codes. The changelog gives no migration notes, so confirm which API version string is pinned and whether it is configurable.
- How do I avoid stripe/stripe-php version conflicts with this plugin?
- The v1.1.0 API bump may pull in a transitive stripe/stripe-php constraint that clashes with other Stripe-touching packages in your monorepo. Run composer why stripe/stripe-php across the dependency graph and resolve conflicts before starting the feature branch. Also confirm the Filament major version you are running before merging.
- Is the plugin well maintained, and is there a test suite?
- The governance signals are limited: two contributors in the release, one of them Dependabot, and both making first contributions. Of three merged pull requests, two are Dependabot CI bumps, which shows CI is kept healthy but says nothing about test coverage of the Stripe upgrade. Ask the maintainer whether a test suite exercises the Stripe call path and what the policy is for following Stripe's deprecation calendar.
- What should I use instead if I am not on Filament?
- If your admin is custom, Livewire-only, or Nova, this package offers nothing useful. Call the Stripe SDK directly instead, because the abstraction here is too thin to justify an adapter. The plugin is a presentation-layer convenience for Filament panels, not a portable payments layer.
- How should I roll this plugin out safely in production?
- Confirm Filament and Stripe SDK compatibility in a throwaway branch, then deploy to staging with Stripe test keys and complete an end-to-end test payment. Feature-flag the action to one internal admin user for a week before rolling out broadly. Because v1.1.0 changes the Stripe API version, that staging verification is non-negotiable. Document the manual Stripe dashboard fallback in your runbook and keep the Stripe secret in your existing secrets manager rather than a committed .env file.