Weave Code
Sermepa Omnipay Laravel Package
nazka/sermepa-omnipay
Omnipay gateway for Sermepa (Redsys), the Spanish payment processor used by banks like BBVA and Santander. Adds Sermepa payment support to any Omnipay-based PHP application, handling signed requests, redirects and responses.
sermepa (redsys) omnipay gateway
Frequently asked questions about Sermepa Omnipay
- What is nazka/sermepa-omnipay used for?
- It is an Omnipay gateway driver for Sermepa/Redsys, the Spanish card processor used by banks such as BBVA and Santander. It adds Sermepa payment support to Omnipay-based PHP applications, handling signed requests, redirects and responses. In Laravel, it is not native and must be wrapped in a service provider and application payment service.
- Does nazka/sermepa-omnipay work with Laravel 10 or Laravel 11?
- The provided evaluation does not confirm an official Laravel 10 or 11 support matrix. It is not Laravel-native, and the package is aged with low adoption, so dependency constraints may conflict with modern Laravel and PHP versions. Validate PHP 8.x, Laravel 10/11, Omnipay v3, Guzzle and Symfony constraints early, and expect dependency upgrades or typed-code fixes.
- How do I install and configure nazka/sermepa-omnipay in Laravel?
- Install it with Composer, then bind a configured gateway as a Laravel singleton rather than calling it directly from controllers. Store the merchant code, terminal, secret and environment in config/services.php, and wrap purchase, complete and refund flows in an application-level payment service. A staging spike against the Redsys sandbox and merchant-account setup should come before production use.
- Which Omnipay version does nazka/sermepa-omnipay target?
- The provided context flags this as a key question rather than confirming a specific major version. It recommends validating Omnipay v3 compatibility early, along with Guzzle and Symfony constraints. If the target Laravel/PHP stack is incompatible, plan to fork the package and upgrade its dependencies or implement a minimal Redsys gateway on top of omnipay/common.
- Does nazka/sermepa-omnipay support Redsys SHA256 signatures and 3DS2/SCA?
- The context does not confirm SHA256 or 3DS2/SCA support and explicitly lists stale Redsys signature support and 3DS/SCA as risks to verify. Payment-critical signature, redirect, callback and refund behavior should be proven in the Redsys sandbox before relying on it. Assume custom work may be needed for current Redsys requirements.
- Can I use nazka/sermepa-omnipay for refunds, recurring payments or stored cards?
- The evaluation says it is a poor fit for marketplace splits, subscriptions, stored cards or advanced reconciliation without custom work. Refund flows are part of the payment-critical surface and should be proven in sandbox testing rather than assumed. Recurring payments and stored cards should not be treated as supported without confirming the driver and Redsys merchant contract.
- Is nazka/sermepa-omnipay production-ready and actively maintained?
- The assessment rates technical risk as high: the package is aged, has low adoption, 21 stars and 0 dependents, with missing automated tests and unclear security maintenance mentioned as risks. It has no meaningful vendor SLA and is community-only. Treat it as a reference implementation or fork candidate, not a default production dependency.
- How should I test Sermepa/Redsys payments with this package?
- Start with a staging spike against the Redsys sandbox using the required merchant contract, terminal and environment. Prove purchase, callback, refund and IPN signature verification flows, then add idempotency, webhook deduplication, reconciliation and observability. If you fork the package, add automated tests and clear ownership before piloting low-value transactions.
- What are alternatives to nazka/sermepa-omnipay for Redsys in Laravel?
- The context suggests forking and upgrading this package, or implementing a minimal Redsys gateway on top of omnipay/common if compatibility fails. It does not name another specific Redsys package. Keep existing checkout behind a feature flag, dual-run with manual reconciliation and roll out gradually with rollback runbooks.
- How do I handle Redsys IPN webhooks and signature verification with this package?
- Do not assume complete IPN signature verification; the evaluation lists webhooks/IPN and signature verification as payment-critical risks and key questions. Persist transaction logs, use queues, idempotency keys, retries, deduplication and rate-limit handling for callbacks. Verify signatures, handle amount, currency and order mismatches, and provide replay and investigation tooling for failed or duplicate IPNs.
Weaver
How can I help you explore Laravel packages today?