- How do I install egopay/sci in a Laravel application?
- Install it with Composer using composer require egopay/sci, then publish the package config and set your merchant credentials through environment variables. Because the package shows no maintainer activity and likely contains PHP 5-era code, run a short spike first to confirm it resolves and installs on your PHP and Laravel baseline. If Composer resolution fails, you may need to pin or vendor the source instead.
- Does egopay/sci support Laravel 10, Laravel 11, or PHP 8?
- There is no compatibility guarantee. Repository evidence suggests PHP 5-era code with limited Laravel awareness and no trusted test suite, while zero stars, zero dependents, and no visible maintenance mean current PHP 8 and Laravel releases are unverified. Treat any claimed auto-discovery or facade support as unverified and prove it in a spike before planning around it.
- How do I configure EgoPay merchant credentials with egopay/sci?
- The package is config-driven, so publish its config file and supply merchant credentials via environment variables rather than hardcoding them. Keep secrets in .env and, where possible, resolve them through config/services.php in a single application-owned service provider. Also identify and rotate or destroy any legacy EgoPay credentials or secrets you still hold.
- How do I create an EgoPay SCI payment form or redirect in Laravel?
- The package provides a fluent payment form and redirect builder for initiating checkout without hand-rolling form posts and signatures. Persist your own order with a local merchant reference and a UUID before redirecting so callbacks can be reconciled later. Keep EgoPay-specific payload handling out of controllers, models, jobs, and Blade templates other than the redirect view.
- How does egopay/sci verify callbacks and signatures?
- It offers callback verification with hash and signature validation before fulfillment, which is the right shape for a payment integration. However, the exact signing and hashing scheme is not documented as independently reviewed, and the package has no security disclosure process. Validate the scheme against payloads you actually received historically, and add your own idempotency and error semantics around fulfillment.
- Is egopay/sci safe to use in production for payments?
- Technical risk is high and dominated by counterparty risk. EgoPay ceased operations around 2015 to 2016 with merchant balances unrecoverable, so there is no live endpoint, sandbox, settlement, or merchant support behind the library. Use it only as a contained, frozen wrapper for legacy traffic, never for new money, and treat any plan that routes new payments through it as a compliance exposure.
- How can I test an EgoPay SCI integration without a sandbox?
- There is no EgoPay sandbox or merchant support, so test against captured historical payloads and fixtures rather than a live gateway. Wrap the package behind an application-owned PaymentGateway adapter and write contract tests for initiate, verifyCallback, pollStatus, and refund. Mock the transport layer and assert idempotency and duplicate-charge behavior explicitly.
- What are good alternatives to egopay/sci for Laravel payments?
- Choose a supported payment service provider with an active security response and contract-test it against your own PaymentGateway interface. Maintained gateway SDKs and aggregator libraries exist for Laravel, but the right pick depends on your acquiring contract and region. The replacement should be a one-line swap behind your adapter, not a rewrite of your checkout flow.
- How do I keep egopay/sci from leaking into my domain layer?
- Put it behind an application-owned adapter such as EgoPayGateway implementing your PaymentGateway contract, bound in a single service provider so the vendor namespace appears in exactly one place. Store money as integer minor units or DECIMAL(12,2) and use a pending to paid, refunded, or failed state machine with an order_events audit table. That containment makes replacement a one-line swap and lets you freeze all feature work on the EgoPay path.
- Is egopay/sci still maintained and does it have a security response process?
- No visible maintenance exists: zero stars, zero dependents, and no maintainer activity or CVE response path. There is no trusted test suite and no Composer compatibility guarantee for current PHP and Laravel, and no PCI-DSS evidence. Classify it as a reference implementation and migration artifact, not a runtime dependency for new work.