Weave Code
Payment Bundle Laravel Package
idci/payment-bundle
IDCI PaymentBundle is a Symfony bundle for adding flexible payment handling to PHP applications, with abstractions for payment methods, gateway integrations, and configurable workflows to process and track transactions.
Symfony payment bundle
Frequently asked questions about Payment Bundle
- Is idci/payment-bundle a Laravel package?
- No. idci/payment-bundle is a Symfony bundle, not a Laravel package. It depends on Symfony components such as DependencyInjection, Config, EventDispatcher, and HttpFoundation, and the assessment explicitly warns that labeling it as a Laravel/PHP package is a scoping error. There is no maintained Laravel bridge and no community port to rely on.
- Can I install idci/payment-bundle in a Laravel app with Composer?
- A direct Composer require into a Laravel app is not feasible without a compatibility shim or a full port. Symfony bundle bootstrapping does not map onto Laravel's service-provider and HTTP kernel abstractions, and the cost of bridging is unbounded relative to the package's maturity. Do not plan a Laravel integration around adaptation.
- Which Symfony and PHP versions does idci/payment-bundle support?
- The available assessment does not establish exact Symfony or PHP version ranges; inspect the package's composer.json constraints and tag history before assuming support. The reported last release date of 2026-09-09 is future-dated, so verify actual tags, commit recency, and CI status. No deprecation policy is visible in the provided signals.
- How do I configure payment gateways in idci/payment-bundle?
- The bundle uses Symfony bundle configuration plus service, event, and form integrations to define gateways and payment workflows. You configure gateways through Symfony configuration and custom provider services, then hook into payment lifecycle events. There is no equivalent Laravel configuration path because the bundle is not built for Laravel.
- Does idci/payment-bundle have tests, CI, or a security disclosure process?
- There is no visible evidence of a test suite, security policy, or CVE response process proportionate to a payment library's risk. The assessment flags this as high domain risk and recommends verifying CI status and meaningful coverage before any commitment. Weak adoption signals mean few external users are exercising edge cases.
- Is idci/payment-bundle safe for production payment processing?
- Treat it as high risk for production payment processing unless a deep audit proves otherwise. Payment code carries PCI scope, idempotency, webhook replay, and reconciliation concerns, and the package has weak adoption plus single-vendor bus factor. The assessment recommends reference-only use or an isolated Symfony service rather than direct adoption in a Laravel app.
- How actively maintained is idci/payment-bundle?
- Adoption signals are weak: 1 star, 0 dependents, a composite score around 18/100, and an opportunity score around 20/100. These metrics suggest a vendor-internal utility rather than a library with an active user base. Check commit cadence over the last 18 months, CI, and the accountable maintainer before relying on it.
- What are alternatives to idci/payment-bundle for Laravel payment handling?
- There is no maintained Laravel bridge, so alternatives are Laravel-native billing or payment packages, direct PSP SDKs, or an internal payment service behind your own PaymentGateway interface. You may read the MIT-licensed source for domain modeling patterns such as payment state machines and gateway abstraction and build internally. Do not require the bundle into a Laravel app as your production payment layer.
- Can idci/payment-bundle handle credit card, callback, and offline payments?
- The bundle is designed for pluggable gateways, including credit cards, callbacks, and offline payments, through a shared payment API. However, the provided assessment does not establish PSP coverage, webhook verification, idempotency keys, or refund and partial-capture handling. Audit these gaps before assuming the bundle covers your payment use case.
- How should I integrate idci/payment-bundle if I already run Symfony services?
- In a Symfony estate, wrap the bundle behind an internal PaymentGateway interface and keep its types out of your domain layer so the dependency is swappable in one file. If the capability is shared with a Laravel app, the correct seam is an internal payment service exposed over an API, not a shared library. Forking and porting is the highest-cost option and makes you the long-term owner of a thinly maintained codebase.
Weaver
How can I help you explore Laravel packages today?