- What is jeka/qiwi-api used for?
- It is a lightweight PHP/Laravel client for the QIWI Wallet API. It is intended to wrap authentication and HTTP calls so you can create and manage invoices, check balances, query payment history, and handle notifications without writing raw Guzzle requests. The technical assessment describes it as a convenience wrapper rather than a full payment platform.
- How do I install jeka/qiwi-api?
- Install it with Composer using composer require jeka/qiwi-api. Then configure your QIWI credentials according to the package config or README, and wire the client into your Laravel service container if no auto-discovery is present. Verify the declared Laravel and PHP constraints before adding it to an existing app.
- Does jeka/qiwi-api support Laravel 10, 11, and PHP 8?
- The package is described as Laravel-friendly, but the technical assessment flags that composer.json version constraints may not cover current Laravel and PHP releases. Check the illuminate/support ranges and PHP 8.x parity before committing engineering time. If constraints are stale, you may need to fork or use it only as a reference implementation.
- Does jeka/qiwi-api include a Laravel service provider and facade?
- The package overview claims Laravel integration, but the technical assessment says there is no service provider, facade, or publishable config and that it is a plain PHP SDK you wire up yourself. Treat the Laravel integration as something to verify in the repository rather than assuming drop-in behavior. Budget time for manual container binding and configuration.
- How do I configure QIWI credentials for jeka/qiwi-api?
- You need QIWI merchant or wallet credentials such as a token or site_id/secret, depending on the API endpoints the package targets. Put secrets in environment variables and avoid logging them, because the assessment notes token handling and secret redaction need review. Confirm with QIWI which authentication mode and IP whitelisting your account requires.
- Can jeka/qiwi-api create, inspect, and cancel QIWI invoices?
- Yes, invoice creation keyed by a caller-supplied bill_id, status lookup, and cancellation are within the scope described for the package. It maps to a narrow slice of checkout: invoice lifecycle plus balance and account reads. Refunds and payouts are not clearly covered and should be treated as gaps.
- Does jeka/qiwi-api handle QIWI payment notifications or webhooks?
- The overview says it can handle payment notifications, but the technical assessment warns that webhooks are not reliably pushed for all QIWI account types and that webhook verification may be on you. Plan for poll-based status reconciliation and implement signature or source verification yourself. Do not assume webhook-driven state without checking your QIWI merchant tier.
- Is jeka/qiwi-api production ready and maintained?
- The assessment rates community validation as high risk: about 16 stars, zero dependents, a single maintainer, and a score of 0.14. Treat it as effectively unmaintained and assume you own the code after adoption. For production, fork it, pin versions, add tests, and assign an internal owner.
- Does jeka/qiwi-api support refunds, payouts, idempotency, retries, and timeouts?
- The package appears to cover invoice creation, status, balance, and history, but refunds/payouts, idempotency, retry policy, and timeout handling are likely on your side. The assessment explicitly flags these as scope gaps to plan for. Wrap calls in your own adapter with idempotency keys, timeouts, and structured logging.
- What are alternatives to jeka/qiwi-api for Laravel QIWI integration?
- If you need a maintained or multi-provider abstraction, use Laravel's HTTP client inside your own adapter or evaluate actively maintained payment packages. The package works best as a reference implementation or a thin client behind an internal provider contract. Avoid putting QIWI-specific facade calls directly in controllers or domain services.