- What is flux-se/payum-stripe used for?
- It is a Payum gateway package for Stripe that lets PHP applications accept card payments, check payment status, and process refunds through Stripe’s API. It provides a consistent Payum interface for Stripe so teams can integrate payments into existing Payum or Symfony workflows with less boilerplate. It is a payment abstraction component, not a Laravel-native Stripe solution.
- Is flux-se/payum-stripe a Laravel package or a Payum/Symfony package?
- It is a Payum gateway package for Stripe, so it fits best where an application already uses Payum or Symfony payment abstractions, such as Sylius-based commerce. Laravel can consume it, but integration requires custom glue to wire Payum into Laravel’s service container and payment flows. Treat it as a Payum component rather than a drop-in Laravel package.
- How do I install flux-se/payum-stripe?
- Installation is typically done with Composer using composer require flux-se/payum-stripe. After installation, you configure a Payum Stripe gateway factory and provide your Stripe API credentials. In Laravel, expect to add container bindings, configuration, and route handling yourself rather than relying on an auto-discovered Laravel service provider.
- Does flux-se/payum-stripe support SCA and 3D Secure?
- The package description states that it includes SCA support, which is important for Strong Customer Authentication and 3D Secure flows in many regions. You should still verify end-to-end SCA behavior in a Stripe sandbox, including authentication challenges, failures, and recovery paths. Confirm that your required PaymentIntent or charge flow matches the package’s supported actions.
- How do I use flux-se/payum-stripe in a Laravel application?
- You can use it in Laravel, but the fit is moderate to weak because it introduces Payum’s gateway, action, and request model alongside Laravel’s container. The safer approach is to isolate Payum behind an internal PaymentGateway interface and run a sandbox proof of concept covering authorize, capture, decline, refund, and webhook reconciliation. If Payum abstraction is not an explicit requirement, Laravel Cashier or the official Stripe SDK may be lower-risk.
- Which Stripe payment flows does flux-se/payum-stripe support?
- The package is intended for Stripe card payments, payment status checks, and refunds through Payum, but the exact supported feature set should be verified against your requirements. Check whether you need PaymentIntents or Charges, full or partial refunds, subscriptions, multi-currency, idempotency, and partial captures. Do not assume advanced Stripe features without testing them in a sandbox.
- Does flux-se/payum-stripe handle Stripe webhooks securely?
- Integrating the package in production requires exposing Stripe webhook endpoints and verifying Stripe signatures, so webhook handling is part of your integration work. Review how the package or your application handles idempotency, replay protection, and duplicate events before relying on it for payment state changes. Add monitoring and dead-letter handling for failed webhook processing.
- Which PHP, Laravel, Payum, and Symfony versions are compatible with flux-se/payum-stripe?
- Compatibility depends on the package’s composer.json constraints and its Payum and Symfony dependencies, so check those before committing. Laravel is not a first-class target, meaning container compatibility and service wiring may need custom work. Run a small integration spike against your exact PHP, Laravel, Payum, Symfony, and Stripe API versions.
- Is flux-se/payum-stripe safe and maintained for production?
- Adoption signals are weak, with around 29 GitHub stars, zero dependents, and no obvious commercial support, which creates maintenance and bus-factor risk. The MIT license is favorable, but low usage means fewer battle-tested edge cases and limited public troubleshooting. For production, pin versions, monitor upstream changes, and keep a fork-ready posture with internal contract tests.
- What are the alternatives to flux-se/payum-stripe for Laravel?
- For Laravel-first applications, Laravel Cashier and the official Stripe PHP SDK are usually lower-risk alternatives because they provide more direct Stripe integration and stronger community usage. If your stack already uses Sylius or Payum, evaluating this package as a Stripe gateway adapter can still make sense. Choose based on whether Payum abstraction is a real architectural requirement or avoidable complexity.