Weave Code
Saferpay Bundle Laravel Package
payment/saferpay-bundle
A Symfony bundle for integrating the Saferpay payment gateway into PHP applications. It streamlines configuration and payment processing, helping you accept secure online card payments with less boilerplate.
At a glance
Frequently asked questions about Saferpay Bundle
- Is payment/saferpay-bundle compatible with Laravel?
- No. It is a Symfony bundle from the payment-legacy namespace, built on older Payment/JMS payment abstractions, with no Laravel service provider, facade, or publishable config. Laravel can autoload the code, but bootstrapping Symfony's DI container alongside Laravel's is not worth the complexity and is likely to break under Octane. Treat it as a protocol reference, not a Laravel dependency.
- How do I install payment/saferpay-bundle with Composer?
- You can run composer require payment/saferpay-bundle, but the package is designed for Symfony bundle registration and configuration, not Laravel. Expect old framework constraints and transitive dependencies that may be abandoned, so audit before installing even for inspection. For a Laravel app, the realistic path is extracting request builders and response models rather than installing it as a runtime dependency.
- Does this bundle support 3DS2, SCA, or PSD2?
- Almost certainly not. A package of this vintage likely predates SCA/3DS2 and PSD2 obligations, and if it only implements the legacy Saferpay HTML/Interface flow it cannot complete a modern challenge. That failure shows up in production, not in a sandbox test. Confirm API generation and authentication result states during your spike, and plan to add SCA handling yourself.
- Which Saferpay API generation does it target, and are the endpoints still live?
- The overview says it wraps Saferpay's Payment Page and Transaction APIs, but it does not state the API generation. Legacy bundles of this age often hard-code old URLs with no version negotiation, which can cause a total payment outage when the provider sunsets an endpoint. Verify the exact API version and whether those endpoints are live in production today before funding integration work.
- Does it support authorize, capture, cancel, refund, partial refund, and tokenization?
- The overview lists Payment Page initialization plus authorize, capture, and cancel helpers. It does not claim refund, partial refund, or tokenization, so assume those operations are missing until proven otherwise. Model the full operation set in your own PaymentGateway contract and implement gaps in a thin Saferpay client.
- Are Saferpay callbacks verified, and is payment processing idempotent?
- Treat callback verification as work you must add, not work you inherit. Packages from this era commonly have unverified callbacks and non-constant-time comparisons, and idempotency is usually left to the application. In Laravel, verify signatures or gateway responses explicitly, store idempotency keys, and make capture and refund handlers replay-safe.
- Is payment/saferpay-bundle maintained and safe for production payments?
- No. The repository is archived, has about 3 stars and 0 dependents, and lives under a payment-legacy namespace, so there is no upstream CVE response or escalation path. Any defect becomes permanently yours. Its value is as a risk-register entry and a protocol reference, not as an adoptable production dependency.
- Does it run on PHP 8.2/8.3, and are its Symfony dependencies abandoned?
- That must be tested, not assumed. A bundle of this age may have old Symfony and PHP constraints, and its transitive dependencies may themselves be abandoned. If you only need the protocol shapes, extract them into modern DTOs and avoid carrying the legacy dependency tree into a Laravel app.
- Does the bundle have tests, and can I test it against the Saferpay sandbox?
- Do not assume a usable test suite. Make standing it up against the Saferpay sandbox a spike deliverable so you can produce a request/response catalogue for amounts, currencies, transaction IDs, and status enums. If the bundle cannot run cleanly, extract the shapes from code and test your own thin client against the sandbox instead.
- What is the license, and is there a maintained Laravel Saferpay alternative?
- Check the repository license before copying any code, because code reuse is only permitted if the license clearly allows it. There is no credible maintained Laravel-native Saferpay integration to adopt; the better output of the spike is an in-house client behind an application-owned PaymentGateway contract. Use the bundle to shorten discovery, then own the implementation.
Weaver
How can I help you explore Laravel packages today?