- What is dercoder/omnipay-paysafecard used for?
- It is a Paysafecard driver for the Omnipay PHP payment processing library, letting you create and handle Paysafecard transactions through Omnipay's consistent gateway API. Instead of writing Paysafecard-specific HTTP and request handling yourself, you call standard Omnipay methods such as purchase and completePurchase. It is framework-agnostic, so it can be used in Laravel, Symfony, or plain PHP applications.
- How do I install dercoder/omnipay-paysafecard with Composer?
- Install it with Composer by requiring the package, for example composer require dercoder/omnipay-paysafecard. Composer will also pull in the Omnipay core packages it depends on. After installation, instantiate the gateway class shipped by the package and pass your Paysafecard credentials as gateway parameters. Check the package README for the exact gateway class namespace and required parameters.
- Does this package work with Laravel?
- Yes. Because Omnipay is framework-agnostic, the driver can be used inside a Laravel application just like any other Composer package. Typical usage is resolving or instantiating the gateway in a controller or a small service class, then calling the Omnipay methods from your payment routes. There is no Laravel-specific service provider required, so you wire configuration through your own config files or environment variables.
- Which Omnipay version does this driver require?
- The exact Omnipay major version constraint is defined in the package's composer.json, so check that file or the README before installing. Omnipay 3.x introduced namespaced gateway classes and PSR-4 autoloading, which differs from the older 2.x API. If your application already uses Omnipay, make sure the driver's constraint matches the version you have installed to avoid dependency conflicts.
- How do I create a Paysafecard payment with this gateway?
- You typically build a purchase or authorize request through the gateway, passing the amount, currency, and any required customer or return URLs. Omnipay then returns a response object that either contains a redirect URL or indicates an error. Always check the response with isRedirect or isSuccessful before sending the user anywhere, and log the transaction reference for reconciliation.
- Is Paysafecard a redirect-based gateway and how do I handle the return?
- Paysafecard flows generally involve sending the customer to a Paysafecard-hosted page to complete the payment, so expect a redirect response from the purchase call. After the customer returns to your application, you call completePurchase with the incoming request data to confirm the final status. Treat the result as authoritative only after verifying it server-side, never on the basis of the return URL alone.
- Does this driver support a sandbox or test mode?
- Omnipay gateways usually expose a testMode parameter, and this driver follows that convention where the underlying Paysafecard API supports it. Enable testMode in your gateway parameters and use test credentials or endpoints so you do not create live transactions. Confirm the specifics in the package README, since sandbox availability depends on what Paysafecard exposes for your account type.
- How should I test Paysafecard payments in my Laravel application?
- Unit-test your integration by mocking the Omnipay gateway and asserting that your code builds the correct purchase parameters and handles each response type, including failures and redirects. For end-to-end checks, use testMode with sandbox credentials and a staging callback URL. Keep the gateway behind a small interface or service class so it is easy to swap for a fake in tests.
- Does using Paysafecard through Omnipay raise PCI compliance concerns?
- Paysafecard is a prepaid voucher-based method, so customers enter a PIN on Paysafecard's own pages rather than card details in your application. That means your code generally does not store or transmit cardholder data for these payments, which reduces your PCI scope. You should still protect credentials, use HTTPS, and never log sensitive request payloads.
- Is this package actively maintained, and what are the alternatives?
- Maintenance status is not documented in the information available here, so check the Packagist page for release history and the repository for recent commits before committing to it. Alternatives include other Omnipay Paysafecard drivers and official or vendor-supported SDKs, which may offer better long-term support. Because the Omnipay API is standardized, migrating between drivers is usually a small change confined to gateway construction and parameter names.