Weave Code
Payment Laravel Package
spatie/payment
UNMAINTAINED. Laravel package to accept payments via payment gateways, with a Europabank e-commerce integration. Provides a payment form and configurable secrets/UID/MPI settings via a published config file.
A Laravel package to accept and verify payments from payment gateways
Frequently asked questions about Payment
- Is this package still actively maintained or safe to use in production?
- No, this package is **not maintained** and archived by Spatie. Use it only if you’re already using Laravel 5.x and Europabank, but be aware of security risks from outdated dependencies (e.g., Guzzle v5, Carbon v1). For new projects, consider modern alternatives like `omnipay/europabank` or `laravel-cashier`.
- Does this package support Laravel 6+ or modern Laravel versions?
- No, it’s designed for Laravel 5.x and will require significant manual refactoring to work with Laravel 6+. Expect to rewrite service providers, update facades, and replace deprecated Carbon/Guzzle versions. Test thoroughly before migration.
- Can I use this package with other payment gateways besides Europabank?
- No, this package is **hardcoded for Europabank** and lacks abstraction for other gateways. Extending it for new providers would require forking and rewriting core logic, which isn’t recommended due to its deprecated state.
- How do I configure the payment form and Europabank credentials?
- Publish the config file with `php artisan config:publish spatie/payment`, then set `clientSecret`, `serverSecret`, `uid`, and `mpiUrl` in `config/packages/spatie/payment.php`. Use environment variables (e.g., `.env`) for sensitive data like `EUROPABANK_CLIENT_SECRET`.
- Does this package handle PCI-DSS compliance or secure card data processing?
- This package provides **no built-in PCI-DSS compliance** or tokenization. You must implement your own security measures (e.g., encryption, tokenization) to handle card data safely. Europabank’s API may have changed since 2016, so verify their current compliance requirements.
- Can I integrate webhooks or asynchronous payment confirmations?
- No, this package lacks **webhook support** for asynchronous payment processing. Modern payment flows require webhooks to handle callbacks from gateways (e.g., payment success/failure). You’d need to build this manually or switch to a package like `spatie/webhook-client` for Laravel.
- What are the risks of using unmaintained dependencies like Guzzle v5?
- Unmaintained dependencies (e.g., Guzzle v5, Carbon v1) pose **security and compatibility risks**, including vulnerabilities and breaking changes. Upgrade these manually or isolate the package in a micro-service to mitigate risks, but expect maintenance overhead.
- How do I test payment flows with this package?
- There’s **no built-in test suite**, so you’ll need to mock Europabank’s API responses manually. Use Laravel’s HTTP testing or a library like `Vcr` to record/replay API calls. Test edge cases like failed payments, timeouts, and form submissions thoroughly.
- What’s the best alternative if I need Europabank support in Laravel?
- For modern Laravel apps, consider **`omnipay/europabank`** (if available) or **`laravel-cashier`** for broader gateway support. These packages follow current Laravel patterns (e.g., dependency injection, queues) and are actively maintained. Check GitHub for updated Europabank drivers.
- Does this package work with PHP 8.x or modern PHP features?
- No, this package likely **doesn’t support PHP 8.x** features like named arguments or attributes. You’ll need to manually update the codebase or use a compatibility layer (e.g., `php-compatibility`). Test thoroughly after any PHP version upgrades.
Weaver
How can I help you explore Laravel packages today?