Weave Code
Paymill Bundle Laravel Package
memeoirs/paymill-bundle
A Symfony bundle for integrating the Paymill payment provider, offering configuration and services to handle payments, transactions, and webhooks with minimal setup.
memeoirs/paymill-bundle provides a convenient Symfony integration for the Paymill payment API, helping you add card payments and transaction handling to your application with less boilerplate. It wires Paymill services into Symfony’s dependency injection container and offers a clean starting point for payment workflows.
- Symfony bundle configuration for Paymill API credentials
- Service container integration for payment clients
- Helpers for transactions and payment processing
- Extensible structure for custom checkout flows
- Composer-ready installation
Frequently asked questions about Paymill Bundle
- Is memeoirs/paymill-bundle a Laravel package?
- No. It is a Symfony bundle extracted from the Memeoirs application, registering services through a Symfony DI extension and depending on Symfony's config and container components. There is no Laravel service provider, facade, or config publishing, so it cannot be installed and used in a Laravel app as-is. Treat it as reference code at best.
- Can I install memeoirs/paymill-bundle with Composer in a Laravel project?
- You can run composer require, but the bundle's autoloading and Symfony 2.x-era dependency constraints will likely conflict with a modern Laravel install. Even if it installs, Laravel will not boot the bundle or register its services. The practical path is to use it as a reference and reimplement the binding in a Laravel service provider.
- Which Laravel and PHP versions does this package support?
- None officially. The bundle was last released in June 2016 and targets Symfony 2.x-era APIs and older PHP versions, not Laravel at all. Modern Laravel 10 or 11 on PHP 8.1+ is unsupported, and you should expect constructor signature and container API incompatibilities.
- How do I integrate Paymill payments into Laravel using this bundle?
- You do not depend on the bundle; you read it as a wiring reference for the paymill/paymill-php SDK. Define a PaymentGateway interface in your domain, bind it in a Laravel service provider, and back it with either the SDK or a small Guzzle client against Paymill REST v2. Keep Paymill types behind an anti-corruption layer so a future PSP swap is an adapter change.
- Does this package support SCA and 3DS2 for EU card payments?
- No. Paymill's platform predates PSD2 and SCA enforcement, and this thin wrapper does not add 3DS2 flows. For EU customers this is a compliance blocker rather than a patchable bug. Confirm your provider's SCA position before writing any code.
- Is memeoirs/paymill-bundle still maintained?
- No. It has a single maintainer, around 12 stars, zero dependents, no release since June 2016, and no visible security policy or test suite. Any CVE in its transitive dependencies, such as Guzzle, the Paymill SDK, or Symfony components, becomes yours to patch. Budget for owning that supply chain or avoid the dependency.
- How do I configure Paymill API keys with this bundle?
- In Symfony you would set the public and private keys in the bundle's config tree under your application configuration. There is no Laravel config file, env publishing, or config cache integration, so in Laravel you would map the same credentials into config/services.php and your own service provider. Never commit private keys; keep them in environment variables.
- Are there tests or a test suite for this bundle?
- There is no visible test suite in the repository. Because it is a thin wrapper over the Paymill SDK, unit tests would mostly assert your own wiring and error handling. Plan to write your own contract tests against Paymill's sandbox and to mock the gateway in application tests.
- What are alternatives to this bundle for Laravel payments?
- Use a maintained PSP with first-class Laravel support such as Stripe with Cashier, Mollie, Adyen, or Braintree, or Paymill's SDK directly if you must stay on Paymill. The bundle adds little over the SDK and is not Laravel-native. Choosing a maintained provider also solves the SCA, 3DS2, and security patching problems.
- What risks should I check before adopting this package in production?
- Confirm you can still onboard a live Paymill merchant account, the settlement and contractual terms, and whether your target markets require SCA or 3DS2. Review the unmaintained dependency tree for CVEs and decide who owns patching. Also plan for duplicate charges, webhook loss, subscription dunning, and refund or chargeback reconciliation, none of which this wrapper handles.
Weaver
How can I help you explore Laravel packages today?