Weave Code
Smoney Bundle Laravel Package
spyrit/smoney-bundle
spyrit/smoney-bundle is a Symfony bundle for integrating SMoney payment services into PHP applications. It wraps the SMoney API with Symfony configuration and services, helping developers add payment workflows with less boilerplate. Best suited to projects already built on Symfony.
At a glance
Frequently asked questions about Smoney Bundle
- Can I use spyrit/smoney-bundle in a Laravel application?
- Not directly in the usual Laravel way. spyrit/smoney-bundle is a Symfony bundle, and Laravel does not boot Symfony bundles or use the Symfony full-stack DI, config, and event system. You can inspect it as a reference for SMoney API logic, but you should not expect drop-in behavior in Laravel. The practical path is to extract or reimplement the SMoney client behind a Laravel service provider.
- Does spyrit/smoney-bundle support Laravel 10 or Laravel 11?
- There is no Laravel version support because the package targets Symfony, not Laravel. Its Composer constraints are likely tied to Symfony components and older PHP versions, which may conflict with modern Laravel releases. Check composer.json before attempting installation, and expect dependency resolution friction. Even if Composer resolves, the bundle’s services and configuration will not be wired into Laravel automatically.
- How do I install spyrit/smoney-bundle with Composer in Laravel?
- A composer require may technically succeed, but it will not register Symfony bundle services in Laravel. Laravel will not read the bundle’s Symfony configuration tree or boot its kernel-dependent services. Installing it directly is therefore not recommended for a Laravel runtime. If you only need reference code, inspect or fork the repository rather than adding it as a production dependency.
- What does spyrit/smoney-bundle actually provide?
- It is a Symfony bundle that wraps SMoney payment API calls with Symfony configuration and services. Its value is reducing boilerplate for Symfony applications that already use the Symfony framework. It is not a Laravel pacakge and does not provide Laravel service providers, facades, config publishing, or Laravel-native HTTP integration. Treat it as a reference implementation or a source of SMoney client logic.
- Is spyrit/smoney-bundle maintained and safe for production payments?
- The available assessment shows 0 stars, 0 dependents, and a score of 0.03, so there is little community validation. Maintenance status, test coverage, security posture, and SMoney API longevity are uncertain. Payment credentials and PII also raise compliance and PCI-scope concerns. Do a full source, license, and security audit before using it in production, and prefer an isolated gateway with fallback behavior.
- What are the alternatives to spyrit/smoney-bundle for Laravel SMoney integration?
- Look first for an official or actively maintained SMoney PHP SDK that is framework-agnostic. If none exists, implement a thin SMoney API client using Laravel’s HTTP client and wrap it in a service provider. Keep the integration behind an internal SmoneyGateway interface so it can be swapped later. The Symfony bundle can serve as behavioral reference, not as the runtime dependency.
- How do I configure SMoney credentials in Laravel without the Symfony bundle config?
- Use Laravel configuration files and environment variables instead of the bundle’s Symfony config tree. Bind an SMoney client or gateway in a service provider, inject it where needed, and avoid exposing credentials in logs or exceptions. Add config caching and secret management appropriate to your deployment. This keeps payment credentials within Laravel’s config and environment conventions.
- Can I extract the SMoney client from spyrit/smoney-bundle and use it in Laravel?
- Possibly, but only after a source audit. Identify the SMoney client classes, request and response DTOs, authentication flows, and any Symfony-specific dependencies. If the API-call layer is cleanly separable, vendor or fork the minimal classes and wrap them in a Laravel service provider. If it is tightly coupled to Symfony components, reimplement the calls with Laravel’s HTTP client instead.
- What are the risks of using a Symfony bundle in a Laravel codebase?
- Laravel uses Symfony components but not the full Symfony framework, so bundle bootstrapping, DI extensions, config trees, and event listeners are likely incompatible. You may get dependency conflicts, unused services, and unclear failure modes. For payments, that increases operational and compliance risk. Avoid introducing a Symfony kernel solely for this package; isolate or rewrite the integration instead.
- How should I test SMoney payment flows in Laravel?
- Confirm sandbox credentials and contract-test the core flows: authorization, capture, refund, webhook handling, and failure cases. Use Laravel’s HTTP client fakes and feature tests around your own gateway interface, not around the Symfony bundle. Test idempotency, retries, logging redaction, and PII handling. Run an isolated proof of concept behind a feature flag before production rollout.
Weaver
How can I help you explore Laravel packages today?